Skip to content
Human resources ⇄ Database

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

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

Put your workforce data where your apps can reach it: MariaDB and Lever share the same people, positions, and org structure in real time.

Lever is the system of record for the people side of the business — employees, candidates, roles, and the org structure around them. MariaDB is where internal tools, dashboards, provisioning jobs, and analytics actually read and store records. The overlap is the workforce itself: Notes and Contacts, Opportunities, Postings, Requisitions in Lever need to exist as queryable Databases (Schemas), Tables, Views, Columns in MariaDB before an app can act on them. When that bridge is a nightly export or a hand-run CSV, every downstream system spends the day working from a roster that has already moved on.

Stacksync syncs Databases (Schemas), Tables, Views, Columns in MariaDB with Notes and Contacts, Opportunities, Postings, Requisitions in Lever field by field, in real time. You decide which system owns which fields — Lever typically owns identity and org attributes, while operational or computed values can flow back the other way — and Stacksync keeps every copy consistent, matching records on a stable key and resolving conflicts by rules you set.

The result is one live picture of the workforce on both sides: HR keeps its source of truth, and the database keeps a current mirror that internal apps, reports, and access controls can trust without a batch window in between.

Common use cases

  • 01 Two-way sync between a MariaDB application database and a CRM so both systems hold the same customer records
  • 02 Replicate ERP or billing master data into MariaDB databases that power customer-facing applications
  • 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

Computed and operational fields flow back

Values assembled or corrected in MariaDB write onto the matching record in Lever where those fields are writable, keeping the people system enriched.

Mirror people records into the database

Records maintained in Lever land as queryable Databases (Schemas), Tables, Views, Columns in MariaDB, so internal apps and dashboards read live data instead of a periodic export.

One directory of record

When a person record is added, changed, or deactivated in either system, the matching row in the other stays current, ending dual maintenance.

What you can sync between Lever and MariaDB

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 MariaDB objects How this pairing syncs
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. Columns Field-level mapping targets with engine-typed values. Requisitions is specific to Lever and Columns to MariaDB — 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. Primary and Unique Keys Match keys for idempotent upserts. Offers is specific to Lever and Primary and Unique Keys to MariaDB — 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. System-Versioned Tables Temporal tables that retain row history natively, useful for auditing synced changes. Users is specific to Lever and System-Versioned Tables to MariaDB — 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. JSON Columns Semi-structured payloads validated with JSON functions. Stages is specific to Lever and JSON Columns to MariaDB — 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. Stored Procedures Server-side logic that can post-process synced rows. Feedback is specific to Lever and Stored Procedures to MariaDB — each maps to any object or custom field on the other side.
Interviews Scheduled interview panel events with times and interviewers; read for scheduling reporting and time-to-hire metrics, and creatable via the panels endpoint. Databases (Schemas) Top-level namespaces that scope a sync's reads and writes. Interviews is specific to Lever and Databases (Schemas) to MariaDB — each maps to any object or custom field on the other side.

How changes propagate between Lever and MariaDB

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

MariaDB Lever Sub-second propagation

DetectionChanges in MariaDB are captured at the source via change data capture — no polling loop against its API. Database triggers — Stacksync creates deterministic triggers for internal logging and syncing.

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.
  • MariaDB: No API rate limits; throughput is bounded by connection limits and server resources.
What ships with Lever ⇄ MariaDB

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

Track your Lever ⇄ MariaDB 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 MariaDB.

How the Lever and MariaDB 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

MariaDB

Integration surface
SQL wire protocol (MySQL-compatible client/server protocol)
Authentication
Database credentials (connection string or parameters), with optional SSL root certificate upload and optional SSH tunnel (SSH user + host)
Change detection
Database triggers — Stacksync creates deterministic triggers for internal logging and syncing
Capabilities
read · write · CDC
Rate limits
No API rate limits; throughput is bounded by connection limits and server resources
MariaDB setup guide
How it works

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

    Choose tables

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

Lever and MariaDB 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 443 integrations available for Lever and MariaDB.

Popular · 7 of 443
All Lever integrations All MariaDB 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