DatriseAI-first ETL

Babelforce to Metabase Integration

AI-first ETL from Babelforce into Metabase. Governed entities, incremental sync, typed landing tables.

How Datrise loads Babelforce into Metabase

Datrise syncs Babelforce's calls, workflows, agents, queues, call events, and dispositions 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

Babelforce: Contact center automation and call workflows.

Metabase: Open-source analytics with questions, dashboards, and embedded insights.

How Babelforce entities map to Metabase

Babelforce entityMetabase objectNotes
callsbabelforce_callsid PK · custom fields → flattened columns for the question builder
workflowsbabelforce_workflowsid PK · linked to babelforce_calls
agentsbabelforce_agentsid PK · linked to babelforce_calls
queuesbabelforce_queuesid PK · linked to babelforce_calls

FAQ

How does Datrise handle Babelforce'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 Babelforce to Metabase sync stay up to date?

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

Related pipelines

Early access

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