DatriseAI-first ETL

Autopilot to ClickHouse Integration

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

How Datrise loads Autopilot into ClickHouse

Datrise syncs Autopilot's contacts, journeys, lists, email events, triggers, and custom fields 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

Autopilot: Visual marketing automation and customer journeys.

ClickHouse: Columnar OLAP engine for fast aggregations.

How Autopilot entities map to ClickHouse

Autopilot entityClickHouse objectNotes
contactsautopilot_contactsid PK · custom fields → JSON or Map columns
journeysautopilot_journeysid PK · linked to autopilot_contacts
listsautopilot_listsid PK · linked to autopilot_contacts
email eventsautopilot_email_eventsDateTime64 events

FAQ

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