Get a clear daily backup failure digest before clients notice
Every morning, WebRun opens Datto Autotask, collects all backup job failures and warnings from the past 24 hours across every managed client, and posts your engineering team a prioritized internal digest in Slack grouped by client and severity.
- No credit card
- Under $0.01 per run
- Cancel anytime
How do I get a daily digest of backup failures across all MSP clients?
Every morning, WebRun reviews all backup job results in Datto Autotask from the past 24 hours across every managed client. It posts your engineering team a prioritized internal Slack digest counting failures, warnings, and missed jobs, with critical items flagged and the on-call engineer tagged so data-protection gaps are caught early.
- Engineers see every backup failure before clients notice a problem
- Critical gaps are flagged and the on-call engineer is tagged within minutes of the run
- No backup failure falls through the cracks across a large client base
Built for managed service providers · MSP engineers · IT service managers · managed backup 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
ww4.autotask.netin a real browser with your saved login - no setup, no API keys. -
1
Datto Autotask - collect backup failures and warnings
autotask.com
WebRun opens Datto Autotask to collect backup failures and warnings. - Open Datto Autotask and navigate to the backup monitoring dashboard
- Collect all backup job results from the past 24 hours across all managed client devices
- Separate results into three categories: failures, warnings, and jobs not run
- Capture the client name, device name, backup type, failure reason, and last successful backup date for each issue
- Sort by severity: failures first, then warnings, then missed jobs
Done when Every backup failure, warning, and missed job from the past 24 hours is catalogued with its details.
-
2
Slack - post the prioritized failure digest
slack.com How to Automate Slack
WebRun opens Slack to post the prioritized failure digest. - Post the daily backup digest to the engineering Slack channel
- Lead with a summary count: X failures, Y warnings, Z missed
- List each issue grouped by client, with the device name and failure reason
- Flag any client whose last successful backup was more than 48 hours ago as critical
- Tag the on-call engineer for any critical items
Done when Engineers have the full backup health picture for all clients in Slack.
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
Does it notify clients when their backups fail?
No. The digest is internal, posted to your engineering Slack channel only. Your team decides when and how to inform a client about a backup issue.
What is the difference between a failure and a warning in the digest?
Failures are jobs that did not complete successfully. Warnings are jobs that completed but with issues such as low changed-block counts or extended duration. Both are shown, with failures listed first.
Does it create a ticket in Autotask for failures?
Not by default. The digest is a read-and-report run. If you want automatic ticket creation for critical failures, that can be configured as an additional step during setup.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.