DatriseAI-first ETL

Ashby to Looker Studio Integration

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

How Datrise loads Ashby into Looker Studio

Datrise syncs Ashby's candidates, applications, jobs, interviews, offers, and interview feedback into Looker Studio as warehouse tables Looker Studio connects to. Flexible or custom fields land in flattened columns for chart fields, and timestamps such as created, updated, and status changes are typed as date dimension columns.

Sync is incremental: Datrise uses incremental refresh of the connected tables, so re-runs update only what changed. Date-partitioned tables to keep extract refresh fast. Looker Studio performs best on pre-aggregated tables, so Datrise lands tidy, report-shaped tables rather than raw API payloads.

Ideal for free, shareable dashboards on Google data sources.

Endpoints

Ashby: Applicant tracking and recruiting analytics.

Looker Studio: Google self-service dashboards and reporting (formerly Data Studio).

How Ashby entities map to Looker Studio

Ashby entityLooker Studio objectNotes
candidatesashby_candidatesid PK · custom fields → flattened columns for chart 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 Looker Studio?

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

How does the Ashby to Looker Studio sync stay up to date?

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

Related pipelines

Early access

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