Skip to content
Human resources ⇄ Business productivity

Lever to Servicemax integration — real-time, two-way sync

Keep Lever and Servicemax in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.

  • SOC 2 and 6 other compliance frameworks
  • POC with real engineers in minutes

Adopted by fast-scaling companies moving mission-critical data in real time

Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect Lever and Servicemax

Keep the people, teams, and status that Servicemax and Lever share aligned in real time, so a hire, role change, or departure recorded in one reaches the other within seconds.

Each tool in Servicemax keeps its own list of who can use it: users, members, or agents, along with the team they sit on and whether they are still active. Lever is the authoritative record of the same people as employees, with their department, manager, and employment status. When those two are connected only by manual account admin or a periodic export, the work tools drift: new hires wait days for access, team and manager changes never catch up, and people who have left keep standing accounts.

Stacksync syncs Work Orders, Work Details, Installed Products, Service Contracts in Servicemax with Interviews, Notes and Contacts, Opportunities, Postings in Lever bi-directionally and in real time. A person added, moved, or offboarded in Lever creates or updates the matching user in Servicemax within seconds, with field-level mapping and conflict resolution in place of spreadsheets and one-off account changes. Where Servicemax captures details of its own, such as a corrected contact or a login identity, those can flow back to Lever in whichever direction you configure.

Because the sync is field-level, each system keeps its own extras; only the shared facts, who a person is, which team they belong to, and whether their access should be on, are held in agreement.

Common use cases

  • 01 Mirror Accounts and Contacts between ServiceMax and the CRM system of record so customer and site data stays consistent.
  • 02 Sync Work Orders (SVMXC__Service_Order__c) and Work Details bi-directionally with Postgres so ops and analytics teams read and write field-service data in plain SQL.
  • 03 Write enriched Sources, Tags, and Contact data back onto Opportunities from an outbound sourcing pipeline.
  • 04 Two-way sync Opportunities and their Stages between Lever and a Postgres database so recruiting ops and analysts query the pipeline in SQL while recruiters keep working in Lever.

Common sync patterns

One employee directory

A person's name, title, contact details, or status corrected in either system updates the other, so both sides stop maintaining separate copies of the same person.

Org and team structure kept current

Department, team, and reporting-line changes from Lever keep the groups, queues, or projects in Servicemax assigned to the right people.

Where Servicemax routes or assigns work by person: assignments follow the org

When someone changes teams or managers in Lever, the queues, ownership, or approvals in Servicemax update to match, so work reaches whoever holds the role now.

What you can sync between Lever and Servicemax

Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.

Lever objects Servicemax objects How this pairing syncs
Users Lever team members (recruiters, hiring managers) with configurable roles; can be created via POST /users, deactivated, and reactivated through the API. Installed Products SVMXC__Installed_Product__c; the installed-base asset record driving entitlement and service history; synced with asset and IoT databases. Users is specific to Lever and Installed Products to Servicemax — each maps to any object or custom field on the other side.
Stages Pipeline stage definitions that Opportunities move through; read to model funnel state and stage transitions in a database. Service Contracts SVMXC__Service_Contract__c; coverage and entitlement agreements; synced to warehouses for renewal, SLA, and warranty reporting. Stages is specific to Lever and Service Contracts to Servicemax — each maps to any object or custom field on the other side.
Feedback Interview feedback and scorecard forms attached to Opportunities; created via POST /opportunities/:id/feedback and consolidated into a warehouse for interviewer analytics. Stock History SVMXC__Stock_History__c; append-only log of inventory transactions (RMA, shipment, parts receipt); read out for parts and inventory analytics. Feedback is specific to Lever and Stock History to Servicemax — each maps to any object or custom field on the other side.
Interviews Scheduled interview panel events with times and interviewers; read for scheduling reporting and time-to-hire metrics, and creatable via the panels endpoint. Accounts Standard Salesforce Account; customer and site company records; synced two-way with CRM and database customer tables. Interviews is specific to Lever and Accounts to Servicemax — each maps to any object or custom field on the other side.
Notes and Contacts Free-text Notes on Opportunities plus the underlying Contact (person) that dedupes multiple Opportunities; notes are posted via POST /opportunities/:id/notes and contact-level tags, sources, and links can be added back for attribution. Contacts Standard Salesforce Contact; people linked to Accounts and service sites; synced with CRM and support person records. Notes and Contacts is specific to Lever and Contacts to Servicemax — each maps to any object or custom field on the other side.
Opportunities The core pipeline record for a candidate applying to a role; replaced the deprecated Candidates endpoint. Created via POST /opportunities and updated (stage, archive, links, tags, sources, files) through the API, and synced two-way with a database or HRIS. Cases Standard Salesforce Case; support records that often precede a Work Order; synced with help desk tools and reporting databases. Opportunities is specific to Lever and Cases to Servicemax — each maps to any object or custom field on the other side.

