Mailjet SMS to Neon Integration

How Datrise loads Mailjet SMS into Neon

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

Sync is incremental: Datrise uses a watermark on updated-at, applied with INSERT … ON CONFLICT DO UPDATE, so re-runs update only what changed. Optional declarative partitioning by load date. Neon separates compute from storage, so Datrise batches writes to keep autoscaling compute from cold-starting on every small change.

Ideal for serverless Postgres workloads that scale to zero between syncs.

Endpoints

Mailjet SMS: SMS delivery and message status tracking.

Neon: Serverless Postgres destination with branching and autoscaling.

How Mailjet SMS entities map to Neon

Mailjet SMS entity	Neon object	Notes
SMS messages	`mailjet_sms_sms_messages`	id PK · custom fields → jsonb columns
recipients	`mailjet_sms_recipients`	id PK · linked to mailjet_sms_sms_messages
delivery statuses	`mailjet_sms_delivery_statuses`	timestamptz events
senders	`mailjet_sms_senders`	id PK · linked to mailjet_sms_sms_messages

FAQ

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

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

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

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

Related pipelines

Early access

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