Mailjet SMS to MySQL Integration

How Datrise loads Mailjet SMS into MySQL

Datrise syncs Mailjet SMS's SMS messages, recipients, delivery statuses, senders, campaigns, and costs into MySQL as a typed table per source entity. Flexible or custom fields land in JSON columns, and timestamps such as created, updated, and status changes are typed as DATETIME/TIMESTAMP.

Sync is incremental: Datrise uses a watermark on updated-at, applied with INSERT … ON DUPLICATE KEY UPDATE, so re-runs update only what changed. Optional RANGE partitioning by load date. MySQL collation matters for CRM text, so Datrise lands utf8mb4 to preserve emoji and non-Latin characters.

Ideal for operational reporting and app databases already standardized on MySQL.

Endpoints

Mailjet SMS: SMS delivery and message status tracking.

MySQL: Widely used OSS relational engine (InnoDB).

How Mailjet SMS entities map to MySQL

Mailjet SMS entity	MySQL object	Notes
SMS messages	`mailjet_sms_sms_messages`	id PK · custom fields → JSON columns
recipients	`mailjet_sms_recipients`	id PK · linked to mailjet_sms_sms_messages
delivery statuses	`mailjet_sms_delivery_statuses`	DATETIME/TIMESTAMP events
senders	`mailjet_sms_senders`	id PK · linked to mailjet_sms_sms_messages

FAQ

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

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

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

It runs incrementally — Datrise uses a watermark on updated-at, applied with INSERT … ON DUPLICATE KEY UPDATE.

Related pipelines

Early access

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