SendGrid to Redash Integration

How Datrise loads SendGrid into Redash

Datrise syncs SendGrid's messages, contacts, delivery events, bounces, opens, and marketing campaigns into Redash as SQL tables Redash queries and visualizes. Flexible or custom fields land in flattened columns for query results, and timestamps such as created, updated, and status changes are typed as temporal columns.

Sync is incremental: Datrise uses incremental refresh of the connected tables, so re-runs update only what changed. Date-partitioned facts for scheduled queries. Redash caches query results on a schedule, so Datrise keeps tables incrementally fresh so cached dashboards reflect reality.

Ideal for lightweight, query-driven dashboards.

Endpoints

SendGrid: Transactional email delivery and engagement events.

Redash: Open-source SQL client for queries, visualizations, and dashboards.

How SendGrid entities map to Redash

SendGrid entity	Redash object	Notes
messages	`sendgrid_core_messages`	id PK · custom fields → flattened columns for query results
contacts	`sendgrid_core_contacts`	id PK · linked to sendgrid_core_messages
delivery events	`sendgrid_core_delivery_events`	temporal columns events
bounces	`sendgrid_core_bounces`	id PK · linked to sendgrid_core_messages

FAQ

How does Datrise handle SendGrid's custom fields in Redash?

Flexible values are stored as flattened columns for query results, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Redash types.

How does the SendGrid to Redash sync stay up to date?

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

Related pipelines

Early access

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