Flag failing CI runs before they block your team
Every hour, WebRun opens GitHub Actions and scans recent workflow runs for failures, looks up the related Linear issue if one is linked, and posts a Slack alert tagging the commit author so the team can act before the failure cascades.
- No credit card
- Under $0.01 per run
- Cancel anytime
How can I automatically flag failing CI runs before they block my team?
Every hour, WebRun opens GitHub Actions and scans recent workflow runs for failures, looks up the related Linear issue if one is linked, and posts a Slack alert tagging the commit author - so blocked work is surfaced immediately and your team can act before the failure cascades.
- Failed builds surfaced within the hour to the responsible author
- Related Linear issues linked automatically for faster context
- CI failures resolved before they block downstream deploys
Built for engineering teams · DevOps engineers · QA engineers · engineering managers
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
github.comin a real browser with your saved login - no setup, no API keys. -
1
GitHub - scan for failed CI workflow runs
github.com
WebRun opens GitHub to scan for failed CI workflow runs. - Open GitHub Actions and filter workflow runs to 'failure' status in the past hour
- For each failed run, read the workflow name, branch, commit SHA, commit message, and author
- Check whether the failure is a known flaky test by comparing against previous failures on the same file
Done when All new CI failures are identified with their branch, author, and failure context.
-
2
Linear - find the linked issue or feature
linear.app
WebRun opens Linear to find the linked issue or feature. - Search Linear for any issue mentioning the branch name or PR number from the failed run
- Read the issue title and current status to add context to the alert
Done when Each CI failure is matched to a Linear issue where one exists.
-
3
Slack - alert the author and team
slack.com How to Automate Slack
WebRun opens Slack to alert the author and team. - Post an alert to #ci-failures with the workflow name, branch, commit, and author
- Include the Linear issue link if one was found
- Tag the commit author so they see it immediately
Done when The author and team have been alerted to every new CI failure.
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 re-run failed CI jobs automatically?
No - re-triggering a workflow is a code action that could mask real problems. WebRun alerts you; you decide whether to rerun or fix.
Does it alert for every failure, even flaky tests?
It flags known flaky tests separately so they don't cry-wolf your team. You define which tests are known-flaky in the plan.
Can it cover multiple repositories?
Yes. Add as many repos as you like and all failures arrive in the same Slack channel with the repo name clearly labelled.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.