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

# Linking CircleCI Insights as a source

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

> **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 CircleCI Insights connector syncs workflow metrics, workflow runs, job metrics, 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

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.

Enter your CircleCI personal API token and project slugs to pull pipeline health metrics - workflow and job durations, success rates, credit usage, recent runs, and flaky tests - from the CircleCI Insights API.

You can create a personal API token in your [CircleCI user settings](https://app.circleci.com/settings/user/tokens). Note that CircleCI retains Insights data for roughly 90 days.

You'll be asked for:

-   **Personal API token**
-   **Project slugs**: comma-separated project slugs in `vcs/org/repo` format, e.g. `gh/your-org/your-repo`. You can find a project's slug in its URL on CircleCI.

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

All CircleCI Insights tables are full refresh. Each sync replaces the contents of the table.

## Configuration

| Option | Description |
| --- | --- |
| `Personal API token` **Type:** password **Required:** True |  |
| `Project slugs` **Type:** text **Required:** True | Comma-separated project slugs in `vcs/org/repo` format, e.g. `gh/your-org/your-repo`. You can find a project's slug in its URL on CircleCI. |
| `Reporting window for aggregated metrics` **Type:** select **Required:** False |  |
| `Branch scope` **Type:** select **Required:** False |  |

## Supported tables

| Table | Description | Sync method | Incremental field | Primary key |
| --- | --- | --- | --- | --- |
| `workflow_metrics` | Aggregated metrics for each workflow in a project over the configured reporting window: run counts, success rate, duration percentiles, credits consumed, MTTR, and throughput. | Full refresh | — | project\_slug, name |
| `workflow_summary` | Summary metrics for each workflow in a project, with the trend for each metric against the previous window. Complements workflow\_metrics, which carries the raw aggregates without trends. | Full refresh | — | project\_slug, workflow\_name |
| `workflow_runs` | Individual recent runs of each workflow, with duration, status, branch, and credits consumed. CircleCI retains run-level Insights data for roughly 90 days. | Incremental, Full refresh | created\_at | id |
| `job_metrics` | Aggregated metrics for each job of each workflow in a project over the configured reporting window: run counts, success rate, duration percentiles, credits consumed, and throughput. | Full refresh | — | project\_slug, workflow\_name, name |
| `job_timeseries` | Daily timeseries of metrics for each job in a workflow, giving point-in-time job trends rather than a single window aggregate. Daily buckets are retained for roughly 90 days. The endpoint has no all-branches option, so these rows cover the project's default branch even when the source is set to all branches. | Incremental, Full refresh | timestamp | project\_slug, workflow\_name, name, timestamp |
| `flaky_tests` | Tests CircleCI has detected as flaky in a project: tests that pass and fail across runs with no code change, with where they flake and how often. | Full refresh | — | project\_slug, workflow\_name, job\_name, classname, test\_name |
| `workflow_test_metrics` | Per-test duration and failure metrics for a workflow, covering the tests CircleCI reports as most failed and slowest. Calculated from the workflow's 10 most recent runs, so this is a snapshot rather than a history. | Full refresh | — | project\_slug, workflow\_name, job\_name, classname, test\_name |
| `branches` | The branches Insights holds data for in a project, as a dimension for slicing the other Insights tables by branch. The API returns at most 5,000 branches per project. | Full refresh | — | project\_slug, branch |
| `org_summary_metrics` | Per-project summary metrics and trends across an organization over the configured reporting window, from the org-level Insights summary. Requires the token to have org membership. | Full refresh | — | org\_slug, project\_name |

## Troubleshooting

-   If the connection fails with an authorization error, the personal API token 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](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.