Linking Trunk.io 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 Trunk.io connector syncs flaky test data from your CI pipelines into the PostHog data warehouse, so you can analyze test health and stability alongside your product data.
Prerequisites
You need a Trunk.io account with API access. You'll also need access to the repository you want to sync data from.
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 Trunk.io, you'll need:
- API token – create one in the Trunk app under Settings > Organization > General > API.
- Organization slug – find this at app.trunk.io/trunk/settings under Organization Name > Slug.
- Repository host – for example,
github.com. - Repository owner – the GitHub organization or user that owns the repository.
- Repository name – the name of the repository you want to sync data from.
Available tables
| Table | Description | Sync method |
|---|---|---|
UnhealthyTests | Tests Trunk currently considers flaky or broken, combining both status filters. | Full refresh |
QuarantinedTests | Tests currently quarantined (failures suppressed) in this repository. | Full refresh |
FailingTests | Distinct tests that failed at least once within a given time window. | Incremental |
Incremental tables sync only new or updated records on each run. Full refresh tables reload all data on each 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.
Configuration
| Option | Description |
|---|---|
API tokenType: password Required: True | |
Organization slugType: text Required: True | Find this at https://app.trunk.io/trunk/settings under "Organization Name" > "Slug". |
Repository hostType: text Required: True | |
Repository ownerType: text Required: True | |
Repository nameType: text Required: True |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
UnhealthyTests | Tests Trunk currently considers flaky or broken, combining both status filters. | Full refresh | — | — |
QuarantinedTests | Tests currently quarantined (failures suppressed) in this repository. | Full refresh | — | — |
FailingTests | Distinct tests that failed at least once within a given time window. | Incremental, Full refresh | synced_through | — |
Troubleshooting
- If you see an authentication error, your API token may be invalid or revoked. Create a new token in your Trunk organization settings and reconnect.
- If data isn't syncing, verify that the organization slug and repository details (host, owner, name) are correct.
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.