DatriseAI-first ETL

Ashby Looker

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

How Datrise loads Ashby into Looker

Datrise syncs Ashby's records, events, and configuration objects into Looker as governed warehouse tables with LookML-ready naming. Flexible or custom fields land in flattened columns (nested fields expanded for modeling), and timestamps such as created, updated, and status changes are typed as date/time dimension columns.

Sync is incremental: Datrise uses incremental refresh of the underlying warehouse tables Looker explores, so re-runs update only what changed. Date-partitioned fact tables for PDT performance. Looker models live in LookML on top of SQL, so Datrise lands clean, stable column names rather than churn that would break your views.

Ideal for governed, version-controlled BI on a warehouse.

Endpoints

Ashby: SaaS or API data source for analytics and warehouse sync.

Looker: Google Cloud BI with LookML semantic models and governed dashboards.

How Ashby entities map to Looker

Ashby entityLooker objectNotes
recordsashby_recordsid PK · custom fields → flattened columns (nested fields expanded for modeling)
eventsashby_eventsdate/time dimension columns events
configuration objectsashby_configuration_objectsid PK · linked to ashby_records

FAQ

How does Datrise handle Ashby's custom fields in Looker?

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

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

It runs incrementally — Datrise uses incremental refresh of the underlying warehouse tables Looker explores.

Related pipelines

Early access

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