Skip to content
Human resources ⇄ ERP

Lever to Rootstock ERP integration — real-time, two-way sync

Keep Lever and Rootstock ERP 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 Rootstock ERP

Sync the workers, org structure, and cost centers that Rootstock ERP and Lever share in real time, so the people Lever manages stay current in the system that runs finance and operations.

Lever is the system of record for people: who was hired, which department and location they sit in, who they report to, and how they are paid. Rootstock ERP runs finance and operations, and much of what it does depends on that same information, from booking labor cost to approving an expense report to staffing a project. Where the two are bridged by re-keying or an overnight file, each side spends the day out of step, with new hires missing from the systems they need and leavers still active where they should not be.

Stacksync syncs Bills of Material, Inventory Balances, Receipts and Shipments, Salesforce Accounts and Contacts in Rootstock ERP with Offers, Users, Stages, Feedback in Lever field by field, in real time, and in both directions. You decide which system owns which fields, so the people side stays authoritative for worker data while Rootstock ERP keeps its own accounting and operational detail, and every change made in one is reflected in the other within seconds instead of at the next batch run.

Common use cases

  • 01 Push confirmed sales orders to a 3PL or WMS and write shipment confirmations back to Rootstock.
  • 02 Replicate work order and inventory data to a Postgres database or warehouse for shop-floor and planning analytics.
  • 03 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.
  • 04 Push Postings and Requisitions into an HRIS or warehouse to reconcile approved headcount against open roles.

Common sync patterns

Reporting lines drive approvals

Manager and reporting-hierarchy changes in Lever keep expense and purchase approval chains in Rootstock ERP pointed at the right people.

Where Lever runs payroll: labor cost in the books

Pay and compensation data from Lever posts into Rootstock ERP as labor cost, so finance sees workforce spend without re-entering it by hand.

Where Lever is the worker system of record: one employee master

When a worker is hired, moved, or offboarded in Lever, the matching employee record in Rootstock ERP is created, updated, or deactivated, so the business system reflects the workforce as it actually is.

What you can sync between Lever and Rootstock ERP

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 Rootstock ERP objects How this pairing syncs
Stages Pipeline stage definitions that Opportunities move through; read to model funnel state and stage transitions in a database. Work Orders Manufacturing execution records synced to MES, scheduling, and analytics tools. Stages is specific to Lever and Work Orders to Rootstock ERP — 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. Purchase Orders Procurement documents synced with supplier portals and AP systems. Feedback is specific to Lever and Purchase Orders to Rootstock ERP — 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. Items / Products The manufacturing item master, kept aligned with e-commerce and PLM systems. Interviews is specific to Lever and Items / Products to Rootstock ERP — 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. Bills of Material Multi-level product structures read for costing and planning integrations. Notes and Contacts is specific to Lever and Bills of Material to Rootstock ERP — 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. Inventory Balances On-hand quantities by site and location, synced to storefronts and WMS. Opportunities is specific to Lever and Inventory Balances to Rootstock ERP — each maps to any object or custom field on the other side.
Postings Job posting records with categories, apply URLs, workplace type, and requisition codes. Can be created via POST /postings and read into a warehouse for open-role reporting. Receipts and Shipments Inbound and outbound transactions synced to logistics and 3PL systems. Postings is specific to Lever and Receipts and Shipments to Rootstock ERP — each maps to any object or custom field on the other side.

How changes propagate between Lever and Rootstock ERP

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 Rootstock ERP 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 Rootstock ERP through its API, with automatic retries and rate-limit backoff.

Rootstock ERP Lever Sub-second propagation

DetectionChanges in Rootstock ERP are captured at the source via change data capture — no polling loop against its API. Salesforce Change Data Capture on Rootstock custom objects where enabled (entity selection limits apply).

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.
  • Rootstock ERP: Consumes the Salesforce org's daily API request allocation, shared with other integrations.
What ships with Lever ⇄ Rootstock ERP

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Lever or Rootstock ERP 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 Rootstock ERP record.

Observability

Monitoring

Track your Lever ⇄ Rootstock ERP 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 Rootstock ERP.

How the Lever and Rootstock ERP 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

Rootstock ERP

Integration surface
Salesforce Platform APIs (REST, SOAP, Bulk) — Rootstock data lives in Salesforce custom objects
Authentication
OAuth 2.0 (standard Salesforce connected app flows)
Change detection
Salesforce Change Data Capture on Rootstock custom objects where enabled (entity selection limits apply); SOQL polling on SystemModstamp as fallback
Capabilities
read · write · CDC
Rate limits
Consumes the Salesforce org's daily API request allocation, shared with other integrations
How it works

How to connect Lever to Rootstock ERP — 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 Rootstock ERP 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
    Rootstock ERP connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Lever and Rootstock ERP 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 ⇄ Rootstock ERP
    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 Rootstock ERP
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Lever and Rootstock ERP 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 408 integrations available for Lever and Rootstock ERP.

Popular · 7 of 408
All Lever integrations All Rootstock ERP 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