All templates
For platform engineers, SRE teams & data platform owners

Confirm last night's cluster snapshots actually completed

Every morning, WebRun signs in to Elastic Cloud, checks the snapshot history on each deployment for last night's run, records which completed, failed, or were skipped, files a dated evidence note to Google Drive, and writes a backup status page into Notion so a restore is never assumed to be possible.

  • 7-day free trial
  • Under $0.01 per run
  • Cancel anytime
14,115 templates Safe automation No code
Every day at 7:00 AM WebRun
1 Elastic check last night's snapshot runs
2 Google Drive file the dated evidence
3 Notion write the backup status page
Run a sample
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 cloud.elastic.co in a real browser with your saved login - no setup, no API keys.

  2. 1
    Elastic - check last night's snapshot runs
    elastic.co
    WebRun in Elastic: check last night's snapshot runs
    WebRun opens Elastic to check last night's snapshot runs.
    • Sign in to Elastic Cloud and open each deployment you rely on
    • Read the snapshot history for the past 24 hours from its snapshot repository
    • Record for each deployment whether the snapshot completed, failed, is partial, or never started, with the timestamp and duration
    • Note which indices are missing from a partial snapshot, since that is what a restore would leave behind

    Done when Every deployment has last night's snapshot outcome recorded with its timestamp and any missing indices.

  3. 2
    Google Drive - file the dated evidence
    drive.google.com How to Automate Google Drive
    WebRun in Google Drive: file the dated evidence
    WebRun opens Google Drive to file the dated evidence.
    • Save a dated evidence note per day listing every deployment, its snapshot outcome, and the repository used
    • Keep the notes in one folder so a run of successful backups can be shown to an auditor
    • Highlight the days with a failure so the gaps in the record are not buried

    Done when Today's snapshot evidence note is filed in Drive alongside the previous days.

  4. 3
    Notion - write the backup status page
    notion.so How to Automate Notion
    WebRun in Notion: write the backup status page
    WebRun opens Notion to write the backup status page.
    • Update the backup status page with a green or red line per deployment and the last known good snapshot date
    • Put failed and partial snapshots at the top with the error text shown
    • Do not rerun or delete a snapshot. Retrying stays with the platform engineer

    Done when The Notion page states, per deployment, when the last verified good snapshot was taken.

How do I verify that my Elasticsearch snapshots completed successfully?

WebRun signs in to Elastic Cloud every morning and checks each deployment's snapshot history for last night's run, recording what completed, failed, was partial, or never started. It files dated evidence to Google Drive and writes a backup status page in Notion, so you know each day whether a restore is possible.

  • You know each morning whether a restore is genuinely possible
  • Snapshots that never started are caught alongside outright failures
  • A dated evidence trail exists for audits without extra work

Built for platform engineers · SRE teams · data platform owners · DevOps

Run settings

How is each run configured?

Starting pageWhere Chrome opens at the start of each run
cloud.elastic.co
ScheduleRuns automatically on this cadence
Every day at 7:00 AM
DeliveryHow each run's result reaches you
Backup status · Notion
OutputWhat each run produces - A per-deployment snapshot verdict for last night with the timestamp, duration, any missing indices, and the last known good snapshot date.
Text
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 rerun or delete a snapshot?

No. WebRun reads the snapshot history and records what it found. Retrying a failed snapshot, changing a policy, or deleting anything from a repository stays with your engineers.

Does it catch a snapshot that never started?

Yes. A run that simply did not fire is recorded the same way as a failure, because a missing snapshot and a failed snapshot leave you equally unable to restore.

Can it prove backups ran for an audit?

It files a dated evidence note per day in Google Drive listing every deployment and its outcome, so the record is a run of dated notes rather than a memory.

Put this on autopilot.

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