Automated Integrately Daily Health Digest
Every morning, WebRun opens Integrately, counts yesterday's successful and failed automation runs, saves the failure details as a log file to Google Drive, and texts the ops lead a one-line summary of how many automations need attention.
How do I know if my Integrately automations are failing?
WebRun checks Integrately every morning for yesterday's automation runs, counts successes and failures, saves a dated failure log to Google Drive, and texts the ops lead a one-line health summary. Broken automations get flagged the same morning instead of being discovered days later when a downstream task quietly stopped happening.
- Failed automations get caught the next morning, not days later
- Every failure is logged and dated for reference in Drive
- The ops lead gets one text instead of checking every automation
Built for Operations teams · RevOps · no-code administrators · small IT 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
integrately.comin a real browser with your saved login - no setup, no API keys. -
1
Integrately - count yesterday's runs
integrately.com
WebRun opens Integrately to count yesterday's runs. - Open Integrately and check the run history for the last 24 hours
- Count successful runs and failed runs by automation
- Note the error message for each failure
Done when Every automation's run count and any failures are captured.
-
2
Google Drive - archive the failure log
drive.google.com
WebRun opens Google Drive to archive the failure log. - Open the automations folder in Google Drive
- Save a dated log file listing each failed run and its error
- Keep prior days' logs in place for reference
Done when Today's failure log is saved and dated in Drive.
-
3
Twilio - text the health summary
twilio.com
WebRun opens Twilio to text the health summary. - Send the ops lead a text with the total runs and failure count
- Name the automation with the most failures if any
- Keep the text to one line pointing at the Drive log for detail
Done when The ops lead has a same-morning text with the health summary.
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 it fix or rerun a failed automation?
No. WebRun only counts, logs, and reports failures. Rerunning or fixing an automation is left to your team in Integrately.
Who gets the daily text?
Whoever you set as the ops lead's phone number. The Twilio text is internal and never goes to a customer.
How far back does the log go?
Each day gets its own dated file in Google Drive, and prior days stay in place, so you can compare failure trends over time.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.