EmailOctopus to Neon Integration

How Datrise loads EmailOctopus into Neon

Datrise syncs EmailOctopus's contacts, lists, campaigns, email events, tags, and automations 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

EmailOctopus: Lightweight email campaigns and list management.

Neon: Serverless Postgres destination with branching and autoscaling.

How EmailOctopus entities map to Neon

EmailOctopus entity	Neon object	Notes
contacts	`emailoctopus_contacts`	id PK · custom fields → jsonb columns
lists	`emailoctopus_lists`	id PK · linked to emailoctopus_contacts
campaigns	`emailoctopus_campaigns`	id PK · linked to emailoctopus_contacts
email events	`emailoctopus_email_events`	timestamptz events

FAQ

How does Datrise handle EmailOctopus'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 EmailOctopus 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 EmailOctopus 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.