n8n to ClickHouse Integration
AI-first ETL from n8n into ClickHouse. Governed entities, incremental sync, typed landing tables.
How Datrise loads n8n into ClickHouse
Datrise syncs n8n's workflows, executions, nodes, credentials, execution logs, and triggers 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
n8n: Workflow automation across apps and APIs.
ClickHouse: Columnar OLAP engine for fast aggregations.
How n8n entities map to ClickHouse
| n8n entity | ClickHouse object | Notes |
|---|---|---|
| workflows | n8n_workflows | id PK · custom fields → JSON or Map columns |
| executions | n8n_executions | id PK · linked to n8n_workflows |
| nodes | n8n_nodes | id PK · linked to n8n_workflows |
| credentials | n8n_credentials | id PK · linked to n8n_workflows |
FAQ
How does Datrise handle n8n'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 n8n 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
More destinations for n8n
More sources for ClickHouse
Early access
Connect n8n 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.