Automated Railway Failed Deployment Alerts
Every hour, WebRun opens Railway, checks every service across your projects for a deployment that failed or a service stuck crash looping, posts a Teams alert naming the project and the error, and creates a Trello card so the fix gets tracked from report to resolved.
How do I get alerted the moment a Railway deployment fails?
Every hour, WebRun checks every service in your Railway projects for a deployment that failed or a service stuck crash looping. It posts a Teams alert naming the project, the service, and the error, and creates a Trello card so the fix gets tracked from report through to resolved instead of getting lost in chat.
- Failed deployments get caught within the hour instead of from a user report
- Every failure has a Trello card, so nothing gets fixed twice or forgotten
- Crash loops are named by project and service, not just a generic alert
Built for indie developers · small engineering teams · startups on Railway · DevOps engineers
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
railway.appin a real browser with your saved login - no setup, no API keys. -
1
Railway - check services for failed deployments
WebRun opens Railway to check services for failed deployments. - Open Railway and check every service across your projects
- Filter to any deployment that failed or any service that is crash looping
- Capture the project, service, and the error from the deploy logs
Done when Every failed or crash looping service is captured with its error.
-
2
Microsoft Teams - alert the team on Teams
WebRun opens Microsoft Teams to alert the team on Teams. - Post a Teams alert to the engineering channel for each failure
- Name the project, the service, and a short version of the error
- Group multiple failures from the same run into one message
Done when The team has a Teams alert for every failure found this run.
-
3
Trello - create a card to track the fix
WebRun opens Trello to create a card to track the fix. - Create a Trello card for each failure on the incidents board
- Include the project, service, and error details on the card
- Leave the card open until someone marks the fix done
Done when Every failure has an open Trello card tracking it to resolution.
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 roll back or redeploy automatically?
No. WebRun only detects and reports the failure. Rolling back, redeploying, or pushing a fix always stays a decision your team makes.
How is this different from Railway's own notifications?
WebRun adds a tracked Trello card to every failure so it cannot get lost in a busy Teams channel, and gives you one place to see it through to fixed.
Will it alert on a deployment that is still in progress?
No. It only reports a deployment once it has actually failed or a service is confirmed crash looping, not while a build is still running.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.