Monitor Amazon and eBay prices and email on changes
An n8n workflow checks product URLs from a Google Sheet three times a day, compares prices, emails changes and logs every check. Task: Suggested implementation: Configure a seven-node n8n workflow to run at 9am, 3pm, and 9pm. It reads product names, URLs, and last prices from a Google Sheet, fetches each page, and extracts prices using regex in a code node. The workflow compares new prices to previous values, sends Gmail alerts on changes, and logs results. Human role: Manually adjust regex patterns for new site formats and handle 403 errors or anti-scraping blocks.; tools: n8n. Human role: Source evidence is unavailable for specific human roles; the workflow automates monitoring, but manual intervention may be needed for regex adjustments or handling 403 errors.; limitations: Prerequisites include an active n8n instance, Google Sheets API access, and Gmail credentials. Constraints: Amazon and eBay often block scrapers with 403 errors, requiring User-Agent headers or official APIs. Regex extraction is fragile and may fail if page structures change. Source reliability is low due to the broken link; treat all claims as unverified..
Tools
Published on Agent Work Atlas:
Overview
An n8n workflow checks product URLs from a Google Sheet three times a day, compares prices, emails changes and logs every check.
Workflow
Suggested implementation: Configure a seven-node n8n workflow to run at 9am, 3pm, and 9pm. It reads product names, URLs, and last prices from a Google Sheet, fetches each page, and extracts prices using regex in a code node. The workflow compares new prices to previous values, sends Gmail alerts on changes, and logs results. Human role: Manually adjust regex patterns for new site formats and handle 403 errors or anti-scraping blocks.
Reported result
Actual outcomes are unknown as the source returned a 404 error and no execution logs were provided. The original text claimed tracking 12 products and reducing competitor price detection time from days to under an hour, but this cannot be verified. Proposed acceptance check: Monitor 3 test URLs for 24 hours and verify that email alerts are sent within 15 minutes of a confirmed price change.
Human role
Source evidence is unavailable for specific human roles; the workflow automates monitoring, but manual intervention may be needed for regex adjustments or handling 403 errors.
Limitations
Prerequisites include an active n8n instance, Google Sheets API access, and Gmail credentials. Constraints: Amazon and eBay often block scrapers with 403 errors, requiring User-Agent headers or official APIs. Regex extraction is fragile and may fail if page structures change. Source reliability is low due to the broken link; treat all claims as unverified.
Try it
Act as an automation engineer. I need to set up a price monitoring workflow using n8n. Inputs: - [Google Sheet URL] containing columns: Product Name, URL, Last Price. - [Target Email] for alerts. - [Sample URLs] for 3 test products. Steps: 1. Create a new n8n workflow with a Schedule Trigger (9am, 3pm, 9pm). 2. Add a Google Sheets node to read the input data. 3. Add an HTTP Request node to fetch each product URL. 4. Add a Code node to extract the price using regex (provide the regex pattern). 5. Add an IF node to compare the extracted price with the 'Last Price' from the sheet. 6. If changed, add a Gmail node to send an alert and a Google Sheets node to update the 'Last Price'. 7. Log all results to a separate sheet. Deliverables: - The n8n workflow JSON. - A test report showing successful execution for the 3 sample URLs. Safeguards: - Run a dry mode first where emails are not sent, only logged. - Confirm with me before enabling live email alerts. - If a 403 error occurs, stop and ask for a User-Agent header or API alternative. - Ask clarifying questions if the regex pattern fails for any sample URL.
Source reports are not independently verified. Publication date is the catalog publication date, not the original article date.