Chase down devices that stopped backing up to Carbonite
Every morning, WebRun opens Carbonite, checks the last backup time for every device, flags anything stale for 3 or more days, schedules a same-day follow-up in Google Calendar, and posts the stale device list to Microsoft Teams.
- No credit card
- Under $0.01 per run
- Cancel anytime
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
www.carbonite.comin a real browser with your saved login - no setup, no API keys. -
1
Carbonite - find devices overdue for backup
carbonite.com
WebRun opens Carbonite to find devices overdue for backup. - Open the Carbonite dashboard and check last backup time for every device
- Flag any device that has not completed a backup in 3 or more days
- Note the device name and how long it has been stale
Done when Every stale device is listed with its last successful backup time.
-
2
Google Calendar - schedule a follow-up
calendar.google.com How to Automate Google Calendar
WebRun opens Google Calendar to schedule a follow-up. - Create a follow-up event to check the device remotely or in person
- Set it for the same day so the check does not slip
- Include the device name and days stale in the event details
Done when A follow-up event exists for every stale device.
-
3
Microsoft Teams - alert IT
microsoft.com How to Automate Microsoft Teams
WebRun opens Microsoft Teams to alert IT. - Post the stale device list to the IT channel
- Sort the list by days stale, oldest first
- Flag anything over 7 days as high priority
Done when IT has today's stale backup list in Teams.
How do I catch a Carbonite device that has stopped backing up?
WebRun checks every device in Carbonite each morning for a completed backup in the last 3 days, and flags anything overdue. It schedules a same-day follow-up in Google Calendar and posts the stale device list to Microsoft Teams, sorted oldest first, so a quietly failing backup gets checked before it becomes a real data loss risk.
- Stale backups are caught within days, not during a data loss
- IT gets a same-day follow-up scheduled automatically
- The oldest, highest-risk devices are flagged first
Built for IT admins · managed service providers · small business office managers
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 try to fix the backup itself?
No. It only flags stale devices and schedules a follow-up. Diagnosing or fixing the backup is left to IT.
How long does a device have to be stale before it is flagged?
Three or more days without a completed backup. Anything over 7 days is marked high priority in the Teams list.
Does it create a new calendar event every day for the same device?
It creates one follow-up event per stale device per run, so a device that gets fixed drops off the list the next day.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.