Skip to content
CRM ⇄ Human resources

6sense to Lever integration — real-time data sync

Keep 6sense 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 6sense and Lever

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

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

6sense 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 Enrich inbound leads with 6sense firmographic and account-match data before routing.
  • 02 Feed in-market account lists to sales engagement tools to start sequences automatically.
  • 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

New team members provisioned when they are hired

When Lever records a new hire, a matching user or owner is created in 6sense, 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 6sense 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 6sense is flagged or deactivated, so former employees do not keep CRM access after their last day.

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

6sense objects Lever objects How this pairing syncs
Buying Stage Scores Model-predicted stage per account, synced onto CRM records for prioritization. Interviews Scheduled interview panel events with times and interviewers; read for scheduling reporting and time-to-hire metrics, and creatable via the panels endpoint. Buying Stage Scores is specific to 6sense and Interviews to Lever — each maps to any object or custom field on the other side.
Intent Signals Keyword-level research activity used to flag in-market accounts. 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. Intent Signals is specific to 6sense and Notes and Contacts to Lever — each maps to any object or custom field on the other side.
People / Contacts Persona and contact data surfaced for accounts, used to build outreach lists. 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. People / Contacts is specific to 6sense and Opportunities to Lever — each maps to any object or custom field on the other side.
Reach Scores Model scores reflecting the level and recency of outreach to an account or contact, used to prioritize follow-up. 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. Reach Scores is specific to 6sense and Postings to Lever — each maps to any object or custom field on the other side.
Accounts Company records enriched with firmographics and intent data, matched to CRM accounts. 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. Accounts is specific to 6sense and Requisitions to Lever — each maps to any object or custom field on the other side.
Segments Dynamic account lists built from intent and fit criteria, read out to drive targeting. 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. Segments is specific to 6sense and Offers to Lever — each maps to any object or custom field on the other side.

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

6sense Lever Interval-based propagation

DetectionStacksync polls 6sense for changes on an incremental schedule, reading only records changed since the previous pass. Polling.

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

Lever 6sense Sub-second propagation

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

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

Rate-limit considerations

  • 6sense: Subject to the platform's API rate limits, which vary by contracted API package.
  • 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 6sense ⇄ Lever

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

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

Real-time

Real-time sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

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

How the 6sense and Lever connectors work

6sense

Integration surface
REST API
Authentication
API key (token passed in request headers)
Change detection
Polling; scores and segment membership are typically refreshed on the platform's model update cadence
Capabilities
read
Rate limits
Subject to the platform's API rate limits, which vary by contracted API package

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

    Choose tables

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

6sense 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 432 integrations available for 6sense and Lever.

Popular · 8 of 432
All 6sense 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