Two-way sync
Changes in Creatio CRM or Lever instantly reflect in both systems. No stale data, no manual imports.
Keep Creatio CRM 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.
Creatio CRM runs on people as much as on accounts: every contact, deal, and account has an owner, and those owners are employees whose roles, teams, and status are held in Lever. Lever is the system of record for the workforce, from new hires to promotions to departures, and often for the candidates the business is still deciding on. When the two systems are connected only by re-keying or an overnight export, they drift apart, and the CRM ends up assigning accounts to people who have left, holding territories that no longer match the org chart, and waiting days to give a new rep access.
Stacksync syncs Orders, Products, Custom sections (objects), Accounts in Creatio CRM with Opportunities, Postings, Requisitions, Offers in Lever field by field, in real time, and in both directions. You decide which system owns which fields, so Lever stays authoritative on roles and org structure while Creatio CRM keeps ownership and territory current, and Stacksync resolves conflicts by the rules you set.
A person's name, title, email, phone, or manager corrected in either system updates the other, so both stop maintaining separate copies of the same individual.
A person recorded in Lever, such as a candidate or applicant, can create or update the matching contact in Creatio CRM, so relationship history and outreach are not rebuilt from scratch when the same individual appears in both.
When Lever records a new hire, a matching user or owner is created in Creatio CRM, so a new rep can start working accounts without waiting on a manual setup ticket.
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.
| Creatio CRM objects | Lever objects | How this pairing syncs | |
|---|---|---|---|
| Opportunities Deal records with stages and amounts used in revenue syncs. | 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. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Cases Service requests handled in Creatio's service workflows; syncable to help desk tools. | Offers Offer records attached to an Opportunity with status and offer-form fields; exposed read-only through GET /opportunities/:id/offers, so they sync outbound to an HRIS or onboarding system when a candidate reaches the offer stage. | Cases is specific to Creatio CRM and Offers to Lever — each maps to any object or custom field on the other side. | |
| Orders Order records bridging CRM and fulfillment or ERP systems. | Users Lever team members (recruiters, hiring managers) with configurable roles; can be created via POST /users, deactivated, and reactivated through the API. | Orders is specific to Creatio CRM and Users to Lever — each maps to any object or custom field on the other side. | |
| Products Catalog items referenced on orders and opportunities. | Stages Pipeline stage definitions that Opportunities move through; read to model funnel state and stage transitions in a database. | Products is specific to Creatio CRM and Stages to Lever — each maps to any object or custom field on the other side. | |
| Custom sections (objects) No-code custom entities, exposed through the same API as standard objects. | Feedback Interview feedback and scorecard forms attached to Opportunities; created via POST /opportunities/:id/feedback and consolidated into a warehouse for interviewer analytics. | Custom sections (objects) is specific to Creatio CRM and Feedback to Lever — each maps to any object or custom field on the other side. | |
| Accounts Company records at the center of Creatio's CRM model; commonly synced with ERP customer masters. | 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 is specific to Creatio CRM and Interviews to Lever — each maps to any object or custom field on the other side. |
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.
DetectionStacksync polls Creatio CRM for changes on an incremental schedule, reading only records changed since the previous pass. Polling on ModifiedOn system columns.
DeliveryEach detected change is written to Lever through its API, with automatic retries and rate-limit backoff.
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 Creatio CRM through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Creatio CRM–Lever connection.
Changes in Creatio CRM or Lever instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Creatio CRM or Lever data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Creatio CRM or Lever record.
Track your Creatio CRM ⇄ Lever sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Creatio CRM and Lever.
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.
Authenticate Creatio CRM 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.
Pick the Creatio CRM 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.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Yes. Stacksync provides a managed, real-time two-way integration between Creatio CRM and Lever: authenticate both systems, choose the objects to sync (such as Creatio CRM's Opportunities and Cases), map fields visually, and changes propagate both ways in milliseconds — no code required.
Change detection on Creatio CRM: Polling on ModifiedOn system columns; outbound notifications require configuring business processes. On Lever: 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. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
On the Creatio CRM side: Orders, Products, Custom sections (objects), Accounts, plus custom fields where Creatio CRM exposes them. On the Lever side: Opportunities, Postings, Requisitions, Offers. Stacksync auto-detects both schemas and converts types between the two systems.
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
Common patterns for Creatio CRM and Lever: One directory of people; Where Lever tracks people the business also engages: contacts stay in sync; New team members provisioned when they are hired. A person's name, title, email, phone, or manager corrected in either system updates the other, so both stop maintaining separate copies of the same individual.
Creatio CRM: OData REST API plus a proprietary DataService API. Authentication: OAuth 2.0 or cookie-based session authentication. 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.
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.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 424 integrations available for Creatio CRM and Lever.