DatriseAI-first ETL

Iterable Supabase

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

How Datrise loads Iterable into Supabase

Datrise syncs Iterable's users, campaigns, journeys, message events, and experiments 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

Iterable: Cross-channel marketing automation and journeys.

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

How Iterable entities map to Supabase

Iterable entitySupabase objectNotes
usersiterable_usersid PK · custom fields → jsonb columns
campaignsiterable_campaignsid PK · linked to iterable_users
journeysiterable_journeysid PK · linked to iterable_users
message eventsiterable_message_eventstimestamptz events

FAQ

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