Skip to content
ClickRuntime

Automate CircleCI

Find out how your CircleCI pipelines are doing without watching the dashboard: failed workflows on main, flaky tests, slow jobs and weekly success rates. Failures can be reported as they happen through a project webhook, and the rest arrive as scheduled summaries. Ask your AI assistant for the report you want, check the steps, and it keeps landing in your inbox or channel.

Add to ChatGPTAdd to Claude
Works inChatGPTClaudeClaude CodeCursorCodexVS CodeGemini CLIZedopencodeAny MCP client

Try asking

Create a ClickRuntime automation: give me a webhook link for my CircleCI project. When a workflow on main finishes as failed or error, email me the project, workflow name and a link to it.

Paste it into your assistant. It tells you what it will send or change before it runs live.

Ideas

What you can automate in CircleCI

A ping the moment main breaks, a morning list of yesterday's failures, the tests that pass and fail at random, and a weekly view of which jobs slowed down. These are ready-made starting points. Anything else you can describe works too.
The moment it happens

Get told the moment main fails

When a workflow on main ends in failure or error, you get the workflow name and a direct link right away.

See how it works
Weekly

Get a weekly build health report

Every Monday you see each workflow's success rate and typical duration for the past week.

See how it works
Weekly

Get the week's flaky tests on Friday

Each Friday you get the tests CircleCI has marked as flaky, so someone can fix them.

See how it works
Daily

See yesterday's failures on main each morning

One email each morning lists the workflows on main that failed the day before, with links, and needs no webhook.

See how it works
Weekly

Find the jobs that got slower this week

Each week you see which jobs in a workflow got slower or less reliable compared with the week before.

See how it works Your own logic

Any other automation you can describe in words

Your own rules, schedule and AI steps with CircleCI, plus any other app. Describe it and your assistant builds it.

See how to build your own

Build your own

Build any CircleCI automation you can describe

The ideas above are ready-made starting points, not a fixed list. Describe what CircleCI should do in your own words, with your conditions, other apps or an AI step, and your assistant writes it, tests it and runs it on ClickRuntime.

  • Your own rules

    Conditions, thresholds, filters and exceptions, written the way you'd explain them to a colleague.

  • Any number of apps

    One automation can read from one app and update several others. Over 248 apps are ready, and anything with an API works too.

  • AI where it helps

    Summaries, classification, extraction and drafts use ClickRuntime's built-in AI, with no extra key.

  • On a schedule or on each event

    Runs as often as every 5 minutes, or the moment an app sends an event, and keeps track of what it already handled.

For example, ask your assistant

Every morning, check CircleCI for pipelines on main that failed overnight and send me the job names and failing step.

When a CircleCI workflow fails on main, post the project, branch and author to Slack.

Every week, pull CircleCI build times and failure rates per project, log them in Google Sheets, and post the slowest workflows to Slack.

Beyond chat

Have CircleCI work when you're not in the chat

Connecting CircleCI to ChatGPT or Claude lets you ask about it while you chat. ClickRuntime handles the part that should happen on its own: checks on a schedule and actions on each new event, set up from the same chat and running after you close it.

Setup

Connect CircleCI

CircleCI connects with a personal API token from your own user settings. It acts with your access to every project you can see, since CircleCI does not offer narrower tokens for its v2 API.

CircleCI

Developer / CI/CD

  1. In CircleCI, open User Settings and go to Personal API Tokens.
  2. Click Create New Token, give it a name such as clickruntime-reports, and copy the token.
  3. In the ClickRuntime dashboard, open Connections & secrets and save the token as a secret for CircleCI.

Good to know

CircleCI limits that affect automations

  • A personal token carries your full CircleCI access with no scoping, so consider creating it from an account that only sees the projects you want reported.
  • Project tokens do not work with the v2 API; only personal tokens do.
  • CircleCI webhooks send only workflow-completed and job-completed events, so instant alerts are limited to finished workflows and jobs.
  • The instant failure alert needs a webhook added once in the project settings, while the daily failure digest works without one.

FAQ

Questions about automating CircleCI

What can ClickRuntime see in CircleCI?
Everything your personal token can see: pipelines, workflows, jobs, insights and test results for the projects you have access to. The ready automations only read; none of them start or cancel builds.
Will I hear about a broken build straight away?
Yes, if you add a webhook to the project for completed workflows. Each event is checked for a failed or errored status on the branch you choose. Without a webhook, use the morning digest instead.
Where does the flaky test list come from?
From CircleCI's own insights, which marks tests that both passed and failed on the same code. The weekly email lists them for the project you name.
Can I keep the token from touching every project?
Not through the token itself, since v2 has no scoped tokens. The practical option is a CircleCI user that only belongs to the projects you want covered.
Is an AI key needed for build reports?
No. The reports are counts, links and comparisons. If you want a short written summary of the week, it comes from the AI included in your ClickRuntime plan.
Is this a CircleCI connector for ChatGPT or Claude?
Not for chatting with CircleCI data. A chat connector lets your assistant read and change CircleCI while you're in the conversation. ClickRuntime is for the work that should happen without you: you set up an automation from the chat once, and it keeps running on a schedule or on each CircleCI event.

Related pages

Keep exploring

Tell your assistant what CircleCI should do

Free plan. No credit card.

Add to ChatGPTAdd to Claude