Weekly

Get a weekly build health report

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

Runs: Weekly
Apps: CircleCI
AI: Not needed
Access: read

Send this to your assistant

Create a ClickRuntime automation: every Monday at 9am, email me the success rate and median duration of each workflow in my CircleCI projects for the last 7 days.

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

Add to ChatGPT Add to Claude

First time? Adding ClickRuntime to your assistant takes about two minutes.

Why use it

Why teams use this automation

Engineering leads often argue about build health from memory. One person says CI has been slow lately, another says it is fine, and the evidence lives in per-project charts that nobody opens on a regular schedule. Without a steady number, a creeping rise in failures or build time goes unnoticed until developers start complaining.

Once a week, this fetches CircleCI's insights for each project, which include the success rate and the duration of each workflow, and emails the results as one report. It turns a vague feeling about CI into the same set of figures every Monday.

It suits teams with several services, where it is easy to ignore the one pipeline that has been slowly getting worse. The numbers come straight from CircleCI's insights, so they reflect the same pipelines your developers wait on every day, rather than a sample or an estimate.

What you get out of it

Replace opinions with the same numbers weekly
With the same success rates and durations arriving each week, a retro conversation about CI starts from data. People stop arguing about whether builds are slow and decide what to fix first.
Notice slow drift before it hurts
A workflow that grows from 8 to 14 minutes over two months never triggers an alert. A weekly figure makes the trend visible while there is still time to cache dependencies or split a job.
See which service is the weak link
Reporting per project shows where failures concentrate. If one repository has a 70% success rate while the rest sit above 95%, you know where to invest engineering time. That focus is worth more than a general performance push, since you fix the pipeline that hurts most and leave the others alone.
Show the cost of flaky infrastructure
Developer time lost to reruns is hard to prove. A lower success rate printed next to the workflow name gives you something concrete to take to a planning meeting. It also helps justify paying for larger resource classes in the few places where speed genuinely matters to the team.
Keep leadership informed with no extra effort
A tidy weekly email can be forwarded as is to a CTO or director who wants a pulse on delivery speed. Nobody has to build a slide or open a dashboard. It takes the guesswork out of status updates, because the same email that you read can be pasted into a report.

How it works

What happens, step by step

Every Monday, ClickRuntime pulls CircleCI's build insights for each of your projects.
For every workflow it reads last week's success rate, typical run time and number of runs.
You get one email grouped by project, like "build-and-test: 94% success, median 8.2 min, 131 runs".

Before it runs live

Connect CircleCI

What you get

RunsWeekly

Get a weekly build health reporttoday, 9:00Succeeded

Email · Weekly build healthgh/acme/web-app build-and-test: 94% success, median 8.2 min, 131 runs

Build your own

Need it to work differently?

This template is a starting point. Copy the prompt and change it, or describe a different automation from scratch, with your own conditions, more apps or an AI step. 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.

Changes you can ask for

Run it at a different time, more or less often, or only on weekdays
Add an AI step, for example to summarize, sort or draft a reply
Add another app, for example also send it to Slack
Combine it with other CircleCI steps into one automation

Under the hood

The code that runs this automation

This is the Python script that runs each time the automation starts. Your AI assistant writes it for you when you send the prompt, and you allow each step in your assistant. To change how the automation works, describe the change to your assistant and it updates the script for you. For every function it can use, see the script reference.

get_a_weekly_build_health_report.pyexample

from clickruntime import on_trigger, credentials, http, notify

PROJECTS = ["gh/acme/web-app", "gh/acme/api"]

@on_trigger
def run(event):
    headers = {"Circle-Token": credentials.secret("CIRCLECI_TOKEN")}
    lines = []
    for slug in PROJECTS:
        resp = http.get(f"https://circleci.com/api/v2/insights/{slug}/workflows",
                        params={"reporting-window": "last-7-days"}, headers=headers)
        resp.raise_for_status()
        lines.append(slug)
        for wf in resp.json()["items"]:
            m = wf["metrics"]
            lines.append(f"  {wf['name']}: {m['success_rate'] * 100:.0f}% success, "
                         f"median {m['duration_metrics']['median'] / 60:.1f} min, {m['total_runs']} runs")
    notify.email_me("CircleCI build health, last 7 days", "\n".join(lines))
    return {"projects": len(PROJECTS)}

FAQ

Common questions

Which time window does the report cover?

It uses CircleCI's insights for the recent reporting period, so each run reflects the latest week of activity. If you prefer a longer window such as 30 days, you can ask for that and review the changed setup first.

Is it per project or across the whole organization?

It reports on the projects you choose. Each project's workflows are listed with success rate and duration, and your AI assistant can add or remove projects from the list at any time. Projects can be added when a new service is created, so the report grows along with your architecture without a rebuild.

Does it include test results?

No. It focuses on workflow success rate and duration. Individual test failures belong in the flaky tests report, which you can run alongside this one for a fuller view of build quality. Separate reports for different teams can be merged into one Monday email if you prefer to read a single summary.

What permissions does it need?

read. Nothing else in your accounts is used.

Does it need AI?

No. It runs without AI, so it doesn't use your plan's AI allowance.

How many runs does it use?

One run each time it runs (weekly). Checks that find nothing to do and stop right away aren't counted.

Can I change how it works?

Yes. Describe the change to your AI assistant, for example a different schedule, channel or filter. It updates the automation, tests it and tells you what changed.

Weekly