Automated Coda Automation Failure Alerts
Every morning, WebRun opens Coda, checks the run history on the automations in your docs, finds the ones that failed or stopped firing, prepares a Twilio text for you to approve about the breakages, and posts the full automation status board to Microsoft Teams.
How do I get alerted when a Coda automation stops working?
WebRun opens Coda every morning and reads the run history on the automations in your docs, flagging both outright failures and automations that quietly stopped firing. It queues a Twilio text for your approval and posts the full status board to Microsoft Teams, so a broken process is found the next day rather than next week.
- A broken automation is known the next morning, not next week
- Automations that silently stopped firing are caught alongside errors
- Every failure arrives with its doc, owner, and error text attached
Built for operations leads · no-code builders · revenue ops · internal tools 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
coda.ioin a real browser with your saved login - no setup, no API keys. -
1
Coda - check every automation's run history
coda.io
WebRun opens Coda to check every automation's run history. - Sign in to Coda and open each doc that carries automations
- Read the run history on every automation: last run time and result
- Flag any run that failed, with the error shown against it
- Flag any automation that has not fired within its expected interval, which is the quiet failure
- Note the doc owner so each breakage has someone to go to
- Check whether the table an automation writes to has stopped receiving rows
Done when Every automation has a last run time, a result, and a working or broken mark.
-
2
Twilio - prepare the failure text
twilio.com
WebRun opens Twilio to prepare the failure text. - Prepare a short text naming the broken automations, their docs, and the error
- Send it to your own number only, never to a customer or a wider list
- Leave the message queued for your approval before it sends
- Queue nothing on a morning when every automation ran clean
Done when Any failure has a text waiting for your approval.
-
3
Microsoft Teams - post the status board
microsoft.com
WebRun opens Microsoft Teams to post the status board. - Post the full automation status board to your operations channel
- Show each automation as ran clean, failed, or has not fired, with its doc and owner
- Put the failures at the top with the error text
- Track how many days each broken automation has been down
Done when The team has today's automation status board in Teams.
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 automation?
No. WebRun never runs an automation, edits one, or changes a doc. It reads the run history and reports what broke, and a human fixes and reruns it in Coda.
Does it text anyone besides me?
No. The Twilio message goes to your own number and stays queued until you approve it. The only automatic post is the status board in your own Teams channel.
How does it catch an automation that just stopped firing?
By expected interval, not just errors. If a daily automation has no run in the last day, it is marked as not fired even though nothing errored, which is the failure mode that usually goes unnoticed for a week.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.