All templates

Automated OpenDrive Backup Status Digest

Every morning, WebRun opens OpenDrive, checks last night's backup jobs and current storage usage, schedules a same day retry on Google Calendar for any failed job, and posts the full summary to Microsoft Teams.

Runs on WebRun · Strict Lockdown policy
Every day at 7:30 AM WebRunorchestrates each step
1 OpenDrive check backup jobs and storage
2 Google Calendar schedule a retry
3 Microsoft Teams post the summary
In short

How do I get a daily summary of OpenDrive backup and storage status?

WebRun checks OpenDrive every morning for last night's backup job results and current storage usage. It schedules a same day retry on Google Calendar for anything that failed and posts the full summary to Microsoft Teams, so a missed backup or a storage limit gets caught before it becomes a bigger problem.

  • A daily read on backup health without opening OpenDrive
  • Storage limit issues surfaced before they block a backup
  • Retry reminders that clear themselves once fixed

Built for IT admins · small business owners · remote teams · managed service providers

Step by step

What does WebRun do on every run?

The exact actions WebRun takes, in order - in plain language, so you can adjust anything.

  1. WebRun signs in and gets to work

    Opens www.opendrive.com in a real browser with your saved login - no setup, no API keys.

  2. 1
    OpenDrive - check backup jobs and storage
    opendrive.com
    WebRun in OpenDrive: check backup jobs and storage
    WebRun opens OpenDrive to check backup jobs and storage.
    • Open the backup dashboard and check last night's job results
    • Note total storage used against your plan limit
    • Flag any job that failed or was skipped

    Done when Last night's backup results and current storage are confirmed.

  3. 2
    Google Calendar - schedule a retry
    calendar.google.com
    WebRun in Google Calendar: schedule a retry
    WebRun opens Google Calendar to schedule a retry.
    • Add a same day event to retry any failed backup job
    • Note the job name and failure reason on the event
    • Clear the event once the job succeeds

    Done when A retry event exists for every failed job.

  4. 3
    Microsoft Teams - post the summary
    microsoft.com
    WebRun in Microsoft Teams: post the summary
    WebRun opens Microsoft Teams to post the summary.
    • Post the backup and storage summary to the IT channel
    • List any failed jobs first with their reason
    • Include current storage usage against the plan limit

    Done when The team has this morning's summary in Teams.

Run settings

How is each run configured?

Starting pageWhere Chrome opens at the start of each run
www.opendrive.com
ScheduleRuns automatically on this cadence
Every day at 7:30 AM
DeliveryHow each run's result reaches you
Backup digest · Microsoft Teams
OutputWhat each run produces - A daily backup and storage status summary, with a scheduled retry for any failures.
Digest
Setup & safety

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.

Your credentials stay in your own private environment - WebRun never stores your passwords.
Strict Lockdown

Every action is checked against this policy before it runs.

Domains ALLOWLIST
Typed input ALLOW
Shell command BLOCK
File uploads BLOCK
Runs in a contained environment More on policies
Good to know

Questions, answered

Will it retry the failed backup itself?

No. WebRun only reads job results and schedules a reminder. Re-running a backup job is a step your team takes in OpenDrive.

What if storage is close to the plan limit?

It includes current usage in the Teams summary every morning, so a limit issue surfaces before it blocks a backup.

Does the retry reminder repeat once a job succeeds?

No. It reads the live job status each morning, so a job that succeeds on retry clears its calendar event automatically.

Put this on autopilot.

Turn it on in minutes - or have our team set it up for you.