Start with the decision each page informs.
A list of thirty pages is not yet a useful monitoring workflow. Write down why each page matters: a supplier’s current price, a product’s availability, a release announcement or an upcoming tender. Keep pages that support a concrete decision.
Use sources you own or have permission to monitor, and review their access requirements. Collect direct page addresses rather than search-result redirects. Give each row a name that a teammate will recognize weeks later.
| Page purpose | Name | Labels | Rule to configure after import |
|---|---|---|---|
| A permitted supplier price page | Supplier A · Standard plan | suppliers, pricing | Falls below the budget threshold |
| Your own release notes | Product releases | product | New item matching a product phrase |
| An authorized policy page | Vendor service policy | policies | Selected text changes |
Review the import before starting any checks.
Prepare the input
Paste one URL per line or use a UTF-8 CSV with url, name and labels columns. Missing schemes default to HTTPS. Import at most 50 rows at once.
Check the review table
Review names, labels, normalized addresses and available Cloud slots. Fix invalid rows. Existing URLs and repeated rows are skipped.
Create paused drafts
Select the rows to create. Each monitor starts paused. Open Finish setup to choose the capture and rule, confirm the preview and activate it.
A CSV cannot prove that every page has the same structure. Confirm each selection rather than copying a selector across unrelated sites. Use the import reference for quoting rules, retries and limits.
Test the change that would matter.
For a price below 100, test both 120 → 95 and 95 → 90. Only the first crosses the threshold; a price-drop rule would match both. For stock plus price, test the combined condition, including a case where only one part is true.
The rule tester uses examples without checking the website or sending alerts. Follow it with a channel delivery test and a controlled capture workflow. Successful extraction, rule matching and delivery are separate things to verify.
Make the watch list easy to live with.
Use labels to group related monitors and select a schedule that fits how quickly you need to act. Review initial changes for noise before expanding the list. Price history can help explain observed movement, but it cannot show changes between checks.
Choose email for personal review or a Business channel such as Discord for a shared destination. If a monitor is temporarily distracting, snooze its change alerts while keeping checks and history. Use pause when you want the checks themselves to stop.
Review the watch list periodically. Remove pages that no longer support a decision, resolve failing captures, and confirm that each notification still reaches the right audience.