DatriseAI-first ETL

Confluence to Metabase Integration

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

How Datrise loads Confluence into Metabase

Datrise syncs Confluence's spaces, pages, blog posts, comments, attachments, and page versions 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

Confluence: Team wiki and documentation workspace.

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

How Confluence entities map to Metabase

Confluence entityMetabase objectNotes
spacesconfluence_spacesid PK · custom fields → flattened columns for the question builder
pagesconfluence_pagesid PK · linked to confluence_spaces
blog postsconfluence_blog_postsid PK · linked to confluence_spaces
commentsconfluence_commentsid PK · linked to confluence_spaces

FAQ

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

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

Related pipelines

Early access

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