Linking LinearB 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 LinearB connector syncs teams, users, services, 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.
Enter your LinearB API key to pull your engineering intelligence and DORA metrics.
Generate an API token from Settings → API Tokens in your LinearB account. The token grants access to your organization's teams, users, services, deployments, and computed metrics.
The Measurements table is only available on LinearB Business and Enterprise plans and is off by default - enable it if your plan includes API metrics access.
You'll be asked for:
- API key
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 LinearB tables are full refresh. Each sync replaces the contents of the table.
Configuration
| Option | Type | Required |
|---|---|---|
API key | password | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
teams | Teams configured in LinearB, including their hierarchy and membership. | Full refresh | — | id |
users | Users and their cross-platform contributor identity mapping in LinearB. | Full refresh | — | id |
services | Services configured in LinearB and the repositories and paths mapped to each. | Full refresh | — | id |
deployments | Deployments recorded in LinearB, used to compute deploy frequency, change failure rate, and MTTR. | Full refresh | — | id |
measurements | Organization-level Git/DORA metrics (cycle time, PR throughput, deploy frequency) rolled up daily for the last 90 days. Requires a LinearB Business or Enterprise plan | Full refresh | — | after, organization_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.