Linking Vercel 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 Vercel connector syncs your deployments, projects, teams, domains, and aliases into PostHog, so you can analyze your Vercel data alongside your product data.
Prerequisites
You need a Vercel account with an access token. A read-only token is sufficient. To sync resources owned by a team, you also need the team's ID.
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.
When linking Vercel, you'll need:
- Access token – create one in your Vercel account settings. A read-only token is sufficient.
- Team ID (optional) – to sync resources owned by a team, enter the team's ID, found under Team Settings. Leave it blank to sync resources owned by the token's user.
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.
Configuration
| Option | Type | Required |
|---|---|---|
Access token | password | Yes |
Team ID (optional) | text | No |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
deployments | A Vercel deployment: a single build and release of a project, with its state, target environment, and URL. | Incremental, Full refresh | created | — |
events | A Vercel team activity event: one action taken on the team, such as a deployment being created, a project renamed, or an environment variable changed. Where the other tables hold current state, this one holds the transitions between states. | Incremental, Full refresh | createdAt | — |
projects | A Vercel project: a codebase connected to Vercel with its build, environment, and deployment configuration. | Full refresh | — | — |
teams | A Vercel team the access token can access. | Full refresh | — | — |
domains | A domain registered with or added to Vercel. | Full refresh | — | — |
aliases | An alias mapping a custom or vercel.app URL to a specific deployment. | Full refresh | — | — |
check_runs | A Vercel check run: one pass/fail gate (a build check or CI integration) that ran against a deployment. Where a deployment's state only reports that it failed, check runs report which gate failed. | Full refresh | — | — |
billing_charges | A team's billing usage and cost, one row per charge in the FOCUS v1.3 open cost-and-usage standard at 1-day granularity. | Incremental, Full refresh | charge_period_start | — |
Troubleshooting
- If your access token is invalid or has been revoked, create a new token in your Vercel account settings, then reconnect.
- If your token is not authorized for a resource, check the token's scope and team access, then reconnect.
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.