Get told when main stays red on CircleCI
Every hour, WebRun opens CircleCI, checks the latest pipeline on the main branch of each watched project, notes the failing job and step and who triggered it, posts the status to Microsoft Teams, and texts the on-call engineer through Twilio when main has been red for longer than the window you set.
- No credit card
- Under $0.01 per run
- Cancel anytime
How do I get alerted when the main branch build stays broken?
WebRun watches your CircleCI main branch every hour. It checks each project's latest pipeline, captures the failing job, step, commit and author, posts the status to Microsoft Teams, and texts the on-call engineer through Twilio once main has stayed red longer than your escalation window.
- A red main branch is named in Teams within the hour
- The on-call is texted once per incident, not once per hour
- Every alert names the failing job, step, and commit author
Built for engineering teams · platform engineers · release managers · DevOps on-call rotas
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
app.circleci.comin a real browser with your saved login - no setup, no API keys. -
1
CircleCI - check the main branch pipelines
circleci.com
WebRun opens CircleCI to check the main branch pipelines. - Open CircleCI and check the most recent pipeline on the main branch of each watched project
- For any failure, capture the failing job, the step that failed, the commit, and who triggered it
- Work out how long the branch has been red by looking back through the recent pipeline history
Done when The main branch status and, where red, the failing job and duration are captured for every project.
-
2
Microsoft Teams - post the failing job
microsoft.com How to Automate Microsoft Teams
WebRun opens Microsoft Teams to post the failing job. - Post the red projects to your engineering Teams channel with the failing job and step
- Include the commit, the author, and a link to the CircleCI run
- Stay silent while every watched project is green
Done when Every red project has been posted to the engineering channel with its failing job.
-
3
Twilio - escalate to the on-call engineer
twilio.com How to Automate Twilio
WebRun opens Twilio to escalate to the on-call engineer. - Check whether main has been red longer than your escalation window
- Send an SMS through Twilio to the on-call number on your internal rota naming the project and the failing job
- Send one text per incident, not one per hour, and never rerun or cancel a pipeline
Done when The on-call engineer has been texted once for each branch that stayed red past the window.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Will it rerun or cancel builds for me?
No. WebRun reads CircleCI and reports. Rerunning a workflow, cancelling a pipeline, or reverting a commit stays with your engineers, who get the failing job and commit by text and in Teams.
How long does main have to be red before someone is texted?
You set the window, commonly thirty or sixty minutes. Anything shorter is posted to Teams only, so a quick fix on a flaky job never wakes the on-call engineer.
Will the on-call get a text every hour until it is fixed?
No. WebRun sends one text per incident. Teams keeps the hourly status updated, and a fresh text is only sent once the branch has gone green and then broken again.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.