Clay to Supabase Integration
AI-first ETL from Clay into Supabase. Governed entities, incremental sync, typed landing tables.
How Datrise loads Clay into Supabase
Datrise syncs Clay's tables, rows, enrichment runs, waterfalls, data sources, and exported lists 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
Clay: Data enrichment tables that build outbound lists.
Supabase: Postgres platform with auth, storage, and realtime APIs.
How Clay entities map to Supabase
| Clay entity | Supabase object | Notes |
|---|---|---|
| tables | clay_tables | id PK · custom fields → jsonb columns |
| rows | clay_rows | id PK · linked to clay_tables |
| enrichment runs | clay_enrichment_runs | id PK · linked to clay_tables |
| waterfalls | clay_waterfalls | id PK · linked to clay_tables |
FAQ
How does Datrise handle Clay'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 Clay 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 Clay
Early access
Connect Clay 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.