Clay to Metabase Integration
AI-first ETL from Clay into Metabase. Governed entities, incremental sync, typed landing tables.
How Datrise loads Clay into Metabase
Datrise syncs Clay's tables, rows, enrichment runs, waterfalls, data sources, and exported lists into Metabase as clean SQL tables Metabase auto-discovers. Flexible or custom fields land in flattened columns for the question builder, and timestamps such as created, updated, and status changes are typed as temporal columns for trends.
Sync is incremental: Datrise uses incremental refresh of the connected tables, so re-runs update only what changed. Date-partitioned facts for large questions. Metabase auto-scans schemas, so Datrise uses readable table and column names so the no-code UI stays self-explanatory.
Ideal for self-serve questions and dashboards for whole teams.
Endpoints
Clay: Data enrichment tables that build outbound lists.
Metabase: Open-source analytics with questions, dashboards, and embedded insights.
How Clay entities map to Metabase
| Clay entity | Metabase object | Notes |
|---|---|---|
| tables | clay_tables | id PK · custom fields → flattened columns for the question builder |
| 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 Metabase?
Flexible values are stored as flattened columns for the question builder, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Metabase types.
How does the Clay to Metabase sync stay up to date?
It runs incrementally — Datrise uses incremental refresh of the connected tables.
Related pipelines
More destinations for Clay
Early access
Connect Clay to Metabase 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.