Mailjet SMS to Chartio Integration

How Datrise loads Mailjet SMS into Chartio

Datrise syncs Mailjet SMS's SMS messages, recipients, delivery statuses, senders, campaigns, and costs into Chartio as SQL tables a visual-SQL explorer connects to. Flexible or custom fields land in flattened columns for visual SQL, 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. Visual-SQL tools build joins from your schema, so Datrise lands clearly related tables with stable id columns.

Ideal for drag-and-drop charting over a database.

Endpoints

Mailjet SMS: SMS delivery and message status tracking.

Chartio: Cloud BI for exploring warehouse data with drag-and-drop charts.

How Mailjet SMS entities map to Chartio

Mailjet SMS entity	Chartio object	Notes
SMS messages	`mailjet_sms_sms_messages`	id PK · custom fields → flattened columns for visual SQL
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 Chartio?

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

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

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

Related pipelines

Early access

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