Secoda to Supabase Integration

How Datrise loads Secoda into Supabase

Datrise syncs Secoda's tables, columns, dictionaries, lineage edges, owners, and documentation entries 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

Secoda: Data catalog, lineage, and documentation.

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

How Secoda entities map to Supabase

Secoda entity	Supabase object	Notes
tables	`secoda_tables`	id PK · custom fields → jsonb columns
columns	`secoda_columns`	id PK · linked to secoda_tables
dictionaries	`secoda_dictionaries`	id PK · linked to secoda_tables
lineage edges	`secoda_lineage_edges`	id PK · linked to secoda_tables

FAQ

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