n8n to Birst Integration
AI-first ETL from n8n into Birst. Governed entities, incremental sync, typed landing tables.
How Datrise loads n8n into Birst
Datrise syncs n8n's workflows, executions, nodes, credentials, execution logs, and triggers into Birst as warehouse tables for Birst's automated star schema. Flexible or custom fields land in flattened columns, and timestamps such as created, updated, and status changes are typed as date/time dimensions.
Sync is incremental: Datrise uses incremental refresh of the source tables Birst ingests, so re-runs update only what changed. Date-partitioned facts. Birst builds its own semantic layer, so Datrise lands conformed, well-keyed tables it can automate against.
Ideal for networked, governed enterprise BI.
Endpoints
n8n: Workflow automation across apps and APIs.
Birst: Cloud BI with networked analytics and enterprise semantic layers.
How n8n entities map to Birst
| n8n entity | Birst object | Notes |
|---|---|---|
| workflows | n8n_workflows | id PK · custom fields → flattened 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 Birst?
Flexible values are stored as flattened columns, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Birst types.
How does the n8n to Birst sync stay up to date?
It runs incrementally — Datrise uses incremental refresh of the source tables Birst ingests.
Related pipelines
More destinations for n8n
Early access
Connect n8n to Birst 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.