Automated Postman Documentation Audits
Every Monday, WebRun opens Postman, walks each workspace and collection, lists the requests missing a description or a saved example response, posts the coverage gaps to Telegram, and leaves a drafted summary email for the collection owner.
How do I find undocumented requests in my Postman collections?
WebRun audits your Postman documentation every Monday. It opens each workspace, walks every collection, and flags requests with no description and no saved example response. It posts the coverage gaps to Telegram and drafts each collection owner a summary email, so partners reading your docs are never guessing at parameters.
- Every undocumented request is named within a week of being added
- Public collections get audited before partners hit them
- Owners get a ready-to-send summary instead of a nagging reminder
Built for API teams · developer relations · platform engineers · technical writers
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 - audit documentation coverage
postman.com
WebRun opens Postman to audit documentation coverage. - Open Postman and list the workspaces you asked it to cover
- Walk every collection and open each request in turn
- Record requests with an empty description, and requests with no saved example response
- Group the gaps by collection and note who owns it
Done when Every request in scope is marked documented or undocumented.
-
2
Telegram - post the coverage gaps
telegram.org
WebRun opens Telegram to post the coverage gaps. - Post a short coverage report per collection: documented requests, gaps, and the percentage covered
- List the undocumented requests by name so they can be picked up straight away
- Put the collections your partners read publicly at the top
Done when This week's documentation gaps are posted in Telegram.
-
3
Gmail - draft the owner a summary
gmail.com
WebRun opens Gmail to draft the owner a summary. - Draft one summary email per collection owner listing their undocumented requests
- Leave every email unsent in Drafts for you to read and send
- Never email an owner or a partner without your approval
Done when A summary email sits in Drafts for each collection owner.
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 email the collection owners on its own?
No. WebRun leaves every owner email unsent in your Gmail drafts. You read it and press send. Only the internal Telegram report is posted automatically.
Does it change anything inside Postman?
No. WebRun only reads your collections and requests. It never edits a request, writes a description, or publishes documentation. The fixes stay yours to make.
Can it cover more than one workspace?
Yes. Name the workspaces you care about and WebRun walks each one every Monday, reporting coverage per collection so public and internal collections stay separate.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.