Skip to content
Data warehouse ⇄ Human resources

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

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

Land the people and organization records from Lever in Firebolt as live tables for workforce reporting, without extract jobs, and write computed results back where Lever can use them.

Workforce data is some of the most requested data in the warehouse and some of the most awkward to move: the record types are many, the fields carry sensitive personal information, the APIs are strict, and hand-built extract jobs go stale or break quietly. Whether Lever is the system of record for employees and payroll, for candidates and applications, or for learners and course completions, the reporting belongs in Firebolt next to everything else the company measures.

Stacksync syncs Stages, Feedback, Interviews, Notes and Contacts from Lever into tables in Firebolt continuously, handling API limits and schema drift as they come. The connection is bi-directional, so values computed in Firebolt, such as headcount rollups, cost allocations, or attrition risk flags, can be written back to fields in Lever where the HR team acts on them. You configure which records and fields cross over, and in which direction, instead of maintaining pipeline code.

Common use cases

  • 01 Sync aggregated results from Firebolt back to operational tools that need computed metrics (reverse ETL).
  • 02 Sync CRM objects into Firebolt so customer-facing dashboards reflect recent pipeline changes.
  • 03 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.
  • 04 Push Postings and Requisitions into an HRIS or warehouse to reconcile approved headcount against open roles.

Common sync patterns

Headcount and cost joined with everything else

Analysts combine Lever's workforce records with finance, product, or operational data already in Firebolt for reporting the HR system cannot produce on its own.

Fresh data instead of last night's load

Because changes stream continuously, reports query current workforce data rather than waiting for an overnight load window to finish.

Queryable history for planning and audit

A continuously synced copy in Firebolt gives you a durable, queryable record of how Lever's records change over time, for headcount planning and audit questions.

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

Firebolt objects Lever objects How this pairing syncs
External tables References to files in object storage used to stage bulk loads. Users Lever team members (recruiters, hiring managers) with configurable roles; can be created via POST /users, deactivated, and reactivated through the API. External tables is specific to Firebolt and Users to Lever — each maps to any object or custom field on the other side.
Views Curated query surfaces commonly used as sources for reverse ETL. Stages Pipeline stage definitions that Opportunities move through; read to model funnel state and stage transitions in a database. Views is specific to Firebolt and Stages to Lever — each maps to any object or custom field on the other side.
Aggregating indexes Precomputed rollups maintained at write time; incremental loads update them automatically. Feedback Interview feedback and scorecard forms attached to Opportunities; created via POST /opportunities/:id/feedback and consolidated into a warehouse for interviewer analytics. Aggregating indexes is specific to Firebolt and Feedback to Lever — each maps to any object or custom field on the other side.
Engines Compute resources that must be running for a sync to read or write. Interviews Scheduled interview panel events with times and interviewers; read for scheduling reporting and time-to-hire metrics, and creatable via the panels endpoint. Engines is specific to Firebolt and Interviews to Lever — each maps to any object or custom field on the other side.
Databases Logical containers holding the tables a sync targets. 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. Databases is specific to Firebolt and Notes and Contacts to Lever — each maps to any object or custom field on the other side.
Tables Managed columnar tables written with SQL; the main sync destination. 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. Tables is specific to Firebolt and Opportunities to Lever — each maps to any object or custom field on the other side.

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

Firebolt Lever Interval-based propagation

DetectionStacksync polls Firebolt 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 Firebolt 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 applied to Firebolt as a row-level write, with types converted between the two schemas.

Rate-limit considerations

  • Firebolt: No fixed request quota; throughput depends on the engine size attached to the workload.
  • 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 Firebolt ⇄ Lever

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

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

How the Firebolt and Lever connectors work

Firebolt

Integration surface
SQL over a REST API, with JDBC, Python, and Node.js SDKs
Authentication
Service account credentials (client ID and secret) exchanged for OAuth 2.0 tokens
Change detection
Polling; Firebolt is an analytics destination and does not expose a change feed
Capabilities
read · write
Rate limits
No fixed request quota; throughput depends on the engine size attached to the workload

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

    Choose tables

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

Firebolt 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 441 integrations available for Firebolt and Lever.

Popular · 8 of 441
All Firebolt 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