Automated Bugsnag New Error Triage
Every morning, WebRun signs in to Bugsnag, filters the inbox to errors first seen in the last 24 hours, records the event count, affected users, and release stage for each, opens a Trello card per new error, and messages the on-call developer on WhatsApp about the one hitting the most users.
How do I make sure new crashes get triaged the day they appear?
WebRun triages new Bugsnag errors every morning. It filters your inbox to errors first seen in the last 24 hours, captures event counts, affected users, and release stage, opens a Trello card for each, and messages the on-call developer on WhatsApp about the error hitting the most users.
- New crashes get a card and an owner the same day they appear
- The highest user-impact error reaches on-call before standup
- Recurring known errors do not clutter the board with duplicates
Built for engineering teams · mobile developers · on-call engineers · QA leads
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.bugsnag.com/user/loginin a real browser with your saved login - no setup, no API keys. -
1
Bugsnag - find errors first seen yesterday
bugsnag.com
WebRun opens Bugsnag to find errors first seen yesterday. - Sign in to Bugsnag and open the error inbox for each project
- Filter to errors first seen in the last 24 hours and still unresolved
- Capture the error class, message, file location, event count, affected user count, and release stage
- Rank the list by affected users, then by event count
Done when Every error that appeared yesterday is captured and ranked by user impact.
-
2
Trello - open a triage card per error
trello.com
WebRun opens Trello to open a triage card per error. - Open your engineering board and check the triage list for an existing card per error class
- Create a card for each genuinely new error, titled with the error class and file
- Put the event count, affected users, release stage, and the Bugsnag link in the description
- Label anything above your user-impact threshold as high priority
Done when Every new error has one triage card and no duplicates were created.
-
3
WhatsApp - flag the worst one to on-call
whatsapp.com
WebRun opens WhatsApp to flag the worst one to on-call. - Message the on-call developer in your internal WhatsApp thread
- Lead with the error hitting the most users, its count, and the release it appeared in
- Give the total number of new errors and link the Trello triage list
Done when On-call knows the day's worst new error and the total new count.
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 resolve or ignore errors in Bugsnag?
No. WebRun reads the inbox and reports. Marking an error resolved, ignored, or snoozed is always done by a developer inside Bugsnag.
Does it create duplicate cards for a recurring error?
No. It checks the triage list for an existing card matching that error class first, so only genuinely new errors get a card.
How does it decide what is worst?
It ranks by the number of affected users first and event count second, so a crash hitting many people outranks a noisy loop affecting one session.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.