Automated Raygun Daily Crash and Error Digest
Every morning, WebRun opens Raygun, reviews crash and error groups reported in the last 24 hours across your applications, logs each one to Airtable with its affected users and occurrence count, and emails the dev lead a summary so the team knows what broke overnight.
How do I get a daily summary of Raygun crashes and errors?
WebRun reviews Raygun crash and error groups every morning, logging each one to Airtable with its affected user count and flagging anything new since yesterday. It then emails the dev lead a digest ranked by user impact, so the team knows within minutes of starting the day what actually broke overnight and how many people it hit.
- The dev lead starts the day knowing what broke and how many users it hit
- New crashes are called out separately from ongoing known issues
- A running Airtable log makes recurring crashes easy to track
Built for Mobile and web development teams · engineering managers · QA teams · site reliability engineers
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.raygun.com/loginin a real browser with your saved login - no setup, no API keys. -
1
Raygun - review crash and error groups
- Open Raygun and review crash and error groups reported in the last 24 hours
- Note the affected users and occurrence count for each
- Flag any group that is new since yesterday
Done when Every crash and error group from the last 24 hours is recorded with its impact.
-
2
Gmail - log the error counts
gmail.com
WebRun opens Gmail to email the daily digest. - Draft and send a daily digest email to the dev lead
- List the top error groups by affected users and any new ones
- Flag anything with a sharp jump in occurrences
Done when The dev lead has today's Raygun digest in their inbox.
-
3
Airtable - email the daily digest
airtable.com
WebRun opens Airtable to log the error counts. - Open the Raygun Error Log base
- Add a row for each group with its occurrence count, affected users, and whether it is new
- Keep the running history for trend comparison
Done when The Airtable base has a row for every crash and error group from the last 24 hours.
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 WebRun resolve or deploy a fix for the crash?
No. It only reads and reports on crash and error data. Resolving an issue in Raygun and shipping a fix both stay with your engineering team.
How does it rank which errors matter most?
By the number of affected users over the last 24 hours, so the digest leads with what is hurting the most people, not just the noisiest error.
Does this replace Raygun's own alerting?
No, it runs alongside it. This adds a logged history in Airtable and one daily rollup email on top of whatever alerts Raygun already sends.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.