Catch the internal tool that quietly broke
Every morning, WebRun signs in to Retool, reads the run history on every scheduled workflow, picks out the runs that errored or timed out overnight, raises a Trello card per broken workflow with the error text, and posts the failure list to your engineering WhatsApp group.
- No credit card
- Under $0.01 per run
- Cancel anytime
How do I find out when a Retool workflow fails overnight?
WebRun signs in to Retool every morning and reads the run history on your scheduled workflows. It picks out the runs that errored, timed out, or never started, raises a Trello card per broken workflow with the error text, and posts the overnight failures to your engineering WhatsApp group.
- Broken workflows are found at 7am, not when someone reports bad data
- Repeat failures rank above one-off flakes
- One Trello card per workflow instead of a duplicate every morning
Built for internal tools teams · operations engineers · startup CTOs · data 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
login.retool.comin a real browser with your saved login - no setup, no API keys. -
1
Retool - read overnight run history
retool.com
WebRun opens Retool to read overnight run history. - Sign in to Retool and open the run history for each scheduled workflow
- Capture every run since yesterday that errored, timed out, or did not start
- Record the workflow name, the failing block, the error text, and how many consecutive runs have now failed
Done when Every failed or missed workflow run from overnight is captured with its error.
-
2
Trello - raise a card per broken workflow
trello.com How to Automate Trello
WebRun opens Trello to raise a card per broken workflow. - Create a Trello card for each workflow failing, titled with the workflow name and the failing block
- Put the error text, the run time, and the consecutive failure count in the description
- Add to the existing card instead of duplicating when a workflow is already open, and close cards for workflows now passing
Done when Every failing workflow has one open Trello card carrying its latest error.
-
3
WhatsApp - post the overnight failures
whatsapp.com How to Automate WhatsApp
WebRun opens WhatsApp to post the overnight failures. - Post the overnight failure list to your engineering WhatsApp group
- Put workflows failing several runs in a row at the top, since those are broken rather than flaky
- Stay quiet on mornings when every scheduled workflow ran clean
Done when Engineering has this morning's failure list, worst first.
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 rerun or edit a broken workflow?
No. WebRun reads the run history and reports the errors. It never reruns a workflow, edits a query, changes a resource, or deploys an app. A person decides what to fix.
How does it tell a flaky run from a real break?
It counts consecutive failures. A workflow that failed once and then passed is listed as flaky, and one failing several runs in a row is pushed to the top of the WhatsApp message as broken.
Will it flood my Trello board with duplicate cards?
No. A workflow that is already failing gets its existing card updated with the latest error, and cards close automatically once the workflow runs clean again.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.