Skip to content
CRM ⇄ Human resources

Clearbit to Lever integration — real-time data sync

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

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

Clearbit 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 Clearbit — without exports, scripts, or schedulers.

Clearbit 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 Refresh firmographic fields on existing accounts on a schedule so segmentation stays current.
  • 02 Enrich new CRM leads with person and company attributes as they are created, keyed by email and domain.
  • 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

Ownership and territory follow the org chart

When a person changes team, manager, or region in Lever, their accounts and territory assignments in Clearbit 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 Clearbit 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 Clearbit 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.

Clearbit objects Lever objects How this pairing syncs
Persons Individual profiles looked up by email and used to enrich contacts and leads. 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. Persons is specific to Clearbit and Offers to Lever — each maps to any object or custom field on the other side.
Reveal matches IP-to-company resolutions used to identify anonymous website traffic. Users Lever team members (recruiters, hiring managers) with configurable roles; can be created via POST /users, deactivated, and reactivated through the API. Reveal matches is specific to Clearbit and Users to Lever — each maps to any object or custom field on the other side.
Name-to-domain lookups Company name resolution used to normalize account records before enrichment. Stages Pipeline stage definitions that Opportunities move through; read to model funnel state and stage transitions in a database. Name-to-domain lookups is specific to Clearbit and Stages to Lever — each maps to any object or custom field on the other side.
Enrichment attributes The firmographic and technographic fields appended to destination records. Feedback Interview feedback and scorecard forms attached to Opportunities; created via POST /opportunities/:id/feedback and consolidated into a warehouse for interviewer analytics. Enrichment attributes is specific to Clearbit and Feedback to Lever — each maps to any object or custom field on the other side.
Companies Firmographic profiles looked up by domain and merged into account records. Interviews Scheduled interview panel events with times and interviewers; read for scheduling reporting and time-to-hire metrics, and creatable via the panels endpoint. Companies is specific to Clearbit and Interviews to Lever — each maps to any object or custom field on the other side.

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

Clearbit Lever Sub-second propagation

DetectionClearbit notifies Stacksync of record changes through webhook events. On-demand lookups.

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

Lever Clearbit Sub-second propagation

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

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

Rate-limit considerations

  • Clearbit: Subject to plan-based API rate limits and lookup volumes.
  • 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 Clearbit ⇄ Lever

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

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

Real-time

Real-time sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

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

How the Clearbit and Lever connectors work

Clearbit

Integration surface
REST API (separate endpoints per product: Enrichment, Reveal)
Authentication
API key (bearer secret key)
Change detection
On-demand lookups; asynchronous enrichment results can be delivered via webhook callbacks
Capabilities
read · webhooks
Rate limits
Subject to plan-based API rate limits and lookup volumes

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 Clearbit 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 Clearbit 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
    Clearbit connected
    Lever connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

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

Clearbit 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 383 integrations available for Clearbit and Lever.

Popular · 8 of 383
All Clearbit 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