Automated Insomnia API Test Failure Alerts
Every hour, WebRun opens Insomnia, checks the results of every scheduled test suite run, texts the API owner through Twilio the moment a test fails, and saves the failing request and response details to a Google Drive folder so debugging can start with the full context already captured.
How do I get alerted when an Insomnia API test fails?
WebRun checks Insomnia's scheduled test suite runs every hour for a failure. It texts the API owner through Twilio the moment a test fails, and saves the failing request and response to Google Drive, so debugging can start with the full context already captured instead of a broken endpoint reaching production.
- Failing API tests get a text within the hour they fail
- Every failure's full request and response is saved for faster debugging
- Broken endpoints get caught before they reach production
Built for API teams · backend engineering teams · QA engineers · 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.insomnia.rest/app/loginin a real browser with your saved login - no setup, no API keys. -
1
Insomnia - check scheduled test suite runs
insomnia.rest
WebRun opens Insomnia to check scheduled test suite runs. - Open Insomnia and check the latest run for each scheduled test suite
- Capture the failing request, expected response, and actual response for anything that failed
- Skip failures already alerted on this hour
Done when Every newly failed test suite run is listed with its request and response details.
-
2
Twilio - text the API owner
twilio.com
WebRun opens Twilio to text the API owner. - Text the API owner the test suite name and failing request for each new failure
- Keep the message short with just enough detail to start investigating
- Send one message per failure, not a batch
Done when The API owner has a text for every newly failed test suite run.
-
3
Google Drive - save the failing request and response
drive.google.com
WebRun opens Google Drive to save the failing request and response. - Save the failing request and response details to the API testing folder
- Name the file with the test suite name and the failure time
- Keep a running folder so failure history is easy to review
Done when Every newly failed test suite run has its details saved to Drive.
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 fix the failing endpoint or retry the test?
No. WebRun only reports the failure and saves the details. Fixing the endpoint is always done by your engineers.
How fast does a failure get reported?
Within the hour it happens, since every scheduled test suite's latest run is checked each hour.
Where can I find the full failure details later?
In the Drive folder. Every failure's request and response is saved there for as long as you need it.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.