Skip to content
CRM ⇄ Human resources

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

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

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

HubSpot 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 Pipeline, Stages, Audit, Contact in HubSpot with Stages, Feedback, Interviews, Notes and Contacts 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 HubSpot keeps ownership and territory current, and Stacksync resolves conflicts by the rules you set.

Common use cases

  • 01 Write warehouse-computed lead and account scores back to HubSpot properties on a schedule or in near real time.
  • 02 Sync HubSpot Tickets with an internal support database to unify service reporting across channels.
  • 03 Push Postings and Requisitions into an HRIS or warehouse to reconcile approved headcount against open roles.
  • 04 When an Opportunity is marked hired, write the candidate and its Offer into an HRIS or onboarding system to start employee provisioning.

Common sync patterns

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.

Where Lever tracks people the business also engages: contacts stay in sync

A person recorded in Lever, such as a candidate or applicant, can create or update the matching contact in HubSpot, so relationship history and outreach are not rebuilt from scratch when the same individual appears in both.

New team members provisioned when they are hired

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

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

HubSpot objects Lever objects How this pairing syncs
Stages Synced with incremental and full sync per the Stacksync docs. Stages Pipeline stage definitions that Opportunities move through; read to model funnel state and stage transitions in a database. Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions.
Line Item Synced with incremental and full sync per the Stacksync docs. 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. Line Item is specific to HubSpot and Requisitions to Lever — each maps to any object or custom field on the other side.
Product Synced with incremental and full sync per the Stacksync docs. 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. Product is specific to HubSpot and Offers to Lever — each maps to any object or custom field on the other side.
Ticket Synced with incremental and full sync per the Stacksync docs. Users Lever team members (recruiters, hiring managers) with configurable roles; can be created via POST /users, deactivated, and reactivated through the API. Ticket is specific to HubSpot and Users to Lever — each maps to any object or custom field on the other side.
Quote Synced with incremental and full sync per the Stacksync docs. Feedback Interview feedback and scorecard forms attached to Opportunities; created via POST /opportunities/:id/feedback and consolidated into a warehouse for interviewer analytics. Quote is specific to HubSpot and Feedback to Lever — each maps to any object or custom field on the other side.
Goal Synced with incremental and full sync per the Stacksync docs. Interviews Scheduled interview panel events with times and interviewers; read for scheduling reporting and time-to-hire metrics, and creatable via the panels endpoint. Goal is specific to HubSpot and Interviews to Lever — each maps to any object or custom field on the other side.

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

HubSpot Lever Sub-second propagation

DetectionHubSpot pushes changes as they happen — webhook events backed by change data capture. Records: incremental near-real-time change tracking.

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

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

Rate-limit considerations

  • HubSpot: Request limits vary by subscription tier and API type.
  • 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 HubSpot ⇄ Lever

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

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

How the HubSpot and Lever connectors work

HubSpot

Integration surface
REST API (CRM v3)
Authentication
OAuth (choose HubSpot account and authorize Stacksync); requires a HubSpot 'Super Admin' to grant access; optional "Grant access to sensitive fields" checkbox for sensitive/highly sensitive fields
Change detection
Records: incremental near-real-time change tracking. Associations: HubSpot has no native association CDC
Capabilities
read · write · CDC · webhooks
Rate limits
Request limits vary by subscription tier and API type.
HubSpot 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 HubSpot 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 HubSpot 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
    HubSpot connected
    Lever connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

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

HubSpot 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 536 integrations available for HubSpot and Lever.

Popular · 6 of 536
All HubSpot 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