Source connector

n8n connector

n8n integration for databases, warehouses and BI tools

Workflow automation across apps and APIs. Datrise captures n8n entities such as workflows, executions, nodes, credentials, execution logs and triggers, then lands normalized and typed models for warehouse reporting, attribution, and AI workflows.

The n8n Public REST API v1 authenticates with API key, incremental runs key on startedAfter / startedBefore filters on GET /executions.

Of the 6 objects, 5 sync as upserts keyed on the primary key and 1 as append-only streams, so each incremental run moves only what changed since the last watermark. Every object lands in its own table (for example `n8n_workflows`) with a schema derived from the n8n API rather than a flattened CSV, in any of the 43 supported destinations.

Datrise is in early access: pick a destination below to open the n8n pipeline page, and join the waitlist to get the n8n connector with guided onboarding.

Incremental syncSchema-aware mapping43 destinations available

What n8n data Datrise extracts

Each object lands in its own typed table. Sync mode is derived from the object: history-style objects append, everything else upserts.

Object	Landing table	Sync mode
workflows	n8n_workflows	Upsert by primary key, incremental on updated-at
executions	n8n_executions	Upsert by primary key, incremental on updated-at
nodes	n8n_nodes	Upsert by primary key, incremental on updated-at
credentials	n8n_credentials	Upsert by primary key, incremental on updated-at
execution logs	n8n_execution_logs	Append-only, incremental by timestamp
triggers	n8n_triggers	Upsert by primary key, incremental on updated-at

n8n API: setup facts for the connector

Verified against the vendor documentation on 2026-09-02. Unknown values are left blank rather than guessed.

API	n8n Public REST API v1
Authentication	API key — API key (implemented as a JWT) generated in Settings > n8n API, sent as the X-N8N-API-KEY header; Enterprise instances can scope keys to specific resources/actions.
Pagination	cursor — Cursor-based via a returned nextCursor value on list endpoints (workflows, executions, credentials, users, tags, variables); default limit 100, maximum limit 250.
Rate limit	Not published
Incremental cursor	startedAfter / startedBefore filters on GET /executions — Only the Executions endpoint documents date-range filters; Workflows, Credentials and other list endpoints have no updatedAfter filter, so incremental workflow sync must diff full listings.
Webhooks	No
Bulk export	No
Deletes detectable	No

Official API reference

What bites when replicating n8n

Only /executions supports startedAfter/startedBefore date filters; /workflows, /credentials and /users have no updatedAfter equivalent, so tracking workflow changes over time means diffing full listings.
Cursor pagination defaults to 100 results and caps at 250 per page (limit query param) — requesting more silently gets clamped rather than erroring.
n8n's own API isn't available on free-trial Cloud instances; a request against a trial instance fails regardless of a valid API key.
There is no publicly documented rate limit for the API itself: self-hosted Community has none enforced, so bursts above roughly 100 requests/second are only throttled if you add your own reverse-proxy limit (e.g. nginx `limit_req`).

Compare this against every other documented API

Popular destinations for n8n

Choose a destination below to open the ready pipeline page.

A
Airtable
Relational spreadsheet destination for ops and go-to-market teams.
View pipeline
A
Amazon Athena
Serverless SQL over S3 data lake tables.
View pipeline
A
Amazon DynamoDB
Serverless key-value and document store on AWS.
View pipeline
A
Amazon QuickSight
AWS serverless BI with SPICE and embedded analytics.
View pipeline
A
Amazon Redshift
AWS petabyte-scale warehouse with Spectrum.
View pipeline
A
Amazon S3 Data Lake
Object storage landing zone for parquet and snapshots.
View pipeline
A
Apache Superset
Open-source BI for SQL exploration, charts, and dashboard publishing.
View pipeline
A
Azure Data Lake Storage
ADLS Gen2 object storage for analytics workloads.
View pipeline
A
Azure Synapse
Microsoft analytics workspace with SQL pools.
View pipeline

n8n connector FAQ

What n8n data does the connector extract?: 6 objects: workflows, executions, nodes, credentials, execution logs and triggers. Each lands in its own table with types preserved; history-style objects (1: execution logs) load as append-only streams.
Is the n8n integration incremental?: Yes. After the initial full load, every run reads only records changed since the last watermark (updated-at or event timestamp) and applies an upsert or an append depending on the object.
Where can I load n8n data?: Into 43 destinations: relational databases, cloud warehouses, data lakes, spreadsheets and BI tools. Each n8n → destination pair has its own page with the object-to-table mapping.

Related sources

Other sources in the same category, each with its own connector page.

Early access

Launch your n8n pipeline with guided onboarding

Join the waitlist to get priority access for n8n integrations with guided setup, schema-aware mapping, and production-grade incremental sync.