Skip to content
Human resources ⇄ CRM

Lever to Oracle CX Sales integration — real-time, two-way sync

Keep Lever and Oracle CX Sales 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 Oracle CX Sales

Keep the people who own accounts in Oracle CX Sales in step with the workforce records in Lever, so ownership, roles, and org structure stay current in both systems, in real time and in both directions.

Oracle CX Sales 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 Opportunities, Activities, Territories, Partners in Oracle CX Sales with Requisitions, Offers, Users, Stages 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 Oracle CX Sales keeps ownership and territory current, and Stacksync resolves conflicts by the rules you set.

Common use cases

  • 01 Run CX Sales alongside a second CRM during a merger or migration, with records converging in both directions.
  • 02 Push product usage and entitlement data from internal databases into CX Sales to inform forecasting.
  • 03 Push Postings and Requisitions into an HRIS or warehouse to reconcile approved headcount against open roles.
  • 04 When an Opportunity is marked hired, write the candidate and its Offer into an HRIS or onboarding system to start employee provisioning.

Common sync patterns

Deactivate access when someone leaves

When Lever marks a worker as departed, the matching user in Oracle CX Sales is flagged or deactivated, so former employees do not keep CRM access after their last day.

One directory of people

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.

Where Lever tracks people the business also engages: contacts stay in sync

A person recorded in Lever, such as a candidate or applicant, can create or update the matching contact in Oracle CX Sales, so relationship history and outreach are not rebuilt from scratch when the same individual appears in both.

What you can sync between Lever and Oracle CX Sales

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 Oracle CX Sales objects How this pairing 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. Opportunities Pipeline records with revenue lines, mirrored to forecasting and billing systems Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions.
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. Territories Assignment structures that downstream routing and comp tools consume Offers is specific to Lever and Territories to Oracle CX Sales — each maps to any object or custom field on the other side.
Users Lever team members (recruiters, hiring managers) with configurable roles; can be created via POST /users, deactivated, and reactivated through the API. Partners Channel records for organizations selling through partner networks Users is specific to Lever and Partners to Oracle CX Sales — 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. Custom objects Objects built in Application Composer, exposed through the same REST conventions Stages is specific to Lever and Custom objects to Oracle CX Sales — 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. Accounts Customer organizations, the anchor record for bi-directional CRM syncs Feedback is specific to Lever and Accounts to Oracle CX Sales — 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. Contacts People linked to accounts, kept consistent with marketing and support systems Interviews is specific to Lever and Contacts to Oracle CX Sales — each maps to any object or custom field on the other side.

How changes propagate between Lever and Oracle CX Sales

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

Oracle CX Sales Lever Interval-based propagation

DetectionStacksync polls Oracle CX Sales for changes on an incremental schedule, reading only records changed since the previous pass. Polling on last-update audit fields.

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.
  • Oracle CX Sales: Subject to the platform's API rate limits.
What ships with Lever ⇄ Oracle CX Sales

Connect Lever and Oracle CX Sales for flexible, real-time data sync.

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Lever or Oracle CX Sales 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 Oracle CX Sales record.

Observability

Monitoring

Track your Lever ⇄ Oracle CX Sales 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 Oracle CX Sales.

How the Lever and Oracle CX Sales 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

Oracle CX Sales

Integration surface
REST API (Oracle Fusion Applications REST framework); SOAP services also available
Authentication
OAuth 2.0 or basic authentication against the Fusion instance, depending on configuration
Change detection
polling on last-update audit fields; event-driven patterns route through Oracle Integration rather than direct webhooks
Capabilities
read · write
Rate limits
subject to the platform's API rate limits
How it works

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

    Choose tables

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

Lever and Oracle CX Sales 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 421 integrations available for Lever and Oracle CX Sales.

Popular · 7 of 421
All Lever integrations All Oracle CX Sales 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