Linking n8n as a source
Let AI connect your sources for you
Skip the manual setup — run this in your project and the wizard auto-detects your databases and APIs and connects them to PostHog.
Contents
This source is currently in alpha. The interface and available tables may change.
The n8n connector syncs workflows, executions, tags, and more into the PostHog data warehouse, so you can analyze them alongside your product data.
Prerequisites
Credentials that can read the data you want to sync. PostHog only reads data, so read access is enough.
Adding a data source
- In PostHog, go to the Sources tab of the data pipeline section.
- Click + New source and click Link next to this source.
- Enter your credentials (see Configuration below) and click Next.
- Select the tables you want to sync, choose a sync method and frequency, then click Import.
Once the syncs are complete, you can start querying this data in PostHog.
Connect your n8n instance to pull your workflow automation data.
Works with n8n Cloud and self-hosted instances. Enter your instance URL (e.g. https://myorg.app.n8n.cloud) and an API key created under Settings > n8n API.
Some tables (users, projects, variables) require an owner/admin key or an Enterprise plan; deselect them if your key can't access them.
You'll be asked for:
- Instance URL: for example
https://myorg.app.n8n.cloud. - API key: for example
n8n_api_....
Sync modes
Each table can be synced in one of several modes, depending on what the source supports:
- Webhook (when available) – the source pushes changes to PostHog in real time. Fastest freshness, lowest ongoing cost, and the only mode that reliably captures updates and deletes.
- Incremental – only new or updated rows are synced on each run, using a cursor field (such as an
updated_attimestamp). Cheaper than a full refresh, but deletes aren't captured. - Append only – new rows are appended using a cursor field; existing rows are never updated. Ideal for immutable, append-only tables like event logs.
- Full refresh – the whole table is reloaded on every sync. Use it when a table has no reliable cursor or when you need deletions reflected.
See sync methods for a full explanation of how each mode works and how to choose between them.
All n8n tables are full refresh. Each sync replaces the contents of the table.
Configuration
| Option | Type | Required |
|---|---|---|
Instance URL | text | Yes |
API key | password | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
workflows | Automation workflows defined in the n8n instance. | Full refresh | — | id |
executions | Individual runs of workflows, one row per execution. | Full refresh | — | id |
tags | Tags used to organize and group workflows. | Full refresh | — | id |
users | Users of the n8n instance. | Full refresh | — | id |
variables | Instance-level environment variables usable across workflows. | Full refresh | — | id |
projects | Projects that group workflows, credentials, and variables. | Full refresh | — | id |
Troubleshooting
- If the connection fails with an authorization error, the API key is wrong, expired, or has been revoked. Create a new one, then reconnect the source.
- If a table syncs no rows, the credential may not have access to that data. Check its permissions, then reconnect the source.
If your sync is failing or data looks wrong, see the Data warehouse troubleshooting guide. If that doesn't help, contact support – we're happy to help.