DatriseAI-first ETL

Lever to PlanetScale Integration

AI-first ETL from Lever into PlanetScale. Governed entities, incremental sync, typed landing tables.

How Datrise loads Lever into PlanetScale

Datrise syncs Lever's candidates, opportunities, postings, interviews, offers, and feedback forms into PlanetScale as a typed table per source entity. Flexible or custom fields land in JSON columns, and timestamps such as created, updated, and status changes are typed as DATETIME.

Sync is incremental: Datrise uses a watermark on updated-at, applied with INSERT … ON DUPLICATE KEY UPDATE, so re-runs update only what changed. Vitess sharding by tenant or entity key for very large tables. PlanetScale disallows foreign-key constraints by default, so Datrise models relationships by stable id columns rather than enforced FKs.

Ideal for horizontally scalable MySQL apps on Vitess.

Endpoints

Lever: Applicant tracking and candidate relationship management.

PlanetScale: Serverless MySQL platform with safe schema workflows.

How Lever entities map to PlanetScale

Lever entityPlanetScale objectNotes
candidateslever_candidatesid PK · custom fields → JSON columns
opportunitieslever_opportunitiesid PK · linked to lever_candidates
postingslever_postingsid PK · linked to lever_candidates
interviewslever_interviewsid PK · linked to lever_candidates

FAQ

How does Datrise handle Lever's custom fields in PlanetScale?

Flexible values are stored as JSON columns, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native PlanetScale types.

How does the Lever to PlanetScale sync stay up to date?

It runs incrementally — Datrise uses a watermark on updated-at, applied with INSERT … ON DUPLICATE KEY UPDATE.

Related pipelines

Early access

Connect Lever to PlanetScale the easy way

Skip brittle scripts and manual exports. Join the waitlist to get a guided setup, AI-assisted mapping, and reliable incremental sync for this integration.