Keep your request collection matching the API spec
Every Monday, WebRun opens your Insomnia workspace, reads the API specification and the requests in the collection beside it, lists the endpoints in the spec with no matching request and the requests pointing at paths the spec no longer has, opens a Trello card for each gap, and sends you a WhatsApp summary.
- No credit card
- Under $0.01 per run
- Cancel anytime
How do I keep an API request collection in sync with the spec?
WebRun opens your Insomnia workspace every Monday and compares the API specification against the requests saved in the collection. It lists endpoints with no request and requests pointing at paths the spec dropped, opens a Trello card per gap, and sends the summary to WhatsApp, so the collection stays trustworthy.
- New endpoints get a request the week they ship
- Requests pointing at removed paths are retired, not left to confuse
- The collection stays trustworthy for everyone on the team
Built for backend developers · API 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 - compare the collection with the spec
insomnia.rest
WebRun opens Insomnia to compare the collection with the spec. - Sign in to Insomnia and open the workspace your team shares
- Read the API specification and list every path and method it defines
- Read the collection and list every request with its path, method, and environment
- Note endpoints in the spec with no request against them, and requests whose path is no longer in the spec
- Read only. WebRun never edits, adds, or deletes a request in the shared collection
Done when Every difference between the spec and the collection is listed.
-
2
Trello - open a card per gap
trello.com How to Automate Trello
WebRun opens Trello to open a card per gap. - Open a card on your API board for each missing or stale request
- Put the path, the method, and which side it is missing from on the card
- Label cards as new endpoint, renamed path, or removed endpoint
- Close cards from previous weeks whose gap no longer exists
Done when The API board has one open card per outstanding gap.
-
3
WhatsApp - summarise the drift
whatsapp.com How to Automate WhatsApp
WebRun opens WhatsApp to summarise the drift. - Send yourself a short summary: endpoints missing from the collection and requests pointing nowhere
- Name the paths rather than just counting them
- Note anything that appeared for the first time this week, since that usually follows a release
- Leave every change to a developer. WebRun reports drift and never edits the collection
Done when You have this week's drift summary in WhatsApp.
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 change the shared collection?
No. WebRun reads the spec and the requests and reports the differences. Adding, renaming, and deleting requests stay developer actions, so a collection your whole team relies on is never rewritten by an automation.
Does it send requests to my API?
No. It compares definitions only: the paths and methods in the spec against the paths and methods saved in the collection. Nothing is executed against any environment.
What if the spec is the thing that is wrong?
WebRun reports drift in both directions, so a request pointing at a path the spec never documented shows up too. Which side to fix is left to you.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.