MailerSend to Redash Integration

How Datrise loads MailerSend into Redash

Datrise syncs MailerSend's messages, templates, domains, delivery events, recipients, and bounces 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

MailerSend: Transactional email delivery and templates.

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

How MailerSend entities map to Redash

MailerSend entity	Redash object	Notes
messages	`mailersend_messages`	id PK · custom fields → flattened columns for query results
templates	`mailersend_templates`	id PK · linked to mailersend_messages
domains	`mailersend_domains`	id PK · linked to mailersend_messages
delivery events	`mailersend_delivery_events`	temporal columns events

FAQ

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

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

Related pipelines

Early access

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