Linking Northflank 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.
This source is currently in alpha. The interface and available tables may change.
The Northflank connector syncs your deployment infrastructure metadata into the PostHog Data warehouse. Northflank is a developer platform for deploying containers, jobs, and managed databases. Once linked, you can join your Northflank projects, services, jobs, addons, and volumes against your product data.
Prerequisites
You need a Northflank account with API access. You can use either a personal or team API token. Create one in your Northflank account settings and grant it read access to the resources you want to sync.
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 Northflank, you'll need:
- API token – a personal or team API token from your Northflank account settings. Grant it read access to the projects and resources you want to sync.
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 Northflank tables use full refresh only, since the API doesn't support server-side timestamp filtering. This means the entire dataset is reloaded on each sync. Because these are infrastructure metadata tables, the data volume is typically small.
Rate limits
Northflank enforces an account rate limit of 1,000 requests per hour. PostHog implements per-project page caps to stay within this limit during syncs.
Configuration
| Option | Type | Required |
|---|---|---|
API token | password | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
projects | A Northflank project — the top-level container that groups services, jobs, addons, and volumes. | Full refresh | — | — |
services | A deployable unit within a project (a combined, build, or deployment service). | Full refresh | — | — |
jobs | A manual or cron job defined within a project. | Full refresh | — | — |
addons | A managed addon (e.g. a database) provisioned within a project. | Full refresh | — | — |
volumes | A persistent volume provisioned within a project. | Full refresh | — | — |
Troubleshooting
- If you get an authorization error, your Northflank API token is invalid or has been revoked. Create a new token in your Northflank account settings, then reconnect.
- If you get a permission error, your Northflank API token doesn't have the required read access. Update the token's permissions, 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.