Skip to content
Human resources ⇄ CRM

Lever to ZoomInfo integration — real-time data sync

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

Flow ZoomInfo data into Lever in real time — no exports, no schedulers, no custom scripts.

ZoomInfo is a read-only source: Stacksync reads its data in real time and delivers it into Lever, so Lever always reflects the current state of ZoomInfo — without exports, scripts, or schedulers.

ZoomInfo 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.

Common use cases

  • 01 Sync intent signals into the CRM or warehouse to trigger outbound plays on in-market accounts.
  • 02 Fill gaps in new lead records (email, phone, company size) as they enter the CRM.
  • 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

New team members provisioned when they are hired

When Lever records a new hire, a matching user or owner is created in ZoomInfo, so a new rep can start working accounts without waiting on a manual setup ticket.

Ownership and territory follow the org chart

When a person changes team, manager, or region in Lever, their accounts and territory assignments in ZoomInfo 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 ZoomInfo is flagged or deactivated, so former employees do not keep CRM access after their last day.

What you can sync between Lever and ZoomInfo

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 ZoomInfo objects How this pairing syncs
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. Technographics Technology install data per company, used for segmentation and territory planning. Notes and Contacts is specific to Lever and Technographics to ZoomInfo — 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. Company Hierarchies Parent and subsidiary linkage used to align CRM account hierarchies. Opportunities is specific to Lever and Company Hierarchies to ZoomInfo — 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. Company Profiles Firmographic records covering industry, size, revenue, and location, matched against CRM accounts. Postings is specific to Lever and Company Profiles to ZoomInfo — each maps to any object or custom field on the other side.
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. Contact Profiles Person records with title, email, phone, and company linkage, used to enrich leads and contacts. Requisitions is specific to Lever and Contact Profiles to ZoomInfo — each maps to any object or custom field on the other side.
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. Intent Signals Company-level topic scores indicating in-market buying behavior. Offers is specific to Lever and Intent Signals to ZoomInfo — 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. Scoops Event-driven signals such as leadership changes, funding rounds, and new projects. Users is specific to Lever and Scoops to ZoomInfo — each maps to any object or custom field on the other side.

How changes propagate between Lever and ZoomInfo

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 ZoomInfo Sub-second propagation

DetectionLever notifies Stacksync of record changes through webhook events. Webhooks for candidate and application lifecycle events (applicationCreated, candidateStageChange, candidateArchiveStateChange, candidateHired,.

DeliveryZoomInfo does not accept inbound record writes, so this direction carries requests rather than records: ZoomInfo's output flows back as field updates on the originating Lever records.

ZoomInfo Lever Interval-based propagation

DetectionStacksync polls ZoomInfo for changes on an incremental schedule, reading only records changed since the previous pass. Scheduled re-enrichment and polling.

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.
  • ZoomInfo: Usage is metered by credits and contract-based limits rather than a single public rate limit.
What ships with Lever ⇄ ZoomInfo

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

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

Real-time

Real-time sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

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

ZoomInfo

Integration surface
REST API organized around search and enrich endpoints
Authentication
API credentials exchanged for a short-lived JWT
Change detection
Scheduled re-enrichment and polling; the platform is primarily a lookup and enrichment source, not an event stream
Capabilities
read
Rate limits
Usage is metered by credits and contract-based limits rather than a single public rate limit.
How it works

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

    Choose tables

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

Lever and ZoomInfo 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 436 integrations available for Lever and ZoomInfo.

Popular · 8 of 436
All Lever integrations All ZoomInfo 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