DatriseAI-first ETL

Gong to Apache Superset Integration

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

How Datrise loads Gong into Apache Superset

Datrise syncs Gong's calls, transcripts, deals, users, trackers, and call topics 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

Gong: Revenue intelligence from recorded sales calls.

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

How Gong entities map to Apache Superset

Gong entityApache Superset objectNotes
callsgong_callsid PK · custom fields → flattened columns for the explore UI
transcriptsgong_transcriptsid PK · linked to gong_calls
dealsgong_dealsid PK · linked to gong_calls
usersgong_usersid PK · linked to gong_calls

FAQ

How does Datrise handle Gong'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 Gong to Apache Superset sync stay up to date?

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

Related pipelines

Early access

Connect Gong 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.