Ashby to MySQL Integration
AI-first ETL from Ashby into MySQL. Governed entities, incremental sync, typed landing tables.
How Datrise loads Ashby into MySQL
Datrise syncs Ashby's candidates, applications, jobs, interviews, offers, and interview feedback into MySQL 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/TIMESTAMP.
Sync is incremental: Datrise uses a watermark on updated-at, applied with INSERT … ON DUPLICATE KEY UPDATE, so re-runs update only what changed. Optional RANGE partitioning by load date. MySQL collation matters for CRM text, so Datrise lands utf8mb4 to preserve emoji and non-Latin characters.
Ideal for operational reporting and app databases already standardized on MySQL.
Endpoints
Ashby: Applicant tracking and recruiting analytics.
MySQL: Widely used OSS relational engine (InnoDB).
How Ashby entities map to MySQL
| Ashby entity | MySQL object | Notes |
|---|---|---|
| candidates | ashby_candidates | id PK · custom fields → JSON columns |
| applications | ashby_applications | id PK · linked to ashby_candidates |
| jobs | ashby_jobs | id PK · linked to ashby_candidates |
| interviews | ashby_interviews | id PK · linked to ashby_candidates |
FAQ
How does Datrise handle Ashby's custom fields in MySQL?
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 MySQL types.
How does the Ashby to MySQL sync stay up to date?
It runs incrementally — Datrise uses a watermark on updated-at, applied with INSERT … ON DUPLICATE KEY UPDATE.
Related pipelines
More destinations for Ashby
Early access
Connect Ashby to MySQL 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.