DatriseAI-first ETL

Ashby to PlanetScale Integration

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

How Datrise loads Ashby into PlanetScale

Datrise syncs Ashby's candidates, applications, jobs, interviews, offers, and interview feedback 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

Ashby: Applicant tracking and recruiting analytics.

PlanetScale: Serverless MySQL platform with safe schema workflows.

How Ashby entities map to PlanetScale

Ashby entityPlanetScale objectNotes
candidatesashby_candidatesid PK · custom fields → JSON columns
applicationsashby_applicationsid PK · linked to ashby_candidates
jobsashby_jobsid PK · linked to ashby_candidates
interviewsashby_interviewsid PK · linked to ashby_candidates

FAQ

How does Datrise handle Ashby'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 Ashby 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 Ashby 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.