DatriseAI-first ETL

Ashby to ThoughtSpot Integration

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

How Datrise loads Ashby into ThoughtSpot

Datrise syncs Ashby's candidates, applications, jobs, interviews, offers, and interview feedback into ThoughtSpot as warehouse tables ThoughtSpot indexes for search. Flexible or custom fields land in flattened columns for searchable fields, and timestamps such as created, updated, and status changes are typed as date/time columns.

Sync is incremental: Datrise uses incremental refresh of the indexed tables, so re-runs update only what changed. Date-partitioned facts for live-query performance. ThoughtSpot search relies on clear names and relationships, so Datrise lands well-named, joinable tables.

Ideal for natural-language search analytics over a warehouse.

Endpoints

Ashby: Applicant tracking and recruiting analytics.

ThoughtSpot: Search-driven analytics with AI-assisted insights on warehouse data.

How Ashby entities map to ThoughtSpot

Ashby entityThoughtSpot objectNotes
candidatesashby_candidatesid PK · custom fields → flattened columns for searchable 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 ThoughtSpot?

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

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

It runs incrementally — Datrise uses incremental refresh of the indexed tables.

Related pipelines

Early access

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