DatriseAI-first ETL

SendGrid Metabase

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

How Datrise loads SendGrid into Metabase

Datrise syncs SendGrid's messages, templates, suppressions, bounces, and engagement events 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

SendGrid: Transactional and marketing email delivery platform.

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

How SendGrid entities map to Metabase

SendGrid entityMetabase objectNotes
messagessendgrid_messagesid PK · custom fields → flattened columns for the question builder
templatessendgrid_templatesid PK · linked to sendgrid_messages
suppressionssendgrid_suppressionsid PK · linked to sendgrid_messages
bouncessendgrid_bouncesid PK · linked to sendgrid_messages

FAQ

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

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

Related pipelines

Early access

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