Automated Xano API Error Rate Alerts
Every hour, WebRun opens the Xano workspace, reviews API request logs for every endpoint, flags any endpoint whose error rate is climbing above its normal baseline, posts the details to Telegram, and texts the on-call developer through Twilio when an endpoint crosses your error rate threshold.
How do I get alerted when a Xano API endpoint's error rate spikes?
WebRun reviews every API endpoint in your Xano workspace each hour, calculating the error rate for the recent window and flagging anything climbing above its normal baseline. It posts the details to Telegram and texts the on-call developer through Twilio once an endpoint crosses your set threshold, so a backend problem gets caught before users start complaining.
- Error spikes get caught within the hour instead of from a user complaint
- The on-call developer is texted only when the threshold is genuinely crossed
- Every endpoint gets checked, not just the ones people remember
Built for No-code backend teams · indie developers · startup engineering teams · platform 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
app.xano.comin a real browser with your saved login - no setup, no API keys. -
1
Xano - check endpoints for rising error rates
WebRun checks endpoints for rising error rates in Xano. - Open the workspace and review the request history for every API endpoint
- Calculate the error rate for the recent window
- Flag any endpoint above its normal baseline
Done when Every endpoint has a current error rate reading.
-
2
Telegram - post the error details
WebRun posts the error details in Telegram. - Post each flagged endpoint to the engineering channel
- Include the error rate and a sample error message
- Group repeats of the same endpoint together
Done when The team has every flagged endpoint posted to Telegram.
-
3
Twilio - text the on-call developer
WebRun texts the on-call developer through Twilio. - Text the on-call developer when an endpoint crosses your set threshold
- Name the endpoint and the error rate
- Stay quiet for endpoints still under threshold
Done when The on-call developer is texted only when the threshold is crossed.
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 roll back or change my API automatically?
No. WebRun only reports rising error rates. Rolling back a change or fixing the endpoint stays a manual step for your developers.
What counts as a rising error rate?
An endpoint's error rate climbing above its normal baseline for the recent window, not a single one-off failed request.
Can I set my own alert threshold?
Yes. Set the error rate that should trigger a text and every future check uses that number.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.