DatriseAI-first ETL

Postmark to ClickHouse Integration

AI-first ETL from Postmark into ClickHouse. Governed entities, incremental sync, typed landing tables.

How Datrise loads Postmark into ClickHouse

Datrise syncs Postmark's messages, servers, delivery events, bounces, opens, and message streams into ClickHouse as a MergeTree table per source entity. Flexible or custom fields land in JSON or Map columns, and timestamps such as created, updated, and status changes are typed as DateTime64.

Sync is incremental: Datrise uses inserts into a ReplacingMergeTree keyed on stable id, so the latest version wins on merge, so re-runs update only what changed. Partition by month and order by (entity id, updated-at) for fast range scans. ClickHouse deduplicates asynchronously on merge, so Datrise uses ReplacingMergeTree and FINAL-safe queries rather than assuming immediate upserts.

Ideal for high-volume event analytics that need sub-second aggregation.

Endpoints

Postmark: Transactional email delivery with detailed events.

ClickHouse: Columnar OLAP engine for fast aggregations.

How Postmark entities map to ClickHouse

Postmark entityClickHouse objectNotes
messagespostmark_app_messagesid PK · custom fields → JSON or Map columns
serverspostmark_app_serversid PK · linked to postmark_app_messages
delivery eventspostmark_app_delivery_eventsDateTime64 events
bouncespostmark_app_bouncesid PK · linked to postmark_app_messages

FAQ

How does Datrise handle Postmark's custom fields in ClickHouse?

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

How does the Postmark to ClickHouse sync stay up to date?

It runs incrementally — Datrise uses inserts into a ReplacingMergeTree keyed on stable id, so the latest version wins on merge.

Related pipelines

Early access

Connect Postmark to ClickHouse 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.