> AI agents: this is one page from PostHog's docs. Full index of Markdown docs for LLMs: https://posthog.com/llms.txt

# Linking n8n as a source

Canonical URL: https://posthog.com/docs/data-pipelines/sources/n8n

> **Cloud region:** This page uses US Cloud hosts. For an EU Cloud project, use `https://eu.posthog.com` instead of `https://us.posthog.com` or `https://app.posthog.com` (app host for links).

## On this page

- [Prerequisites](#prerequisites)
- [Adding a data source](#adding-a-data-source)
- [Sync modes](#sync-modes)
- [Configuration](#configuration)
- [Supported tables](#supported-tables)
- [Troubleshooting](#troubleshooting)

![](https://res.cloudinary.com/dmukukwp6/image/upload/texture_tan_9608fcca70)

![](https://res.cloudinary.com/dmukukwp6/image/upload/texture_tan_dark_a92b0e022d)

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.

`npx @posthog/wizard warehouse`

![PostHog Wizard hedgehog](https://res.cloudinary.com/dmukukwp6/image/upload/wizard_3f8bb7a240.png)

![](https://res.cloudinary.com/dmukukwp6/image/upload/wizard_3f8bb7a240.png)Let AI connect your sources for you

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

1.  In PostHog, go to the [Sources tab](https://app.posthog.com/data-management/sources) of the data pipeline section.
2.  Click **\+ New source** and click **Link** next to this source.
3.  Enter your credentials (see [Configuration](#configuration) below) and click **Next**.
4.  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, project\_users, folders) 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_at` timestamp). 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](https://posthog.com/docs/data-pipelines/sources.md#sync-methods) for a full explanation of how each mode works and how to choose between them.

Most n8n tables are full refresh – each sync replaces the contents of the table. The `insights_summary` table is incremental, syncing new days since the last run.

## 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 |
| `project_users` | Members of each project, one row per user and project, with the user's role in that project. | Full refresh | — | projectId, id |
| `folders` | Folders that organize workflows inside each project. | Full refresh | — | projectId, id |
| `test_runs` | Evaluation test runs of each workflow. | Full refresh | — | workflowId, id |
| `test_cases` | Per-case results of each evaluation test run. | Full refresh | — | testRunId, id |
| `insights_summary` | Headline execution metrics for the instance, one row per UTC day. | Incremental, Full refresh | startDate | date |

## 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](https://posthog.com/docs/data-warehouse/troubleshooting.md). If that doesn't help, [contact support](https://us.posthog.com/#panel=support%3Asupport%3Adata_warehouse%3A%3Atrue) – we're happy to help.