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

# Linking CircleCI as a source

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

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

## On this page

- [Adding a data source](#adding-a-data-source)
- [Configuration](#configuration)
- [Supported tables](#supported-tables)

![](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 connector syncs your CI/CD data – pipelines, workflows, jobs, projects, deploy components and environments, organization groups, and users – into PostHog.

## Adding a data source

1.  Go to the [sources tab](https://app.posthog.com/data-management/sources) of the data pipeline section in PostHog.
2.  Click **\+ New source** and then click **Link** next to CircleCI.
3.  Next, you need a personal API token from CircleCI. In your [CircleCI user settings](https://app.circleci.com/settings/user/tokens), create a new personal API token and copy it. The token inherits your user permissions and grants read access to your organization's data.
4.  You also need your organization slug in the `vcs/org` format. For example, if your organization is on GitHub with the name `your-org`, the slug is `gh/your-org`. For Bitbucket, use `bb/your-org`. You can find it under **Organization settings** in CircleCI.
5.  Back in PostHog, enter the personal API token and organization slug, then click **Next**.
6.  Select the tables you want to sync, set the sync frequency, then click **Import**.

Once the syncs are complete, you can start using CircleCI data in PostHog.

## Configuration

| Option | Description |
| --- | --- |
| `Personal API token` **Type:** password **Required:** True |  |
| `Organization slug` **Type:** text **Required:** True | The organization slug in `vcs/org` format, e.g. `gh/your-org`. You can find it under **Organization settings** in CircleCI. |

## Supported tables

All tables use **full refresh** syncing, reloading all data on each sync. CircleCI's API does not support incremental syncing.

| Table | Description | Sync method | Incremental field | Primary key |
| --- | --- | --- | --- | --- |
| `pipelines` | A CircleCI pipeline — the full unit of work triggered for a project on a commit. | Full refresh | — | — |
| `workflows` | A workflow — a configured run of jobs within a pipeline. | Full refresh | — | — |
| `jobs` | A job within a workflow — a single execution unit with steps. | Full refresh | — | — |
| `projects` | A CircleCI project — a repository configured to build on CircleCI. | Full refresh | — | — |
| `components` | A deployed component — a deployable unit of a project tracked by CircleCI releases. | Full refresh | — | — |
| `component_versions` | A version of a component deployed to an environment, one row per deploy target. | Full refresh | — | — |
| `environments` | A deploy environment of the organization, the target that component versions are deployed to. | Full refresh | — | — |
| `groups` | A user group in the organization. | Full refresh | — | — |
| `collaborations` | An organization that the token's user is a member of or can collaborate on. | Full refresh | — | — |
| `users` | A CircleCI user referenced as the actor on a workflow. | Full refresh | — | — |