n8n to Spotfire Integration
AI-first ETL from n8n into Spotfire. Governed entities, incremental sync, typed landing tables.
How Datrise loads n8n into Spotfire
Datrise syncs n8n's workflows, executions, nodes, credentials, execution logs, and triggers into Spotfire as warehouse tables or in-memory data for Spotfire analyses. Flexible or custom fields land in flattened columns for visualizations, and timestamps such as created, updated, and status changes are typed as date/time columns.
Sync is incremental: Datrise uses incremental refresh of the connected tables or in-memory data, so re-runs update only what changed. Date-partitioned facts. Spotfire can load data in-memory, so Datrise keeps the backing tables incremental so analyses refresh without full reloads.
Ideal for interactive analytical visualization and data science.
Endpoints
n8n: Workflow automation across apps and APIs.
Spotfire: Visual analytics platform for interactive dashboards and data science workflows.
How n8n entities map to Spotfire
| n8n entity | Spotfire object | Notes |
|---|---|---|
| workflows | n8n_workflows | id PK · custom fields → flattened columns for visualizations |
| 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 Spotfire?
Flexible values are stored as flattened columns for visualizations, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Spotfire types.
How does the n8n to Spotfire sync stay up to date?
It runs incrementally — Datrise uses incremental refresh of the connected tables or in-memory data.
Related pipelines
More destinations for n8n
Early access
Connect n8n to Spotfire 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.