This article contains affiliate links. If you buy through them, we may earn a commission at no extra cost to you.
Why Manual Price Monitoring Is Costing You Money
If you sell products online — whether on your own store, Amazon, or eBay — you already know how fast prices move. A competitor drops their price on a Tuesday afternoon, and by Wednesday morning you have lost a dozen sales you never even knew were at risk. Most small business owners respond by checking prices manually, maybe once or twice a week. That is not enough.
An automated price monitoring system watches your competitors around the clock, logs every change, and sends you an alert the moment something relevant happens. You can build this entire workflow with n8n, an open-source automation tool with 400+ integrations that you can self-host for free or run in the cloud.
What Your Automated System Will Do
Before diving into the build, here is what the finished workflow will handle automatically:
- Scrape or fetch competitor prices from target URLs on a schedule you control
- Compare today's price against yesterday's stored price and calculate the percentage change
- Log every data point to a Google Sheet or Airtable for historical analysis
- Send an instant alert via email or Slack when a price drops below your threshold
- Generate a weekly summary so you always have a market overview ready
Step 1 — Choose Your Data Sources
Start by listing the exact product pages you want to monitor. These might be Amazon listings for your top-selling SKUs, pages on a direct competitor's website, or price-comparison portals like Idealo or Google Shopping.
For publicly accessible web pages, you have two clean options:
- HTTP Request node — fetches the raw HTML of any URL. Pair it with an HTML Extract node to pull the price element using a CSS selector.
- Price-data APIs — services like Rainforest API (Amazon) or PriceAPI return structured JSON. These are more reliable and do not break when a website redesigns.
For most SMEs, a mix of both works well. Use an API for Amazon and direct HTTP scraping for niche competitor sites.
Step 2 — Build the Core Workflow
Trigger: Run on a Schedule
Set a Cron node to run every four to six hours. Checking more frequently than that rarely adds value and may get your IP flagged on some sites.
Fetch and Parse the Price
Use an HTTP Request node to hit your target URL. Then use the HTML Extract node to grab the price. A typical CSS selector for an e-commerce product page looks like .product-price span or #priceblock_ourprice. Clean the result — strip the currency symbol and convert to a number — using a Set or Function node.
Compare Against the Previous Price
Read the last known price from your Google Sheet using the Google Sheets node. Inside an IF node, check whether the new price differs by more than your chosen threshold — for example, more than 5% in either direction. This keeps you from getting flooded with alerts over rounding differences.
Log the Data Point
Always write every price check to your sheet, not just the ones that trigger alerts. After a few weeks you will have a rich dataset showing how prices move across the week or in response to promotions.
Send the Alert
When your IF condition is met, route the workflow to a Send Email node or a Slack node. Include the product name, competitor URL, old price, new price, and the percentage change. A well-formatted alert might read: Competitor X dropped the price of Widget Pro from €49.90 to €39.90 — a 20% decrease.
Step 3 — Add a Weekly Summary Report
Create a second workflow triggered every Monday morning. It reads all the price data logged during the past seven days, groups it by product and competitor, and emails you a clean summary table. This gives you the strategic view your day-to-day alerts cannot provide.
Real-World Example: An Online Electronics Retailer
A small electronics shop in Hamburg monitors 40 SKUs across three competitors. Before automation, the owner spent roughly three hours every week manually checking prices in browser tabs. After setting up this workflow, the system now runs unattended, logs approximately 1,200 price data points per week, and sends an average of four to eight alerts. The owner uses those alerts to adjust prices in their Shopify store within the hour — a response time that was previously impossible.
Tips to Keep Your System Reliable
- Handle errors gracefully — add an Error Trigger node so you get notified if a scrape fails rather than silently missing data.
- Rotate your checks — if you monitor many URLs, space the requests a few seconds apart to stay polite to servers.
- Version your selectors — when a competitor redesigns their site, your CSS selector will break. A quick monthly check keeps things running.
- Enrich your alerts with context — include your own current price in the alert so you can see at a glance whether you are now above or below the market.
Ready to Build It?
Price monitoring is one of the highest-ROI automations an SME can implement because it directly protects margin and revenue with minimal ongoing effort. The workflow described here takes around two hours to set up from scratch, and the insights it delivers start paying off within the first week.
Start building your price monitoring workflow today with n8n — it is the most practical starting point for this kind of automation, whether you self-host it for free or use the managed cloud version.