DatriseAI-first ETL

Dixa Apache Superset

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

How Datrise loads Dixa into Apache Superset

Datrise syncs Dixa's conversations, agents, customers, tags, and resolution metrics 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

Dixa: Customer service platform for conversations across channels.

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

How Dixa entities map to Apache Superset

Dixa entityApache Superset objectNotes
conversationsdixa_conversationsid PK · custom fields → flattened columns for the explore UI
agentsdixa_agentsid PK · linked to dixa_conversations
customersdixa_customersid PK · linked to dixa_conversations
tagsdixa_tagsid PK · linked to dixa_conversations

FAQ

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

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

Related pipelines

Early access

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