CircleCI Insights

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.

Learn more

Connect CircleCI Insights to PostHog to sync your data into the PostHog data warehouse for analysis and modeling.

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 into the PostHog Data warehouse.

You can create a personal API token in your CircleCI user settings. Note that CircleCI retains Insights data for roughly 90 days.

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

Linking CircleCI Insights to PostHog

Go to the Data pipeline page in PostHog
Click New source and select CircleCI Insights
Fill in the required configuration fields
Click Next, select the tables you want to sync, and then press Import

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