Automated Postman API Monitor Failure Alerts
Every hour, WebRun opens Postman, checks the results of every scheduled monitor run, saves the failing request and response details to a Google Drive folder for anyone debugging it, and posts an alert to Slack so a failing endpoint gets attention before it becomes a customer facing outage.
How do I get alerted when a Postman API monitor fails?
WebRun checks Postman's scheduled monitor runs every hour for a failed API health check. It saves the failing request and response details to Google Drive for debugging, and posts an alert to Slack, so a broken endpoint gets attention before it turns into a customer facing outage.
- Failing endpoints get flagged within the hour, not at the next outage report
- Every failure's request and response is saved for faster debugging
- The API team channel gets alerts without anyone watching the dashboard
Built for API teams · backend engineering teams · platform 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
identity.getpostman.com/loginin a real browser with your saved login - no setup, no API keys. -
1
Postman - check the API monitor results
postman.com
WebRun opens Postman to check the API monitor results. - Open Postman and check the latest run for each scheduled monitor
- Capture the failing request, response code, and error message for anything that failed
- Skip failures already alerted on this hour
Done when Every newly failed monitor run is listed with its request and response details.
-
2
Google Drive - save the failing response details
drive.google.com
WebRun opens Google Drive to save the failing response details. - Save the failing request and response details to the API monitoring folder
- Name the file with the monitor name and the failure time
- Keep a running folder so failure history is easy to review
Done when Every newly failed monitor run has its details saved to Drive.
-
3
Slack - alert the team
slack.com
WebRun opens Slack to alert the team. - Post an alert to the API team channel naming the failing monitor and endpoint
- Include the response code and error message
- Link the saved details in Drive
Done when The API team channel has an alert for every newly failed monitor run.
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 retry the failing request or change the API?
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 WebRun checks every monitor's latest run each hour.
Where can I find the full failure details later?
In the Drive folder. Every failure's request and response is saved there, so nothing is lost once the Slack alert scrolls by.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.