DatriseAI-first ETL

Day.ai to Supabase Integration

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

How Datrise loads Day.ai into Supabase

Datrise syncs Day.ai's contacts, companies, meetings, opportunities, AI summaries, and relationship signals into Supabase as a typed table per source entity in your Supabase Postgres. Flexible or custom fields land in jsonb columns, and timestamps such as created, updated, and status changes are typed as timestamptz.

Sync is incremental: Datrise uses a watermark on updated-at, applied with INSERT … ON CONFLICT DO UPDATE, so re-runs update only what changed. Optional declarative partitioning for high-volume tables. Datrise lands into a dedicated schema and leaves row-level security to you, so synced tables don't inherit public access by accident.

Ideal for app builders who want CRM data alongside their Supabase product data.

Endpoints

Day.ai: CRM that builds records from meetings and email automatically.

Supabase: Postgres platform with auth, storage, and realtime APIs.

How Day.ai entities map to Supabase

Day.ai entitySupabase objectNotes
contactsday_ai_contactsid PK · custom fields → jsonb columns
companiesday_ai_companiesid PK · linked to day_ai_contacts
meetingsday_ai_meetingsid PK · linked to day_ai_contacts
opportunitiesday_ai_opportunitiesid PK · linked to day_ai_contacts

FAQ

How does Datrise handle Day.ai's custom fields in Supabase?

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

How does the Day.ai to Supabase sync stay up to date?

It runs incrementally — Datrise uses a watermark on updated-at, applied with INSERT … ON CONFLICT DO UPDATE.

Related pipelines

Early access

Connect Day.ai to Supabase 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.