DatriseAI-first ETL

Ashby to Spreadsheets Integration

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

How Datrise loads Ashby into Spreadsheets

Datrise syncs Ashby's candidates, applications, jobs, interviews, offers, and interview feedback into Spreadsheets as a tab per source entity. Flexible or custom fields land in JSON-stringified cells for nested fields, and timestamps such as created, updated, and status changes are typed as ISO-8601 text or serial date cells.

Sync is incremental: Datrise uses refreshes the tab's rows each run, preserving header order, so re-runs update only what changed. Sheets caps out around the low millions of cells, so Datrise lands a curated column set rather than every raw field.

Ideal for lightweight, shareable reporting for non-technical teams.

Endpoints

Ashby: Applicant tracking and recruiting analytics.

Spreadsheets: Business-friendly spreadsheet destination for collaborative analysis.

How Ashby entities map to Spreadsheets

Ashby entitySpreadsheets objectNotes
candidatesashby_candidatesid PK · custom fields → JSON-stringified cells for nested fields
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 Spreadsheets?

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

How does the Ashby to Spreadsheets sync stay up to date?

It runs incrementally — Datrise uses refreshes the tab's rows each run, preserving header order.

Related pipelines

Early access

Connect Ashby to Spreadsheets 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.