Automated CrewAI Run Failure Alerts
Every hour, WebRun opens the CrewAI dashboard, checks crew runs that failed since the last check, exports the run details with the failing agent and error to a dated log in Google Drive, and sends a Twilio text when the same crew has failed twice in a row.
How do I get alerted when a CrewAI run fails?
Every hour, WebRun checks CrewAI for crew runs that failed, exports the run details to a dated log in Google Drive, and sends a Twilio text when the same crew fails twice in a row. This catches a broken multi-agent workflow the same day instead of it silently failing run after run unnoticed.
- A broken crew gets caught the same day, not after repeated silent failures
- A full dated failure history builds up automatically in Drive
- A single isolated failure stays quiet so texts stay trustworthy
Built for AI engineering teams · automation developers · startup technical teams · AI agent builders
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
app.crewai.comin a real browser with your saved login - no setup, no API keys. -
1
CrewAI - check crew run history for failures
crewai.com
WebRun opens CrewAI to check crew run history for failures. - Open the CrewAI dashboard and review runs from the past hour
- Filter to runs that ended in a failure
- Capture the crew name, the agent or task that failed, and the error
Done when Every crew run that failed in the past hour is listed with its cause.
-
2
Google Drive - export the failure log
drive.google.com
WebRun opens Google Drive to export the failure log. - Open the crew run logs folder in Google Drive
- Save this hour's failures as a new dated log
- Keep prior hours in place so recurring crews are visible
Done when This hour's failure log is saved to Drive.
-
3
Twilio - text on a repeat failure
twilio.com
WebRun opens Twilio to text on a repeat failure. - Check whether the same crew has now failed twice in a row
- Send a text through Twilio naming the crew and its errors if it has
- Skip the text for a single isolated failure
Done when A text has gone out only for crews stuck in a repeated failure state.
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
Does it restart the crew or fix the failing agent?
No. WebRun only reads run history and logs what failed. Restarting a run or fixing an agent's task stays with whoever owns the crew.
Why log every failure but only text on repeats?
A single failed run often clears on retry, so it just gets logged. A text goes out once the same crew fails twice in a row, since that usually points to something actually broken.
Can I see which crews fail most over time?
Yes. Every hour's failures are saved as a dated log in Google Drive, so a recurring problem crew is easy to spot across days.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.