All templates

Automated CtrlS Uptime and DR Digest

Every morning, WebRun opens the CtrlS customer portal, checks every server's uptime for the past 24 hours and the status of disaster recovery replication, archives the full status report as a file in Google Drive, and posts a daily digest to Slack summarizing uptime and replication health across the account.

Deploy this workflow Browse all templates
Runs on WebRun · Strict Lockdown policy
Every day at 7:00 AM WebRunorchestrates each step
1 CtrlS check uptime and DR replication status
2 Google Drive archive the status report
3 Slack post the daily digest to Slack
In short

How do I monitor CtrlS server uptime and disaster recovery status daily?

Every morning, WebRun checks every CtrlS server's uptime over the past 24 hours and its disaster recovery replication status. It archives the full status report to Google Drive and posts a daily digest to Slack, calling out any server with downtime or a replication lag, so server health is visible without a manual portal login.

  • Server health lands in Slack every morning without a portal login
  • A replication lag is flagged the same day, not at the next audit
  • A dated daily archive builds a compliance ready uptime record

Built for IT administrators · enterprise hosting customers · compliance teams · CtrlS customers

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.ctrls.in in a real browser with your saved login - no setup, no API keys.

  2. 1
    CtrlS - check uptime and DR replication status
    ctrls.in
    WebRun in CtrlS: check uptime and DR replication status
    WebRun opens CtrlS to check uptime and DR replication status.
    • Open the CtrlS customer portal and check uptime for every server over the past 24 hours
    • Check disaster recovery replication status for each server that has DR configured
    • Capture any server with downtime or a replication lag

    Done when Uptime and DR replication status is captured for every server.

  3. 2
    Google Drive - archive the status report
    drive.google.com
    WebRun in Google Drive: archive the status report
    WebRun opens Google Drive to archive the status report.
    • Save the full status report as a file in the CtrlS folder in Google Drive
    • Name the file with the date
    • Keep a running archive rather than overwriting the prior report

    Done when Today's status report is archived in Google Drive.

  4. 3
    Slack - post the daily digest to Slack
    slack.com
    WebRun in Slack: post the daily digest to Slack
    WebRun opens Slack to post the daily digest to Slack.
    • Post a daily digest to Slack summarizing uptime and DR replication status across every server
    • Call out any server with downtime or a replication lag in the past 24 hours
    • Keep the message compact enough to scan in seconds

    Done when Slack has today's server health digest.

Run settings

How is each run configured?

Starting pageWhere Chrome opens at the start of each run
www.ctrls.in
ScheduleRuns automatically on this cadence
Every day at 7:00 AM
DeliveryHow each run's result reaches you
Health digest · Slack
OutputWhat each run produces - A daily Slack digest of server uptime and DR replication status, plus an archived status report in Google Drive.
Text + document
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

Does it fix downtime or trigger a DR failover itself?

No. WebRun only reads status and reports it. Triggering a failover or fixing a server always stays a decision your team makes with CtrlS support.

What counts as a replication lag?

Any DR configured server whose replication is behind by more than the window you set, so the digest reflects your own tolerance rather than a generic default.

Is the archived report useful for compliance reporting?

It gives you a dated daily record of uptime and DR status, which is often exactly what an internal compliance review is looking for.

Keep going

Related templates

Automated 000webhost Usage Limit Warnings
Every morning, WebRun checks your 000webhost account for disk and bandwidth usage against the free plan caps, logs the history to Google Sheets, and emails you a warning when you are close to a limit.
000webhost›Google Sheets›Gmail
Automated 101domain Portfolio Renewal Reminders
Every morning, WebRun checks your 101domain portfolio for domains expiring within 30 days, posts the list to Telegram, and texts you directly for anything expiring within 5 days.
101domain›Telegram›Twilio
123 Reg Automated Renewal Handoff
Every morning, WebRun checks 123 Reg for domains and hosting packages renewing within 21 days, posts a Teams alert, and creates a Trello card assigned to whoever manages billing for each one.
123 Reg›Microsoft Teams›Trello

Put this on autopilot.

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

Deploy this workflow Talk to us