DatriseAI-first ETL

Webflow to Supabase Integration

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

How Datrise loads Webflow into Supabase

Datrise syncs Webflow's collections, collection items, sites, fields, form submissions, and publish events 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

Webflow: Visual website builder with a structured CMS.

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

How Webflow entities map to Supabase

Webflow entitySupabase objectNotes
collectionswebflow_collectionsid PK · custom fields → jsonb columns
collection itemswebflow_collection_itemsid PK · linked to webflow_collections
siteswebflow_sitesid PK · linked to webflow_collections
fieldswebflow_fieldsid PK · linked to webflow_collections

FAQ

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