How changes propagate between Lever and Servicemax

Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.

Lever Servicemax Sub-second propagation

DetectionLever notifies Stacksync of record changes through webhook events. Webhooks for candidate and application lifecycle events (applicationCreated, candidateStageChange, candidateArchiveStateChange, candidateHired,.

DeliveryEach detected change is written to Servicemax through its API, with automatic retries and rate-limit backoff.

Servicemax Lever Sub-second propagation

DetectionChanges in Servicemax are captured at the source via change data capture — no polling loop against its API. Salesforce mechanisms — Apex triggers or polling on SystemModstamp/LastModifiedDate, with Change Data Capture / Platform Events available per object.

DeliveryEach detected change is written to Lever through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • Lever: 10 requests/second per API key with a token-bucket burst to ~20/s; POSTs that create candidates/applications are throttled to roughly 2/second. Sustained overage returns 429 with Retry-After. List endpoints are cursor-paginated at up to 100 records per page.
  • Servicemax: Governed by the Salesforce org-wide daily API request allocation, shared across all integrations and scaled by edition and license count.
What ships with Lever ⇄ Servicemax

Connect Lever and Servicemax for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Lever–Servicemax connection.

Real-time

Two-way sync

Changes in Lever or Servicemax instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Lever or Servicemax data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.

At scale

Event queues

Handle millions of events per minute without losing a single Lever or Servicemax record.

Observability

Monitoring

Track your Lever ⇄ Servicemax sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Lever and Servicemax.

How the Lever and Servicemax connectors work

Lever

Integration surface
REST Data API (api.lever.co/v1)
Authentication
API key over HTTP Basic auth (key as username, blank password) for internal integrations, or OAuth 2.0 with 1-hour access tokens for partner integrations (auth.lever.co)
Change detection
Webhooks for candidate and application lifecycle events (applicationCreated, candidateStageChange, candidateArchiveStateChange, candidateHired, interview created/updated/deleted), plus incremental polling via created_at and updated_at range filters on Opportunities
Capabilities
read · write · webhooks
Rate limits
10 requests/second per API key with a token-bucket burst to ~20/s; POSTs that create candidates/applications are throttled to roughly 2/second. Sustained overage returns 429 with Retry-After. List endpoints are cursor-paginated at up to 100 records per page.
Lever setup guide

Servicemax

Integration surface
Salesforce REST, SOAP, and Bulk APIs (ServiceMax is a managed package on the Salesforce platform)
Authentication
Salesforce OAuth login via a user with API access; the connecting profile needs object and field permissions on ServiceMax's SVMXC__ objects
Change detection
Salesforce mechanisms — Apex triggers or polling on SystemModstamp/LastModifiedDate, with Change Data Capture / Platform Events available per object where enabled
Capabilities
read · write · CDC
Rate limits
Governed by the Salesforce org-wide daily API request allocation, shared across all integrations and scaled by edition and license count
How it works

How to connect Lever to Servicemax — three steps, no code

Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.

  1. 01

    Connect your apps

    Authenticate Lever and Servicemax with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Lever connected
    Servicemax connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Lever and Servicemax objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Lever ⇄ Servicemax
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Lever Servicemax
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Lever and Servicemax integration FAQ

SECURITY

Security teams trust Stacksync

As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.

Learn more about security
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 511 integrations available for Lever and Servicemax.

Popular · 8 of 511
All Lever integrations All Servicemax integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.

Book a demo Tour the platform on your own