Monitoring with BNOD

Monitor any page and get a desktop alert when it matters

Tell BNOD what to watch — a price, a stock status, a line of text — and it checks on the schedule you set, then fires a desktop notification when your condition is met: an item back in stock, a price under your number, a page that changed since last time. No refreshing a tab all day. It runs as a Chrome extension inside the browser you already use, so the page sees a normal logged-in person, not a bot.

Manual monitoring means keeping a tab open and hitting refresh, which you can't do around the clock. Cloud monitoring services can, but they charge a monthly fee per page, run on their own servers, and get blocked the moment a site notices a headless check. BNOD checks locally, in your session, with your real fingerprint — so it keeps working on pages that block cloud monitors, and there's nothing to pay per month.

How BNOD watches a page

A monitor is a tiny workflow you build once. The schedule_trigger block wakes it up on a cron interval — every 5 minutes, hourly, once a day, whatever you choose. On each run BNOD loads the page and reads the value you're watching with a scrape or get_text step. From there you decide when to be pinged:

Restock alerts. Watch a "Sold out" / "Add to cart" state and add an if_then step so the notification fires when the item is available — sneakers, GPUs, consoles, limited drops.
Price-drop alerts. Track a product's price and notify only when it falls below a threshold you set, using a condition on the scraped value.
Change alerts. Store the value in a variable one run and compare it the next, so the alert fires only when it's different from last time.
Every-run heads-up. Skip the condition entirely and just get the current value pushed to you each time it checks — a daily price, a status line, a count.
Visual proof. Add a take_screenshot step so an alert comes with a picture of the page as it looked on that run.

With 40+ blocks in the visual node editor, a monitor can do more than ping — it can log the value, hit a webhook with http_request, or hand the page to an AI step to summarize what's on it.

Real example: track an Amazon price

Say you want a daily heads-up on a product's price. Build a three-step monitor: a schedule_trigger set to run once a day, a scrape step that grabs the price element off the product page, and a notification step that pings your desktop with the current price. Want it quieter? Add an if_then condition so it only pings when the price is under your number. Set it, and BNOD checks every morning in your own browser — and because it uses your real session, it sees the same page and price you would.

Why it beats cloud monitors

The one thing cloud monitors cannot do: run inside your real browser. BNOD does. Because each check executes in your actual Chrome tab, it uses your real session, your real cookies, and your real fingerprint. Sites that block headless and datacenter bots see an ordinary logged-in visitor, so pages a cloud monitor can't even load are checked normally here — including stock and pricing behind a login.

It is also local-first and runs on your schedule. Checks happen in the browser on your machine, there's no per-page metering, and no monthly monitoring subscription. AI features are bring-your-own-key, so if a monitor uses a model to summarize a page you pay your provider directly at cost, not a markup.

Describe it, AI builds it

You don't have to wire the monitor by hand. BNOD's AI Workflow Builder turns a plain-English request — "check this product page every day and notify me when the price drops below $50" — into a ready-to-run monitor. It sets the schedule, adds the scrape and the condition, and drops in the notification step.

The builder is BYOK across 10 providers — Anthropic, OpenAI, Gemini, OpenRouter, Groq, DeepSeek, Mistral, xAI, Ollama, and any OpenAI-compatible endpoint — plus a ChatGPT Plus sign-in option. Prefer to build by hand? Every monitor it produces is fully editable in the visual node editor.

How it works in 3 steps

Point. Open the page and pick the value to watch — a price, a stock label, a line of text.
Schedule. Set a cron interval with schedule_trigger, then choose when the notification fires — every run, past a price threshold, or only when the value changed.
Run. Turn it on. BNOD checks in the background and pings you when your condition is met.

FAQ

Is it free? Yes. BNOD is free to install and monitor pages with — there's no monthly subscription and no per-page fee. AI features are bring-your-own-key, so if a monitor calls a model you pay your provider directly.

How do I get notified? BNOD fires a desktop notification when your condition is met. You can also add a screenshot to the alert or hit a webhook with http_request.

Can it do restock and price-drop alerts? Yes. Watch a stock label or a price and add an if_then condition so you're pinged when an item is back or drops below a threshold you set — sneakers, GPUs, consoles, tickets, limited drops.

Can it alert only when something changed? Yes, with one extra step: store the value in a variable on one run and compare it on the next, so the notification fires only when it's different from last time.

How often does it check? As often as you want. The schedule_trigger runs on a cron interval you choose — every few minutes, hourly, or once a day.

Will sites block it? It's much harder to block than a cloud monitor. BNOD checks inside your real Chrome with your real session and fingerprint, so a site sees a normal logged-in visitor rather than a headless or datacenter monitor.

Does it work on pages behind a login? Yes. It runs in your own logged-in browser, so it can watch stock, pricing, or dashboards on sites you already have access to.

Comparing tools? See our roundup of the best website change monitoring tools in 2026, start from a ready-made monitor in the templates gallery, or pair monitoring with web scraping to capture the data behind a change. When you're ready, add BNOD to Chrome and set up your first alert in minutes.