Skip to content
Human resources ⇄ Data warehouse

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

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

Land the people and organization records from Lever in Tinybird 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 Tinybird next to everything else the company measures.

Stacksync syncs Feedback, Interviews, Notes and Contacts, Opportunities from Lever into tables in Tinybird continuously, handling API limits and schema drift as they come. The connection is bi-directional, so values computed in Tinybird, 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 Compute aggregates in Tinybird and write the results back to CRM fields for scoring and routing.
  • 02 Stream CRM activity such as deals and tickets into Tinybird Data Sources to power customer-facing dashboards.
  • 03 When an Opportunity is marked hired, write the candidate and its Offer into an HRIS or onboarding system to start employee provisioning.
  • 04 Consolidate Feedback, Interviews, and Notes into a warehouse for interviewer scorecard and time-to-fill reporting.

Common sync patterns

Write-back of computed values

Segments, rollups, or risk flags computed in Tinybird sync back onto the matching records in Lever, where the HR team sees them in the system they already use.

HR data in the warehouse, minus the pipeline

People and organization records from Lever arrive in Tinybird as queryable tables, current within seconds instead of a day behind, replacing hand-built extract jobs.

Headcount and cost joined with everything else

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

What you can sync between Lever and Tinybird

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.

Lever objects Tinybird objects How this pairing syncs
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. Data Sources ClickHouse-backed tables that receive ingested rows; the write target for syncs into Tinybird. Postings is specific to Lever and Data Sources to Tinybird — each maps to any object or custom field on the other side.
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. Pipes Chained SQL nodes that transform Data Sources into query-ready results. Requisitions is specific to Lever and Pipes to Tinybird — each maps to any object or custom field on the other side.
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. API Endpoints Published Pipe outputs exposed as parameterized HTTP queries; the main read surface. Offers is specific to Lever and API Endpoints to Tinybird — each maps to any object or custom field on the other side.
Users Lever team members (recruiters, hiring managers) with configurable roles; can be created via POST /users, deactivated, and reactivated through the API. Materialized Views Pipes materialized into new Data Sources for pre-aggregation at ingest time. Users is specific to Lever and Materialized Views to Tinybird — each maps to any object or custom field on the other side.
Stages Pipeline stage definitions that Opportunities move through; read to model funnel state and stage transitions in a database. Workspaces Project boundary that scopes Data Sources, Pipes, and tokens for a sync. Stages is specific to Lever and Workspaces to Tinybird — each maps to any object or custom field on the other side.
Feedback Interview feedback and scorecard forms attached to Opportunities; created via POST /opportunities/:id/feedback and consolidated into a warehouse for interviewer analytics. Tokens Scoped credentials that control read and append rights per resource. Feedback is specific to Lever and Tokens to Tinybird — each maps to any object or custom field on the other side.

How changes propagate between Lever and Tinybird

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.

Lever Tinybird 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 Tinybird as a row-level write, with types converted between the two schemas.

Tinybird Lever Interval-based propagation

DetectionStacksync polls Tinybird for changes on an incremental schedule, reading only records changed since the previous pass. Append-oriented ingestion.

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

Rate-limit considerations

  • 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.
  • Tinybird: Subject to the platform's ingestion and query rate limits; batch appends where possible.
What ships with Lever ⇄ Tinybird

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

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

How the Lever and Tinybird connectors work

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

Tinybird

Integration surface
REST API (Events API for ingestion, published query endpoints) with a ClickHouse SQL dialect
Authentication
Scoped auth tokens
Change detection
Append-oriented ingestion; reads are pulled by querying published endpoints, no outbound CDC
Capabilities
read · write
Rate limits
Subject to the platform's ingestion and query rate limits; batch appends where possible.
How it works

How to connect Lever to Tinybird — 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 Lever and Tinybird 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
    Lever connected
    Tinybird connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

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

Lever and Tinybird 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 431 integrations available for Lever and Tinybird.

Popular · 7 of 431
All Lever integrations All Tinybird 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