Front to ClickHouse Integration

How Datrise loads Front into ClickHouse

Datrise syncs Front's conversations, messages, contacts, inboxes, tags, and teammates 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

Front: Shared inbox for team email and messaging.

ClickHouse: Columnar OLAP engine for fast aggregations.

How Front entities map to ClickHouse

Front entity	ClickHouse object	Notes
conversations	`frontapp_conversations`	id PK · custom fields → JSON or Map columns
messages	`frontapp_messages`	id PK · linked to frontapp_conversations
contacts	`frontapp_contacts`	id PK · linked to frontapp_conversations
inboxes	`frontapp_inboxes`	id PK · linked to frontapp_conversations

FAQ

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