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

# Linking Trunk.io as a source

Canonical URL: https://posthog.com/docs/data-pipelines/sources/trunk-io

> **Cloud region:** This page uses US Cloud hosts. For an EU Cloud project, use `https://eu.posthog.com` instead of `https://us.posthog.com` or `https://app.posthog.com` (app host for links).

## On this page

- [Prerequisites](#prerequisites)
- [Adding a data source](#adding-a-data-source)
- [Available tables](#available-tables)
- [Sync modes](#sync-modes)
- [Configuration](#configuration)
- [Supported tables](#supported-tables)
- [Troubleshooting](#troubleshooting)

**Beta release**

This source is currently in **beta**. It works end to end, but you may still hit rough edges. [Let us know](https://us.posthog.com/#panel=support%3Asupport%3Adata_warehouse%3A%3Atrue) if you do.

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

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

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

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.

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](https://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

New Trunk.io sources use API v2 and sync all of the tables below. Existing sources remain on v1 and see only the repository-scoped tables.

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

### Test collection tables (v2 only)

Available for organizations that use [test collections](https://docs.trunk.io/flaky-tests/reference/api-reference).

| Table | Description | Sync method |
| --- | --- | --- |
| `TestCollections` | Test collections in the organization, with test counts and quarantine settings. | Full refresh |
| `Tests` | Tests across every test collection, with current status and quarantine state. | Full refresh |

**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_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](https://posthog.com/docs/data-pipelines/sources.md#sync-methods) for a full explanation of how each mode works and how to choose between them.

## Configuration

| Option | Description |
| --- | --- |
| `API token` **Type:** password **Required:** True |  |
| `Organization slug` **Type:** text **Required:** True | Find this at [https://app.trunk.io/trunk/settings](https://app.trunk.io/trunk/settings) under "Organization Name" > "Slug". |
| `Repository host` **Type:** text **Required:** True |  |
| `Repository owner` **Type:** text **Required:** True |  |
| `Repository name` **Type:** text **Required:** True |  |
| `Merge queue target branch` **Type:** text **Required:** False | Only needed for the `MergeQueuePullRequests` table. A Trunk merge queue covers one target branch, so this is the branch your queue merges into. |

## 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 | — |
| `MergeQueuePullRequests` | Pull requests submitted to the merge queue for one target branch, with queue state and priority. | Incremental, Full refresh | synced\_through | — |
| `TestCollections` | Test collections in the organization, with test counts and quarantine settings. | Full refresh | — | — |
| `Tests` | Tests across every test collection in the organization, with current status and quarantine state. | Full refresh | — | — |

## 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](https://posthog.com/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.