Automated Instatus Downtime Paging
Every few minutes, WebRun checks your Instatus monitors for a failed check, texts the on call engineer through Twilio the instant a component goes down, drafts the incident update with a timeline and likely cause, and saves it to Google Drive for a human to review and publish.
How do I get paged the moment an Instatus monitor goes down?
WebRun checks your Instatus monitors every few minutes for a failed status, texts your on call engineer through Twilio the moment a component goes down, and drafts the incident update with a timeline and likely cause. The draft is saved to Google Drive for a human to review, since publishing a public status update stays a human decision.
- On call engineers hear about an outage within minutes, not from a customer report
- A ready incident draft is waiting the moment someone opens Drive
- No component gets paged twice for the same ongoing outage
Built for DevOps teams · SRE teams · IT operations · SaaS engineering 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
instatus.comin a real browser with your saved login - no setup, no API keys. -
1
Instatus - check monitors for downtime
instatus.com
WebRun opens Instatus to check monitors for downtime. - Check every active monitor in Instatus for a failed status
- Note which component is down and since what time
- Check whether an incident is already open for that component
- Skip components that already have an active incident logged
Done when Every monitor is checked and any new downtime is identified.
-
2
Twilio - text the on call engineer
twilio.com
WebRun opens Twilio to text the on call engineer. - Send a text to the on call engineer the moment a new component goes down
- Include the component name and the time the check first failed
- Do not send a second text for a component already being paged
Done when The on call engineer has been texted about every new outage.
-
3
Google Drive - save the drafted incident update
drive.google.com
WebRun opens Google Drive to save the drafted incident update. - Draft an incident update with a timeline, affected component, and likely cause
- Save the draft to the incident log folder in Google Drive
- Leave it for a human to review and publish on the public status page. Never publish it directly
Done when A reviewable incident draft is saved in Google Drive for every new outage.
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
Will WebRun publish the incident update on my public status page?
No. It only drafts the update and saves it to Google Drive. Publishing to your public status page is always a human decision.
How fast does the on call engineer get paged?
Within minutes of the failed check, since WebRun reviews your Instatus monitors every few minutes and texts immediately on a new outage.
Will it page the same outage twice?
No. It checks whether an incident is already open for that component and skips paging again until it's resolved and a new failure starts.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.