DatriseAI-first ETL

Clay to Apache Superset Integration

AI-first ETL from Clay into Apache Superset. Governed entities, incremental sync, typed landing tables.

How Datrise loads Clay into Apache Superset

Datrise syncs Clay's tables, rows, enrichment runs, waterfalls, data sources, and exported lists into Apache Superset as governed SQL tables Superset queries directly. Flexible or custom fields land in flattened columns for the explore UI, and timestamps such as created, updated, and status changes are typed as temporal columns for time-series charts.

Sync is incremental: Datrise uses incremental refresh of the queried tables, so re-runs update only what changed. Date-partitioned tables to keep dashboards responsive. Superset charts run live SQL, so Datrise lands query-friendly, indexed tables rather than wide raw payloads.

Ideal for open-source dashboards over your own database.

Endpoints

Clay: Data enrichment tables that build outbound lists.

Apache Superset: Open-source BI for SQL exploration, charts, and dashboard publishing.

How Clay entities map to Apache Superset

Clay entityApache Superset objectNotes
tablesclay_tablesid PK · custom fields → flattened columns for the explore UI
rowsclay_rowsid PK · linked to clay_tables
enrichment runsclay_enrichment_runsid PK · linked to clay_tables
waterfallsclay_waterfallsid PK · linked to clay_tables

FAQ

How does Datrise handle Clay's custom fields in Apache Superset?

Flexible values are stored as flattened columns for the explore UI, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Apache Superset types.

How does the Clay to Apache Superset sync stay up to date?

It runs incrementally — Datrise uses incremental refresh of the queried tables.

Related pipelines

Early access

Connect Clay to Apache Superset 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.