Mailjet SMS to DuckDB Integration

How Datrise loads Mailjet SMS into DuckDB

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

Sync is incremental: Datrise uses rewrites changed entities into the local database (or Parquet) on each run, so re-runs update only what changed. Hive-partitioned Parquet by load date when exporting. DuckDB is single-writer and embedded, so Datrise produces a consistent file snapshot rather than concurrent streaming writes.

Ideal for local and notebook analytics without standing up a server.

Endpoints

Mailjet SMS: SMS delivery and message status tracking.

DuckDB: In-process analytics database for fast local OLAP.

How Mailjet SMS entities map to DuckDB

Mailjet SMS entity	DuckDB object	Notes
SMS messages	`mailjet_sms_sms_messages`	id PK · custom fields → JSON or STRUCT columns
recipients	`mailjet_sms_recipients`	id PK · linked to mailjet_sms_sms_messages
delivery statuses	`mailjet_sms_delivery_statuses`	TIMESTAMP WITH TIME ZONE events
senders	`mailjet_sms_senders`	id PK · linked to mailjet_sms_sms_messages

FAQ

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

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

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

It runs incrementally — Datrise uses rewrites changed entities into the local database (or Parquet) on each run.

Related pipelines

Early access

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