Inspiration
After an invoice bump one month, the customer wanted to know when the tax rate changed.
What it does
Notify tax rate changes.
How we built it
Postman collection and a scheduled monitor
Challenges we ran into
Not being able to persist collectionVariables across monitor-runs using pm.collectionVariables.set() api is hindering the implementation of a monitor. I like the fact that collectionVariables act like a mini key-value db and using it to persist values across different runs helps to compare previous state with current state while running in the desktop app, and this opens up a lot of possibilities to implement solutions that otherwise would have taken a full-blown app to accomplish something so simple and straightforward.
I am aware that modifying collections is possible in monitor-runs via postman API. However, that approach calls for extra code as opposed to just using pm.collectionVariables.set() api. If pm.collectionVariables.set() can work across all types of runs, transparently, then it would be epic.
If anyone read this far and know a better way to implement a monitor for the above use case, please holler at me. I would love to learn.
Thanks, Mahi
Log in or sign up for Devpost to join the conversation.