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

# Linking Bitrise as a source

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

> **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)
- [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 Bitrise connector pulls your CI data into the PostHog data warehouse, including apps, builds, workflows, and build artifacts, so you can analyze build durations, failure rates, and release cadence alongside your product data.

## Prerequisites

You need a Bitrise account with access to the apps you want to sync, and a personal access token or workspace API token.

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

You need a Bitrise API token:

-   **Personal access token**: create one in your [Bitrise security settings](https://app.bitrise.io/me/account/security). It has access to the same apps as your user.
-   **Workspace API token**: create one from your workspace's settings page. It is scoped to a single workspace and is the more secure option for team use.

Paste the token in the **API token** field and click **Next**.

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

The `builds` table supports incremental sync on `triggered_at`. Note that the Bitrise API only returns builds from roughly the last 200 days, so older builds are not synced.

The `artifacts` table is disabled by default because it makes one API request per build. Enable it only if you need artifact metadata.

The `activities` table is disabled by default because each full refresh pages through the entire account activity history. Enable it only if you need to analyze account-level activity events.

## Configuration

| Option | Type | Required |
| --- | --- | --- |
| `API token` | password | Yes |

## Supported tables

| Table | Description | Sync method | Incremental field | Primary key |
| --- | --- | --- | --- | --- |
| `apps` | An app registered on Bitrise, tying a source code repository to its CI configuration. | Full refresh | — | — |
| `builds` | The Bitrise API only returns builds from roughly the last 200 days | Incremental, Full refresh | triggered\_at | — |
| `workflows` | A workflow defined in an app's Bitrise configuration, one row per app and workflow name. | Full refresh | — | — |
| `artifacts` | Fetches artifacts for every build, one request per build. Disabled by default because of the API cost | Incremental, Full refresh | build\_triggered\_at | — |
| `pipelines` | A pipeline or standalone build run of an app. Pipelines are Bitrise's multi-stage execution unit, running several workflows together. | Incremental, Full refresh | triggered\_at | — |
| `branches` | Only branches that already have builds on Bitrise are listed | Full refresh | — | — |
| `organizations` | A Bitrise organization (workspace) the token's account belongs to. | Full refresh | — | — |
| `organization_members` | A member of a Bitrise organization, one row per organization and member. | Full refresh | — | — |
| `archived_builds` | The Bitrise API returns at most 1000 archived builds per app | Full refresh | — | — |
| `build_requests` | Only open build requests are listed | Full refresh | — | — |
| `activities` | Activity events of the account that owns the API token. Disabled by default because every sync reads the full history | Full refresh | — | — |
| `available_stacks` | A build stack (operating system image with preinstalled tools) that builds can run on. | Full refresh | — | — |

## Troubleshooting

-   **Invalid Bitrise API token**: the token is invalid or has been revoked. Create a new token in your Bitrise security settings and reconnect the source.
-   **Missing builds**: the Bitrise API caps the builds listing at roughly the last 200 days. Builds older than that are not available to sync.

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.