Real-time
Two-way sync
Changes in Cin7 or Lever instantly reflect in both systems. No stale data, no manual imports.
ERP ⇄ Human resources
Cin7 to Lever integration — real-time, two-way sync
Keep Cin7 and Lever 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 Cin7 and Lever
Sync the workers, org structure, and cost centers that Cin7 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. Cin7 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 Inventory levels, Sales orders, Purchase orders, Contacts in Cin7 with Users, Stages, Feedback, Interviews 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 Cin7 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 Sync sales orders from Cin7 into an accounting platform or warehouse for revenue and margin reporting.
- 02 Keep customer records aligned between Cin7 and the CRM to remove duplicate account entry.
- 03 Consolidate Feedback, Interviews, and Notes into a warehouse for interviewer scorecard and time-to-fill reporting.
- 04 Write enriched Sources, Tags, and Contact data back onto Opportunities from an outbound sourcing pipeline.
Common sync patterns
One org structure
Departments, cost centers, and locations that both systems reference stay in agreement, so labor cost, approvals, and reporting in Cin7 roll up to the same structure Lever maintains.
Reporting lines drive approvals
Manager and reporting-hierarchy changes in Lever keep expense and purchase approval chains in Cin7 pointed at the right people.
Where Lever runs payroll: labor cost in the books
Pay and compensation data from Lever posts into Cin7 as labor cost, so finance sees workforce spend without re-entering it by hand.
What you can sync between Cin7 and Lever
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.
| Cin7 objects | Lever objects | How this pairing syncs | |
|---|---|---|---|
| Sales orders Orders captured from all channels; the main object for fulfillment and revenue syncs. | Stages Pipeline stage definitions that Opportunities move through; read to model funnel state and stage transitions in a database. | Sales orders is specific to Cin7 and Stages to Lever — each maps to any object or custom field on the other side. | |
| Purchase orders Supplier orders synced with procurement and accounting workflows. | 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 is specific to Cin7 and Feedback to Lever — each maps to any object or custom field on the other side. | |
| Contacts Customers and suppliers, matched to CRM records to keep account data consistent. | Interviews Scheduled interview panel events with times and interviewers; read for scheduling reporting and time-to-hire metrics, and creatable via the panels endpoint. | Contacts is specific to Cin7 and Interviews to Lever — each maps to any object or custom field on the other side. | |
| Branches / locations Warehouse entities that scope every stock movement and order allocation. | 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. | Branches / locations is specific to Cin7 and Notes and Contacts to Lever — each maps to any object or custom field on the other side. | |
| Stock adjustments and transfers Inventory movements read for audit and reconciliation reporting. | 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. | Stock adjustments and transfers is specific to Cin7 and Opportunities to Lever — each maps to any object or custom field on the other side. | |
| Credit notes / returns Return documents synced so finance and support see the same refund state. | 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. | Credit notes / returns is specific to Cin7 and Postings to Lever — each maps to any object or custom field on the other side. |
How changes propagate between Cin7 and Lever
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.
Cin7 Lever Sub-second propagation
DetectionCin7 notifies Stacksync of record changes through webhook events. Polling on modified-date filters.
DeliveryEach detected change is written to Lever through its API, with automatic retries and rate-limit backoff.
Lever Cin7 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 Cin7 through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Cin7: Subject to per-account API rate limits that differ between Cin7 Omni and Cin7 Core.
- 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.
What ships with Cin7 ⇄ Lever
Connect Cin7 and Lever for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Cin7–Lever connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Cin7 or Lever 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 Cin7 or Lever record.
Observability
Monitoring
Track your Cin7 ⇄ Lever sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Cin7 and Lever.
How the Cin7 and Lever connectors work
Cin7
- Integration surface
- REST API; note that Cin7 Omni and Cin7 Core (formerly DEAR Systems) are separate products with separate APIs
- Authentication
- API key credentials (paired with a username or account ID, depending on the product)
- Change detection
- Polling on modified-date filters; webhook support exists on some editions for order and stock events
- Capabilities
- read · write · webhooks
- Rate limits
- Subject to per-account API rate limits that differ between Cin7 Omni and Cin7 Core
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.
How it works
How to connect Cin7 to Lever — 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.
- 01
Connect your apps
Authenticate Cin7 and Lever with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Cin7
connected
Lever
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Cin7 and Lever 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.
objects · Cin7 ⇄ LeverCustomers 12,480Sales Orders 8,213Invoices 5,902Items 1,344 - 03
Map fields
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Cin7 LeverCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Cin7 and Lever integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Cin7 and Lever: authenticate both systems, choose the objects to sync (such as Cin7's Sales orders and Purchase orders), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Common patterns for Cin7 and Lever: One org structure; Reporting lines drive approvals; Where Lever runs payroll: labor cost in the books. Departments, cost centers, and locations that both systems reference stay in agreement, so labor cost, approvals, and reporting in Cin7 roll up to the same structure Lever maintains.
-
Cin7: REST API; note that Cin7 Omni and Cin7 Core (formerly DEAR Systems) are separate products with separate APIs. Authentication: API key credentials (paired with a username or account ID, depending on the product). Lever: 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). Stacksync manages authentication, retries, and rate limits on both sides.
-
Cin7: Order objects carry channel context (POS, B2B, e-commerce), which downstream reporting syncs typically preserve for channel-level margin analysis. Lever: List endpoints use cursor-based pagination at up to 100 records per page; incremental syncs rely on created_at and updated_at range filters. Stacksync's field mapping accounts for these differences between Cin7 and Lever without custom code.
-
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means Cin7 and Lever records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Cin7 and Lever connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Cin7–Lever integration in-house.
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.
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:
Related integrations
Every pair below is a real-time, two-way sync. Search all 500 integrations available for Cin7 and Lever.
Popular · 7 of 500
-
Cin7 ⇄ Greenhouse -
Cin7 ⇄ Jobvite -
Cin7 ⇄ Namely -
Cin7 ⇄ Paylocity -
Lever ⇄ Blue Yonder WMS -
Lever ⇄ Brightpearl - Lever ⇄ DEAR Inventory
No integrations match .
