Automated Koyeb Deploy Failure Alerts
Every hour, WebRun opens the Koyeb dashboard, reads the status of every service's latest build and deploy, texts the on-call engineer through Twilio the moment one fails, and logs the failure details to a Google Drive incident log for the post-mortem.
How do I get alerted immediately when a Koyeb deploy fails?
WebRun checks every Koyeb service's latest build and deploy status every hour. The moment one fails, it texts the on-call engineer through Twilio with the service name and error summary, and logs the failure to a Google Drive incident doc, so a broken deploy gets a same hour human response instead of being discovered by your users.
- Failed deploys get a same hour text to the on call engineer
- Every failure is logged in one place for the post-mortem
- Nothing gets redeployed or rolled back without a human decision
Built for DevOps engineers · backend developers · startups shipping on Koyeb · platform 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
app.koyeb.comin a real browser with your saved login - no setup, no API keys. -
1
Koyeb - check the latest build and deploy status
koyeb.com
WebRun checks the latest build and deploy status in Koyeb. - Open the Koyeb dashboard and read the status of every service's latest deploy
- Flag any build or deploy marked failed
- Capture the service name and the error summary shown
Done when Every service's latest deploy status is checked.
-
2
Twilio - text the on-call engineer
twilio.com
WebRun texts the on-call engineer through Twilio. - Send a text to the on-call engineer for any failed deploy
- Name the service and a one line error summary
- Skip the text if every deploy is healthy
Done when A failed deploy gets a text within the hour it happens.
-
3
Google Drive - log the failure details
drive.google.com
WebRun logs the failure details to Google Drive. - Add an entry to the incident log doc with the service, time, and error summary
- Keep the newest failures at the top
- Leave the actual fix and redeploy to the engineer
Done when Every failure is logged for the post-mortem.
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 redeploy or roll back the service automatically?
No. WebRun only reads deploy status and alerts the on-call engineer. Redeploying, rolling back, or changing the service stays a manual step someone takes in Koyeb.
Will it text me for every deploy, even successful ones?
No. It only texts for a failed build or deploy. Healthy deploys are read and logged silently, no text sent.
Why log to Google Drive instead of just texting?
The text is for the immediate page. The Drive log builds a running incident history so the team can review patterns later, during a post-mortem.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.