How to Watch a Web Page for a Price or Policy Change
Get a notice when a supplier's page changes, or when a value on it passes a limit.
Overview
Suppliers, carriers and platforms often announce changes on a web page rather than by email: a new price list, a shipping cut-off, an API version. A Web page monitor in Spojit checks a public page on a schedule and tells you when it changes, when Miraxa answers a question about it yes, or when a value Miraxa reads from it changes or passes a limit.
A plain change raises a notice, told once. A value compared against a limit raises an incident that stays open while the value is past it. Turn on suggested next steps and Miraxa can find the workflows that use the old value and suggest updating them.
Before You Start
- You need permission to manage monitors.
- The page must be public and show its content without JavaScript or a login.
- Questions and values Miraxa reads use AI credits on each check.
Steps
- Open Control Center, go to the Monitors tab and choose New monitor.
- Choose Tell me once to hear about each change, or Alert me while it's wrong to be alerted while a value is past a limit.
- Select what it watches, choose Web page, and enter its Address.
- Optionally enter a CSS selector in Only this part to watch one section, such as the price table, instead of the whole page.
- Choose what to tell you when:
- The text changes - any change to the text you are watching.
- Miraxa answers a question yes - for example, "Has a new price list been published for 2027?"
- A value Miraxa reads from it - for example, "the price of the 2kg bag". Choose whether it is a number or short text, and alert when it changes, changes by at least a percentage, or passes a comparison such as more than 25.
- Set how often to check. Daily is usually enough for prices and policies.
- Choose Test it now to see what the monitor reads from the page today.
- Pick who to tell and choose Create monitor.
Tips
- Use Only this part whenever you can. Pages change for many reasons (dates, banners, related links), and watching one section keeps the notices to the changes you care about.
- Prefer a question or a value over The text changes on busy pages, so the monitor alerts on what you asked about rather than on every edit to the page.
- For an API rather than a web page, use a Connection monitor on one of your HTTP connections instead.
Common Pitfalls
- Watching a page that builds its content with JavaScript or sits behind a login. The monitor sees what a plain request returns, which may be nearly empty.
- Checking too often. A page that updates once a month does not need checking every few minutes, and each question or value read uses credits.
- Watching the whole page of a site that shows the current date or time. Every check then counts as a change.
Related Articles
- Creating a Monitor
- Applying Suggested Fixes and Using Auto-Apply
- Understanding the Control Center
- HTTP Requests
- Managing Credits
- How to Prompt Miraxa: Writing Effective Instructions