Skip to content
Veilus Docs
These docs describe the Veilus release after v0.2.1, coming soon. If you have v0.2.1, some screens and features (Datasets, Trash, the new profile panel, many MCP tools) are not in your version yet.

Price Monitor

This recipe tracks prices on a list of product pages. Each run opens every page in a real profile, reads the price, compares it with the last run, and prints what changed.

Script and example data: solutions/price-monitor on GitHub. It runs daily on a real Veilus profile.

Set it up

Section titled “Set it up”
  1. Create a script in Veilus Flow → Scripts and paste script.ts, then approve it: dataset rows reach approved scripts only. See Scripts.
  2. Import dataset.csv as a dataset and assign it to the profile. See Datasets.
  3. Run it once, then add a schedule, for example every 6 hours.

What a run prints

Section titled “What a run prints”
RESULT {"checked":2,"changed":[{"url":"https://…","from":51.77,"to":49.99}]}

The first run records prices only, so changed is empty. Later runs list the pages whose price changed.

Change it for your sites

Section titled “Change it for your sites”
  • URL column: your product pages. SELECTOR column: the CSS selector of the price (empty means .price).
  • Profile variable WEBHOOK_URL: a webhook URL that accepts JSON, to get a message on each change. The body carries text (read by Slack) and content (read by Discord).
  • A page whose price can’t be read does not stop the run: it is listed under failed in the RESULT line, the other pages are still checked, and the run is marked failed so you notice.
  • Profile variable OUT_DIR: where the last prices are kept (default ~/veilus-solutions).
Section titled “Legal considerations”