Skip to content
Data warehouse ⇄ Human resources

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

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

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

Stacksync syncs Postings, Requisitions, Offers, Users from Lever into tables in Exasol continuously, handling API limits and schema drift as they come. The connection is bi-directional, so values computed in Exasol, 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 Consolidate data from multiple operational databases into Exasol as the central analytics layer.
  • 02 Keep dimension tables such as customers and products aligned with the systems of record.
  • 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

Queryable history for planning and audit

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

Write-back of computed values

Segments, rollups, or risk flags computed in Exasol 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 Exasol as queryable tables, current within seconds instead of a day behind, replacing hand-built extract jobs.

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

Exasol objects Lever objects How this pairing syncs
UDF scripts In-database functions that can transform synced data after load. 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. UDF scripts is specific to Exasol and Requisitions to Lever — each maps to any object or custom field on the other side.
Users and roles Grant read/write access for the dedicated integration account. 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. Users and roles is specific to Exasol and Offers to Lever — each maps to any object or custom field on the other side.
Schemas Namespaces that group the tables a sync reads from or writes into. Users Lever team members (recruiters, hiring managers) with configurable roles; can be created via POST /users, deactivated, and reactivated through the API. Schemas is specific to Exasol and Users to Lever — each maps to any object or custom field on the other side.
Tables Primary sync target; columnar relational tables written with standard SQL. Stages Pipeline stage definitions that Opportunities move through; read to model funnel state and stage transitions in a database. Tables is specific to Exasol and Stages to Lever — each maps to any object or custom field on the other side.
Views Read-only query surfaces often used as curated sources for reverse ETL. Feedback Interview feedback and scorecard forms attached to Opportunities; created via POST /opportunities/:id/feedback and consolidated into a warehouse for interviewer analytics. Views is specific to Exasol and Feedback to Lever — each maps to any object or custom field on the other side.
Virtual schemas Federated views over external sources; useful for deciding what needs physical replication. Interviews Scheduled interview panel events with times and interviewers; read for scheduling reporting and time-to-hire metrics, and creatable via the panels endpoint. Virtual schemas is specific to Exasol and Interviews to Lever — each maps to any object or custom field on the other side.

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

Exasol Lever Interval-based propagation

DetectionStacksync polls Exasol for changes on an incremental schedule, reading only records changed since the previous pass. Polling with timestamp or key columns.

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

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

Rate-limit considerations

  • Exasol: No API quota; concurrency is bounded by cluster resources and session limits.
  • 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 Exasol ⇄ Lever

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

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

How the Exasol and Lever connectors work

Exasol

Integration surface
SQL over JDBC/ODBC drivers and a WebSocket-based client protocol
Authentication
Database credentials (username and password)
Change detection
Polling with timestamp or key columns; Exasol does not expose a transaction-log change feed to clients
Capabilities
read · write
Rate limits
No API quota; concurrency is bounded by cluster resources and session limits

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

    Choose tables

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

Exasol 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 Exasol and Lever.

Popular · 7 of 432
All Exasol 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