DatriseAI-first ETL

Outreach ClickHouse

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

How Datrise loads Outreach into ClickHouse

Datrise syncs Outreach's sequence activity, pipeline execution metrics, and sales engagement events 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

Outreach: Sales execution platform for sequence activity and pipeline outcomes.

ClickHouse: Columnar OLAP engine for fast aggregations.

How Outreach entities map to ClickHouse

Outreach entityClickHouse objectNotes
sequence activityoutreach_sequence_activityDateTime64 events
pipeline execution metricsoutreach_pipeline_execution_metricsid PK · linked to outreach_sequence_activity
sales engagement eventsoutreach_sales_engagement_eventsDateTime64 events

FAQ

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