n8n to DuckDB Integration
AI-first ETL from n8n into DuckDB. Governed entities, incremental sync, typed landing tables.
How Datrise loads n8n into DuckDB
Datrise syncs n8n's workflows, executions, nodes, credentials, execution logs, and triggers into DuckDB as a typed table per source entity in a DuckDB file. Flexible or custom fields land in JSON or STRUCT columns, and timestamps such as created, updated, and status changes are typed as TIMESTAMP WITH TIME ZONE.
Sync is incremental: Datrise uses rewrites changed entities into the local database (or Parquet) on each run, so re-runs update only what changed. Hive-partitioned Parquet by load date when exporting. DuckDB is single-writer and embedded, so Datrise produces a consistent file snapshot rather than concurrent streaming writes.
Ideal for local and notebook analytics without standing up a server.
Endpoints
n8n: Workflow automation across apps and APIs.
DuckDB: In-process analytics database for fast local OLAP.
How n8n entities map to DuckDB
| n8n entity | DuckDB object | Notes |
|---|---|---|
| workflows | n8n_workflows | id PK · custom fields → JSON or STRUCT 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 DuckDB?
Flexible values are stored as JSON or STRUCT columns, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native DuckDB types.
How does the n8n to DuckDB sync stay up to date?
It runs incrementally — Datrise uses rewrites changed entities into the local database (or Parquet) on each run.
Related pipelines
More destinations for n8n
Early access
Connect n8n to DuckDB 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.