Automated FastComet Backup Verification Digest
Every morning, WebRun opens the FastComet cPanel dashboard for every hosting account, checks whether last night's automatic backup completed and its size, archives a verification log as a file in Google Drive, and posts a daily digest to Slack naming any account whose backup failed or did not run.
How do I confirm my FastComet backups are actually completing?
Every morning, WebRun checks every FastComet hosting account's cPanel dashboard for whether last night's automatic backup completed and its size. It archives a verification log to Google Drive and posts a Slack digest naming any account whose backup failed or did not run, so a missed backup gets caught the next morning, not during a restore.
- A failed backup is caught the next morning, not discovered during a restore
- A dated archive proves backups were actually running, not just scheduled
- Slack stays quiet on days every account's backup completed normally
Built for web agencies · hosting resellers · site administrators · FastComet customers
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.fastcomet.comin a real browser with your saved login - no setup, no API keys. -
1
FastComet - check whether last night's backup completed
fastcomet.com
WebRun opens FastComet to check whether last night's backup completed. - Open the cPanel dashboard for every FastComet hosting account
- Check whether last night's automatic backup completed and note its size
- Flag any account whose backup failed, is missing, or is smaller than expected
Done when Every account's backup status is captured for last night.
-
2
Google Drive - archive the verification log
drive.google.com
WebRun opens Google Drive to archive the verification log. - Compile a verification log listing every account and its backup status
- Save it as a new file in the FastComet folder in Google Drive
- Keep a dated file each day so the backup history stays available
Done when Today's backup verification log is archived in Google Drive.
-
3
Slack - post a digest of any failures to Slack
slack.com
WebRun opens Slack to post a digest of any failures to Slack. - Post a digest to Slack naming any account whose backup failed or did not run
- Stay quiet about accounts whose backup completed normally
- Include the last known good backup date for any failed account
Done when Slack has an alert for every backup failure this run, or confirms all clear.
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 rerun a failed backup itself?
No. WebRun only checks whether a backup completed and reports it. Rerunning a backup or contacting FastComet support always stays a step your team takes.
What counts as a backup that did not run?
Any account with no new backup file since the prior check, or one clearly smaller than its typical size, gets flagged rather than assumed to be fine.
Is there a record if I need to prove backups were happening?
Yes. Every day's verification log is archived in Google Drive with a date, building a running record of backup completion over time.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.