Skip to content
Business productivity ⇄ Human resources

Full Enrich to Lever integration — real-time, two-way sync

Keep Full Enrich 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 Full Enrich and Lever

Keep the people, teams, and status that Full Enrich and Lever share aligned in real time, so a hire, role change, or departure recorded in one reaches the other within seconds.

Each tool in Full Enrich keeps its own list of who can use it: users, members, or agents, along with the team they sit on and whether they are still active. Lever is the authoritative record of the same people as employees, with their department, manager, and employment status. When those two are connected only by manual account admin or a periodic export, the work tools drift: new hires wait days for access, team and manager changes never catch up, and people who have left keep standing accounts.

Stacksync syncs Credits, Enrichment requests, Contacts, Enrichment results in Full Enrich with Requisitions, Offers, Users, Stages in Lever bi-directionally and in real time. A person added, moved, or offboarded in Lever creates or updates the matching user in Full Enrich within seconds, with field-level mapping and conflict resolution in place of spreadsheets and one-off account changes. Where Full Enrich captures details of its own, such as a corrected contact or a login identity, those can flow back to Lever in whichever direction you configure.

Because the sync is field-level, each system keeps its own extras; only the shared facts, who a person is, which team they belong to, and whether their access should be on, are held in agreement.

Common use cases

  • 01 Enrich new CRM contacts with verified emails and mobile numbers as they are created.
  • 02 Run waterfall enrichment over warehouse lead lists before importing them into outbound sequencers.
  • 03 Write enriched Sources, Tags, and Contact data back onto Opportunities from an outbound sourcing pipeline.
  • 04 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.

Common sync patterns

Org and team structure kept current

Department, team, and reporting-line changes from Lever keep the groups, queues, or projects in Full Enrich assigned to the right people.

Where Full Enrich routes or assigns work by person: assignments follow the org

When someone changes teams or managers in Lever, the queues, ownership, or approvals in Full Enrich update to match, so work reaches whoever holds the role now.

Onboarding: access ready on day one

A new hire recorded in Lever creates the matching user in Full Enrich with the right team and manager already set, so people can start working without waiting on a provisioning ticket.

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

Full Enrich objects Lever objects How this pairing syncs
Phone numbers Returned mobile and direct-dial numbers from the provider waterfall. 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. Phone numbers is specific to Full Enrich and Notes and Contacts to Lever — each maps to any object or custom field on the other side.
Credits Account balance consumed on successful finds; monitored to pace sync jobs. 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. Credits is specific to Full Enrich and Opportunities to Lever — each maps to any object or custom field on the other side.
Enrichment requests Submitted batches of contacts to enrich; processed asynchronously by the waterfall. 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. Enrichment requests is specific to Full Enrich and Postings to Lever — each maps to any object or custom field on the other side.
Contacts The person inputs (name plus company or domain) sent for enrichment. 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. Contacts is specific to Full Enrich and Requisitions to Lever — each maps to any object or custom field on the other side.
Enrichment results Completed records fetched by request ID or delivered via webhook. 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. Enrichment results is specific to Full Enrich and Offers to Lever — each maps to any object or custom field on the other side.
Emails Returned addresses with verification status, written back to the CRM or database. Users Lever team members (recruiters, hiring managers) with configurable roles; can be created via POST /users, deactivated, and reactivated through the API. Emails is specific to Full Enrich and Users to Lever — each maps to any object or custom field on the other side.

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

Full Enrich Lever Sub-second propagation

DetectionFull Enrich notifies Stacksync of record changes through webhook events. Webhook callbacks when enrichment batches complete, with polling of result endpoints as a fallback.

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

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

Rate-limit considerations

  • Full Enrich: Subject to the platform's API rate limits and per-batch size constraints.
  • 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 Full Enrich ⇄ Lever

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

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

How the Full Enrich and Lever connectors work

Full Enrich

Integration surface
REST API with asynchronous bulk enrichment endpoints
Authentication
API key (Bearer token)
Change detection
Webhook callbacks when enrichment batches complete, with polling of result endpoints as a fallback
Capabilities
read · write · webhooks
Rate limits
Subject to the platform's API rate limits and per-batch size constraints

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

    Choose tables

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

Full Enrich 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 386 integrations available for Full Enrich and Lever.

Popular · 7 of 386
All Full Enrich 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