DatriseAI-first ETL

PipeRun to ClickHouse Integration

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

How Datrise loads PipeRun into ClickHouse

Datrise syncs PipeRun's deals, contacts, companies, pipeline stages, activities, and sales teams 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

PipeRun: Sales pipeline management for Brazilian revenue teams.

ClickHouse: Columnar OLAP engine for fast aggregations.

How PipeRun entities map to ClickHouse

PipeRun entityClickHouse objectNotes
dealspiperun_dealsid PK · custom fields → JSON or Map columns
contactspiperun_contactsid PK · linked to piperun_deals
companiespiperun_companiesid PK · linked to piperun_deals
pipeline stagespiperun_pipeline_stagesid PK · linked to piperun_deals

FAQ

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