DatriseAI-first ETL

Day.ai Looker

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

How Datrise loads Day.ai into Looker

Datrise syncs Day.ai's contacts, accounts, deals, activities, and lifecycle events 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

Day.ai: AI-native CRM for relationship data, enrichment, and workflow automation.

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

How Day.ai entities map to Looker

Day.ai entityLooker objectNotes
contactsday_ai_contactsid PK · custom fields → flattened columns (nested fields expanded for modeling)
accountsday_ai_accountsid PK · linked to day_ai_contacts
dealsday_ai_dealsid PK · linked to day_ai_contacts
activitiesday_ai_activitiesdate/time dimension columns events

FAQ

How does Datrise handle Day.ai'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 Day.ai 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 Day.ai 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.