Automated Checkly Daily Check Results Digest
Every morning, WebRun opens Checkly, reviews the last 24 hours of API and browser check runs, logs any failures to Airtable with the failing step and affected check, and emails the team a summary of what passed and what needs attention.
How do I get a daily summary of Checkly check results?
WebRun reviews every Checkly API and browser check each morning, logs any failures to Airtable with the failing step and error, and emails the team a digest of pass and fail counts. Checks failing more than one day in a row are called out specifically, so the team always knows what is actually broken without opening the dashboard.
- The team gets one daily rollup instead of a stream of individual check alerts
- Checks failing repeatedly are called out instead of blending into the noise
- A logged history in Airtable makes flaky checks easy to spot over time
Built for Engineering teams · QA teams · site reliability engineers · API platform teams
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.checklyhq.com/loginin a real browser with your saved login - no setup, no API keys. -
1
Checkly - review check results
checklyhq.com
WebRun opens Checkly to review check results. - Open Checkly and review API and browser check runs from the last 24 hours
- Note the pass and fail count per check
- For any failing check, capture the failing step and the error
Done when Every check's pass and fail count from the last 24 hours is recorded with failure details.
-
2
Gmail - log failures
gmail.com
WebRun opens Gmail to email the daily digest. - Draft and send a daily digest email to the engineering team
- List total checks run, how many passed, and which failed with their error
- Flag any check that has failed for more than one day in a row
Done when The team has today's Checkly digest in their inbox.
-
3
Airtable - email the daily digest
airtable.com
WebRun opens Airtable to log failures. - Open the Checkly Failures base
- Add a row for each failed check run with the failing step and error
- Mark any check that has been failing for more than one day
Done when The Airtable base has a row for every check failure 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 retry a failed check or fix the underlying issue?
No. It only reports on check results. Retrying a check or fixing the API or page it tests stays with your engineering team.
Does this replace Checkly's own alerting?
No. It runs alongside your existing Checkly alert channels. It adds a logged history in Airtable and one daily rollup email.
What if a check has been failing for a while?
It gets flagged specifically as failing more than one day in a row, so it stands out from a check that just had a single bad run.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.