Omnisend → Supabase
AI-first ETL from Omnisend into Supabase. Governed entities, incremental sync, typed landing tables.
How Datrise loads Omnisend into Supabase
Datrise syncs Omnisend's records, events, and configuration objects 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
Omnisend: SaaS or API data source for analytics and warehouse sync.
Supabase: Postgres platform with auth, storage, and realtime APIs.
How Omnisend entities map to Supabase
| Omnisend entity | Supabase object | Notes |
|---|---|---|
| records | omnisend_records | id PK · custom fields → jsonb columns |
| events | omnisend_events | timestamptz events |
| configuration objects | omnisend_configuration_objects | id PK · linked to omnisend_records |
FAQ
How does Datrise handle Omnisend'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 Omnisend 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
More destinations for Omnisend
Early access
Connect Omnisend 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.