n8n to GoodData Integration
AI-first ETL from n8n into GoodData. Governed entities, incremental sync, typed landing tables.
How Datrise loads n8n into GoodData
Datrise syncs n8n's workflows, executions, nodes, credentials, execution logs, and triggers into GoodData as warehouse tables GoodData maps into its logical data model. Flexible or custom fields land in flattened columns, and timestamps such as created, updated, and status changes are typed as date dimensions.
Sync is incremental: Datrise uses incremental refresh of the connected tables, so re-runs update only what changed. Date-partitioned facts. GoodData's LDM maps datasets by keys, so Datrise lands stable primary and foreign id columns to keep the model valid.
Ideal for embedded, multi-tenant analytics.
Endpoints
n8n: Workflow automation across apps and APIs.
GoodData: Composable analytics platform with headless BI and embedded dashboards.
How n8n entities map to GoodData
| n8n entity | GoodData 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 GoodData?
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 GoodData types.
How does the n8n to GoodData sync stay up to date?
It runs incrementally — Datrise uses incremental refresh of the connected tables.
Related pipelines
More destinations for n8n
Early access
Connect n8n to GoodData 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.