DatriseAI-first ETL

Mailgun to Metabase Integration

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

How Datrise loads Mailgun into Metabase

Datrise syncs Mailgun's messages, domains, delivery events, bounces, complaints, and mailing lists 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

Mailgun: Transactional email API with delivery analytics.

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

How Mailgun entities map to Metabase

Mailgun entityMetabase objectNotes
messagesmailgun_messagesid PK · custom fields → flattened columns for the question builder
domainsmailgun_domainsid PK · linked to mailgun_messages
delivery eventsmailgun_delivery_eventstemporal columns for trends events
bouncesmailgun_bouncesid PK · linked to mailgun_messages

FAQ

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

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

Related pipelines

Early access

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