Automated Mendix Build Failure Alerts
Every few minutes, WebRun checks your Mendix apps for deployments that failed, files a Trello card with the app, environment, and error, and messages the on-call developer on WhatsApp so a broken build never sits unnoticed.
How do I get notified the moment a Mendix deployment fails?
WebRun checks your Mendix apps every few minutes for deployments that failed. It files a Trello card with the app, environment, and error message, then messages your on-call developer on WhatsApp with a link to the card, so a broken build gets picked up in minutes instead of at the next standup.
- Failed builds get flagged within minutes instead of at the next standup
- Every failure is tracked on one Trello board with its error
- Repeat failures stand out instead of getting buried in new cards
Built for low-code development teams · IT ops · enterprise app teams · DevOps
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
home.mendix.comin a real browser with your saved login - no setup, no API keys. -
1
Mendix - check for failed deployments
WebRun opens Mendix to check for failed deployments. - Open Mendix and check each app's latest deployment status
- Note any environment that shows a failed or errored build
- Capture the app name, environment, and error message
Done when Every failed deployment this run has been identified with its details.
-
2
Trello - file a card with the error
WebRun opens Trello to file a card with the error. - Open the deployments board in Trello
- Create a card for each failed build with the app, environment, and error
- Move any repeat failure to the top of the list
Done when Every failed deployment has a Trello card.
-
3
WhatsApp - alert the on-call developer
WebRun opens WhatsApp to alert the on-call developer. - Message the on-call developer with the app and error summary
- Link to the Trello card for full detail
- Only message your own team's on-call number, never a customer
Done when The on-call developer has been messaged for every failed build.
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 try to redeploy or fix the app itself?
No. It only detects the failure, files the Trello card, and alerts the on-call developer. Redeploying is always a human decision.
Who gets messaged on WhatsApp?
Only the on-call developer's number your team has on file. It is never sent to a customer or anyone outside your team.
What if the same build keeps failing?
Repeat failures are moved to the top of the Trello board so they stand out instead of getting buried under new cards.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.