Skip to content
CRM ⇄ Human resources

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

Keep Chorusai 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 Chorusai and Lever

Keep the people who own accounts in Chorusai 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.

Chorusai 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 Moments, Playlists, Engagements, Recordings (Conversations) in Chorusai 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 Lever stays authoritative on roles and org structure while Chorusai keeps ownership and territory current, and Stacksync resolves conflicts by the rules you set.

Common use cases

  • 01 Upload externally recorded dialer or web-conference audio into Chorus as Recordings so it gets transcribed and analyzed like native calls.
  • 02 Sync Trackers such as pricing, competitor, and next-steps mentions onto matching CRM Opportunities as coaching and deal-risk signals.
  • 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

Ownership and territory follow the org chart

When a person changes team, manager, or region in Lever, their accounts and territory assignments in Chorusai update to match, so pipeline stays with the right owner.

Deactivate access when someone leaves

When Lever marks a worker as departed, the matching user in Chorusai 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.

What you can sync between Chorusai 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.

Chorusai objects Lever objects How this pairing syncs
Users Chorus users with roles and team membership; read to map engagement owners and participants to CRM and warehouse identities. Users Lever team members (recruiters, hiring managers) with configurable roles; can be created via POST /users, deactivated, and reactivated through the API. Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions.
Playlists Curated collections of Moments and Recordings; created and managed to share coaching examples across teams. Interviews Scheduled interview panel events with times and interviewers; read for scheduling reporting and time-to-hire metrics, and creatable via the panels endpoint. Playlists is specific to Chorusai and Interviews to Lever — each maps to any object or custom field on the other side.
Engagements Meetings and dialer calls, the core record; filterable by date_time, participants, and processing_state, and polled incrementally to read conversation activity out. 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. Engagements is specific to Chorusai and Notes and Contacts to Lever — each maps to any object or custom field on the other side.
Recordings (Conversations) The recorded call with utterances, transcript, thumbnails, and metrics; read for analysis and uploaded or deleted through the API. 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. Recordings (Conversations) is specific to Chorusai and Opportunities to Lever — each maps to any object or custom field on the other side.
Trackers AI keyword and topic trackers (pricing, competitors, next steps) surfaced within a conversation; read out as coaching and deal-risk signals. 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. Trackers is specific to Chorusai and Postings to Lever — each maps to any object or custom field on the other side.
Deals CRM opportunity context attached to a conversation (account, deal, owner); read to attribute call activity to open pipeline. Requisitions Headcount/requisition records with custom requisition fields, tied to Postings; read via GET /requisitions and synced to an HRIS to reconcile approved headcount against open roles. Deals is specific to Chorusai and Requisitions to Lever — each maps to any object or custom field on the other side.

How changes propagate between Chorusai 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.

Chorusai Lever Interval-based propagation

DetectionStacksync polls Chorusai for changes on an incremental schedule, reading only records changed since the previous pass. Polling the engagements endpoint on date_time and processing_state.

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

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

Rate-limit considerations

  • Chorusai: Rate limits are not publicly documented; recording upload and analysis are asynchronous, so transcripts and trackers appear only after processing_state completes.
  • 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 Chorusai ⇄ Lever

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

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

How the Chorusai and Lever connectors work

Chorusai

Integration surface
REST API (api-docs.chorus.ai)
Authentication
Per-user API token generated in Chorus Personal Settings, sent in the Authorization request header
Change detection
Polling the engagements endpoint on date_time and processing_state; no public change webhooks or CDC
Capabilities
read · write
Rate limits
Rate limits are not publicly documented; recording upload and analysis are asynchronous, so transcripts and trackers appear only after processing_state completes
Chorusai setup guide

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
How it works

How to connect Chorusai 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.

  1. 01

    Connect your apps

    Authenticate Chorusai 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.

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

    Choose tables

    Pick the Chorusai 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.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Chorusai ⇄ Lever
    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
    Chorusai Lever
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Chorusai and Lever 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 527 integrations available for Chorusai and Lever.

Popular · 7 of 527
All Chorusai integrations All Lever 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