CircleCI

What Plutus imports

• Successful workflow runs

Connecting

Method: Personal API Token

1. In CircleCI, click your avatar in the bottom left, then go to User Settings > Personal API Tokens.
2. Click Create New Token, name it, and click Create.
3. Copy the token immediately — CircleCI shows it only once.
4. In Plutus, paste the token into Personal API Token.
5. In Projects to track, enter the project slugs to sync, separated by commas — either gh/your-org/your-repo or circleci/your-org-id/your-project-id format. Plutus syncs up to 10 projects per account.
6. Click Save & connect, then Sync now to pull completed workflows onto your cost charts.

The token must be a personal API token. A project-scoped token is rejected by the CircleCI v2 API this integration uses.

Notes

Only successful workflows become timeline markers, and they are read from the pipeline feed rather than the Insights API — Insights never returns tag-triggered workflows, so a tag-based deploy pipeline would otherwise be invisible. Insights is still used, best-effort, to attach each run’s duration and CircleCI credits as event metadata; it refreshes daily, so runs from the last ~24 hours land without those two fields. Credits are shown as-is and are not converted to money — CircleCI publishes no per-credit price via the API, and its own docs say the Insights figures should not be used for precise credit reporting.