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

# Linking Netlify as a source - Docs

Copy page

# Linking Netlify as a source - Docs

![](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`

[Learn more](/wizard.md)

![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

**Alpha release**

This source is currently in **alpha**. The interface and available tables may change.

The Netlify connector syncs your Netlify sites, deploys, builds, forms, form submissions, DNS zones, accounts, and members into the PostHog data warehouse for engineering and marketing analytics.

## Prerequisites

You need a Netlify account and a personal access token. The token has full access to the resources your account can reach, so no extra scopes are required.

## 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.

You need a Netlify personal access token. Create one under **User settings > Applications > Personal access tokens** in the [Netlify UI](https://app.netlify.com/user/applications).

> **Note:** Netlify invalidates tokens on password reset. If your team requires SAML SSO, select **Allow access to my SAML-based Netlify team** when generating the token, otherwise Netlify denies the token access to that team's data.

## 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](/docs/cdp/sources.md#sync-methods) for a full explanation of how each mode works and how to choose between them.

All Netlify tables are full refresh only, since the API exposes no server-side timestamp filter.

## Configuration

| Option | Type | Required |
| --- | --- | --- |
| Personal access token | password | Yes |

## Supported tables

| Table | Description | Sync method | Incremental field | Primary key |
| --- | --- | --- | --- | --- |
| sites | A site hosted on Netlify, including its domains, SSL, and published deploy. | Full refresh | — | — |
| deploys | A deploy of a site: a build of the site's content published to Netlify. | Full refresh | — | — |
| builds | A build of a site, producing a deploy. Includes build status and errors. | Full refresh | — | — |
| forms | A form defined on a Netlify site that collects submissions. | Full refresh | — | — |
| submissions | A single submission to a Netlify form, including the submitted field data. | Full refresh | — | — |
| dns_zones | A DNS zone managed by Netlify for a domain. | Full refresh | — | — |
| accounts | A Netlify account (team) the authenticated user is a member of. | Full refresh | — | — |
| members | A member of a Netlify account, fanned out one row per account. | Full refresh | — | — |

The `sites` table includes every site the token can access, across all of your teams. The `builds`, `deploys`, `forms`, and `submissions` tables are fetched per site, and `members` is fetched per account.

## Troubleshooting

-   If the connection fails with an access-denied error, your token may be invalid or revoked (Netlify invalidates tokens on password reset). Create a new token and reconnect.
-   If syncs complete but tables stay empty, the token likely can't access the team that owns your sites. For SAML SSO teams, generate a new token with **Allow access to my SAML-based Netlify team** selected, then reconnect.
-   The `builds`, `deploys`, `forms`, and `submissions` tables stay empty until the `sites` table syncs at least one row, since they're fetched per site.
-   The `dns_zones` table is only populated if your team manages DNS through Netlify.

If your sync is failing or data looks wrong, see the [Data warehouse troubleshooting guide](/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.

### Was this page useful?

HelpfulCould be better