Automated Synology C2 Backup Freshness Checks
Every morning, WebRun opens Synology C2, checks each backup task and device for its last successful run, counts the restore points available, notes storage usage, sends the team a WhatsApp summary, and pings you on Telegram about any device that has silently stopped backing up.
How do I confirm every device actually backed up last night?
WebRun proves your backups ran every morning. It opens Synology C2, reads the last successful backup time and restore point count for every device, checks storage usage, posts the team a WhatsApp summary, and pings Telegram about any machine whose backup has silently gone stale.
- A failed job is found in the morning, not during a restore
- Every device shows a last successful backup time and restore point count
- Storage filling up surfaces before it blocks a backup
Built for IT administrators · managed service providers · small business owners · operations 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
c2.synology.comin a real browser with your saved login - no setup, no API keys. -
1
Synology C2 - read last successful backup per device
c2.synology.com
WebRun opens Synology C2 to read last successful backup per device. - Open Synology C2 and list every backup task and the device behind it
- Record the last successful backup time for each device
- Flag any device whose last success is older than your freshness window
- Count the restore points available per device, since a task can run and still keep nothing usable
- Note storage usage so a full account is caught before it blocks a backup
- Never delete a restore point or change a task. WebRun reads status only
Done when Every device has a last successful backup time and a restore point count recorded.
-
2
WhatsApp - post the morning backup summary
whatsapp.com
WebRun opens WhatsApp to post the morning backup summary. - Post the morning summary to the team chat: devices protected and devices stale
- List stale devices first with the hours since their last success
- Add the storage usage figure so a filling account is visible early
Done when The team can see this morning whether every machine is protected.
-
3
Telegram - alert on a stale device
telegram.org
WebRun opens Telegram to alert on a stale device. - Send a Telegram alert only when a device has missed its freshness window
- Name the device, the task, and the hours since the last successful backup
- Say whether any restore point still exists for that device
- Stay quiet on a morning where everything backed up cleanly
Done when Whoever owns backups hears about a stale device the same morning.
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
Can it delete restore points or change a task?
No. WebRun reads backup task status, last run times, restore point counts, and storage usage. It never deletes a restore point, edits a task, or changes a retention setting.
Why check restore points as well as the last run?
Because a task can report a run and still leave nothing you can restore from. Counting restore points per device catches the case where the schedule looks healthy but the recovery would fail.
What counts as stale?
Any device whose last successful backup is older than the freshness window you set, for example 26 hours for a nightly job. Those devices lead the summary and trigger the Telegram alert.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.