n8n to Neon Integration
AI-first ETL from n8n into Neon. Governed entities, incremental sync, typed landing tables.
How Datrise loads n8n into Neon
Datrise syncs n8n's workflows, executions, nodes, credentials, execution logs, and triggers into Neon as a typed table per source entity. Flexible or custom fields land in jsonb columns, and timestamps such as created, updated, and status changes are typed as timestamptz.
Sync is incremental: Datrise uses a watermark on updated-at, applied with INSERT … ON CONFLICT DO UPDATE, so re-runs update only what changed. Optional declarative partitioning by load date. Neon separates compute from storage, so Datrise batches writes to keep autoscaling compute from cold-starting on every small change.
Ideal for serverless Postgres workloads that scale to zero between syncs.
Endpoints
n8n: Workflow automation across apps and APIs.
Neon: Serverless Postgres destination with branching and autoscaling.
How n8n entities map to Neon
| n8n entity | Neon object | Notes |
|---|---|---|
| workflows | n8n_workflows | id PK · custom fields → jsonb 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 Neon?
Flexible values are stored as jsonb columns, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Neon types.
How does the n8n to Neon sync stay up to date?
It runs incrementally — Datrise uses a watermark on updated-at, applied with INSERT … ON CONFLICT DO UPDATE.
Related pipelines
More destinations for n8n
Early access
Connect n8n to Neon 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.