Mailjet SMS to Mode Integration

How Datrise loads Mailjet SMS into Mode

Datrise syncs Mailjet SMS's SMS messages, recipients, delivery statuses, senders, campaigns, and costs into Mode as warehouse tables Mode queries with SQL. Flexible or custom fields land in flattened columns for SQL and notebooks, and timestamps such as created, updated, and status changes are typed as temporal columns.

Sync is incremental: Datrise uses incremental refresh of the queried tables, so re-runs update only what changed. Date-partitioned facts for report queries. Mode runs analyst-written SQL, so Datrise lands stable, documented tables that won't break saved reports.

Ideal for SQL-first analysis with Python and R notebooks.

Endpoints

Mailjet SMS: SMS delivery and message status tracking.

Mode: Collaborative analytics workspace for SQL, Python, and shared reports.

How Mailjet SMS entities map to Mode

Mailjet SMS entity	Mode object	Notes
SMS messages	`mailjet_sms_sms_messages`	id PK · custom fields → flattened columns for SQL and notebooks
recipients	`mailjet_sms_recipients`	id PK · linked to mailjet_sms_sms_messages
delivery statuses	`mailjet_sms_delivery_statuses`	temporal columns events
senders	`mailjet_sms_senders`	id PK · linked to mailjet_sms_sms_messages

FAQ

How does Datrise handle Mailjet SMS's custom fields in Mode?

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

How does the Mailjet SMS to Mode sync stay up to date?

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

Related pipelines

Early access

Connect Mailjet SMS to Mode 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.