DatriseAI-first ETL

n8n to Metabase Integration

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

How Datrise loads n8n into Metabase

Datrise syncs n8n's workflows, executions, nodes, credentials, execution logs, and triggers 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

n8n: Workflow automation across apps and APIs.

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

How n8n entities map to Metabase

n8n entityMetabase objectNotes
workflowsn8n_workflowsid PK · custom fields → flattened columns for the question builder
executionsn8n_executionsid PK · linked to n8n_workflows
nodesn8n_nodesid PK · linked to n8n_workflows
credentialsn8n_credentialsid PK · linked to n8n_workflows

FAQ

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

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

Related pipelines

Early access

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