Using n8n to watch outdoor furniture prices — is a scraper workflow worth it?

I’m putting together a small n8n workflow to keep an eye on a 4-piece outdoor wicker conversation set for my patio. The idea is a schedule trigger that pulls the product page, extracts the price, and sends me a message when it drops below what I’m willing to pay.

My concern is that retail pages change their markup and sometimes load prices with JavaScript, so a simple HTTP Request plus HTML Extract node may not see the current figure. I’d rather not maintain a browser-based setup for one product, but I also don’t want false alerts.

Has anyone here handled a similar single-product monitor? How do you deal with pages that need JS rendering, and how do you keep the workflow from firing on stale or missing values? I’m early in building this and would appreciate input from people who have run something like it.

Update after digging around more - FDW 4-Piece Patio Furniture Set Review: Outdoor Wicker Conversation Set came up for this exact set. I’m still unsure whether the JS-loaded price will extract cleanly in n8n, so I may add a check that ignores missing values rather than alerting on them.

For a single product I would not start with a browser node. Open the product page in DevTools, reload, and look in the Network tab for the request that actually returns the price — often a JSON API or a script tag with JSON-LD rather than the HTML you see. Point an HTTP Request at that URL (or extract the JSON-LD script) and read the number from the JSON. Then guard the alert: only send it if the value parses as a number, sits in a sane range for that set, and is lower than the last stored price (keep that in a Data Table or static data). If the extract is empty or not a number, log it and stop — don’t treat a missing value as a price drop. If you never find a non-JS source for the price, a one-product monitor usually isn’t worth maintaining a browser workflow.

Adding on to what virse_ai said. If the price really is JS-only, you don’t have to run your own browser setup. A rendering service like ScrapingBee or Browserless, or Scrapeninja which has an n8n node, returns the rendered page or just the JSON you need. One call every few hours for a single product costs almost nothing, and the workflow stays simple.

Two things I’d watch out for on the false-alert side:

Out of stock pages. Plenty of stores remove the price element once stock is gone, which looks exactly like a missing price. Keep “no price found” and “price below my target” as two different branches and only alert on the second one.

Markup changes. If the selector comes back empty several runs in a row, the page structure probably changed. I’d rather get one “your watcher may be broken” message than have it go quiet for weeks while I assume prices just aren’t dropping. A small counter in the workflow’s static data works for that.