n8n to Supabase Integration
AI-first ETL from n8n into Supabase. Governed entities, incremental sync, typed landing tables.
How Datrise loads n8n into Supabase
Datrise syncs n8n's workflows, executions, nodes, credentials, execution logs, and triggers 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
n8n: Workflow automation across apps and APIs.
Supabase: Postgres platform with auth, storage, and realtime APIs.
How n8n entities map to Supabase
| n8n entity | Supabase object | Notes |
|---|---|---|
| workflows | n8n_workflows | id PK · custom fields → jsonb columns |
| executions | n8n_executions | id PK · linked to n8n_workflows |
| nodes | n8n_nodes | id PK · linked to n8n_workflows |
| credentials | n8n_credentials | id PK · linked to n8n_workflows |
FAQ
How does Datrise handle n8n'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 n8n 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 n8n
Early access
Connect n8n 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.