Monitor Google Shopping prices with Bright Data & email alerts

493 views

2/3/2026

Lead Generation Webhook HubSpot Salesforce CRM

🛒 Monitor Google Shopping Prices with Bright Data & Email Alerts

This template requires a self-hosted n8n instance to run.

A comprehensive n8n automation that monitors product prices daily using Bright Data's Google Shopping dataset and sends smart email alerts when price conditions are met.

📋 Overview

This workflow provides an automated price monitoring solution that tracks product prices from Google Shopping daily and sends intelligent email notifications. Perfect for e-commerce monitoring, competitor analysis, deal hunting, and inventory management.

✨ Key Features

🕘 Scheduled Monitoring: Daily automated price checks at 9 AM
🛍️ Google Shopping Integration: Uses Bright Data's dataset for accurate pricing
📊 Smart Price Comparison: Compares current prices with historical data
📧 Intelligent Alerts: Sends emails only when prices meet criteria
📈 Data Storage: Updates Google Sheets with latest pricing data
🔄 Batch Processing: Handles multiple products with rate limiting
⚡ Fast & Reliable: Built-in error handling
🎯 Customizable Filters: Advanced price comparison logic

🎯 What This Workflow Does

Schedule Trigger: Runs daily at 9 AM
Data Retrieval: Fetches product list from Google Sheets
Price Extraction: Scrapes current prices using Bright Data
Data Update: Updates Google Sheets with new prices
Price Comparison: Compares new vs. old prices
Smart Filtering: Filters products that meet alert criteria
Email Notifications: Sends alerts for qualifying changes
Rate Limiting: Adds delay between emails

Output Data Points

🚀 Setup Instructions

Prerequisites

n8n instance (self-hosted or cloud)
Google account with Sheets access
Bright Data account with Google Shopping dataset access
Gmail account for notifications

Steps

Import the workflow JSON into n8n
Configure Bright Data credentials and dataset access
Set up Google Sheets with required columns
Configure Gmail OAuth2 credentials
Update sheet IDs and schedule settings
Test with sample products and activate

📖 Usage Guide

Google Sheet Structure

Your Google Sheet should have the following columns to ensure the workflow functions correctly:

Product URL (Text): The direct URL to the Google Shopping product page. This is the primary identifier for the product.
Product Name (Text): The name of the product. This will be automatically populated or updated by the workflow.
Old Price (Number/Currency): The price of the product from the previous check. This column is crucial for price comparison.
New Price (Number/Currency): The most recently scraped price of the product.
Ratings (Number): The star rating of the product.
Reviews (Number): The total number of reviews for the product.
Timestamp (Datetime): The date and time when the price check was performed.

Adding Products

Add Google Shopping URLs to your Google Sheet.
The workflow will fetch product details and track prices.
Historical price data builds over time.

Understanding Price Alerts

The default setting for this workflow is to send an email alert when the new price equals the old price. This might seem counterintuitive, but it's useful for specific scenarios, such as:

Monitoring stable pricing: If you are tracking a product and want to be notified when its price has remained consistent over time, indicating a potential stable buying opportunity or a benchmark.
Verifying data consistency: To confirm that the scraping process is working correctly and consistently retrieving the same price when no changes are expected.

You can easily customize the alert logic to trigger on different conditions as described below.

Customizing Alert Logic

Price drops: new_price < old_price
Significant drops: new_price < (old_price * 0.9) (e.g., price dropped by more than 10%)
Price increases: new_price > old_price
Any change: new_price != old_price

Reading the Results

Real-time pricing data
Historical tracking
Product metadata
Timestamps for each check

🔧 Customization Options

Add More Data: Descriptions, availability, seller info, shipping, images
Modify Email Templates: Customize subject and body
Multiple Recipients: Duplicate email node and change recipients
Webhook Integration: Add real-time triggers or Slack alerts

🚨 Troubleshooting

Bright Data connection failed: Check API credentials and dataset access
No price data extracted: Verify URLs and test with different products
Google Sheets permission denied: Re-authenticate and check sharing
Emails not sending: Re-auth Gmail OAuth and verify recipients
Filter not working: Check price formats and logic
Workflow failed: Check logs, retry logic, and network status

📊 Use Cases & Examples

E-commerce Monitoring: Track competitor pricing and trends
Deal Hunting: Get alerts for price drops on wishlist items
Inventory Management: Monitor supplier pricing for procurement
Market Research: Analyze pricing trends and generate reports

⚙️ Advanced Configuration

Batch Processing: Increase batch size, add delays, use parallel processing
Price History: Store historical data, calculate averages, forecast trends
Tool Integration: CRM, Slack, databases, BI tools (Tableau, Power BI)

📈 Performance & Limits

Single URL: 2–5 seconds
Concurrent Requests: 3–5 (depends on Bright Data plan)
Data Accuracy: 95%+
Success Rate: 90%+
Daily Capacity: 100–500 products
Memory: ~100MB per execution
API Calls: 1 Bright Data + 2 Google Sheets per product

🤝 Support & Community

n8n Forum: <https://community.n8n.io>
Documentation: <https://docs.n8n.io>
Bright Data Support: Via your Bright Data dashboard
GitHub Issues: Report bugs and request features

🎯 Ready to Use!

Your workflow provides a solid foundation for automated price monitoring. Customize it to fit your specific needs and use cases for maximum effectiveness in tracking Google Shopping prices with intelligent email notifications.

Please note that this template uses Community Nodes. Ensure you understand the risks before using community nodes.

Monitor Google Shopping Prices with Bright Data & Email Alerts

This n8n workflow automates the process of monitoring product prices on Google Shopping using Bright Data and sends email alerts when price changes are detected. It's designed to help you track competitor pricing, identify deals, or monitor your own product listings.

What it does

This workflow simplifies price monitoring by performing the following steps:

Triggers on a Schedule: The workflow starts at predefined intervals (e.g., daily, hourly) to check for price updates.
Retrieves Product Data: It fetches a list of products to monitor from a Google Sheet. Each row in the sheet should contain product details, including the Google Shopping URL.
Loops Through Products: For each product listed in the Google Sheet, the workflow processes it individually.
Extracts Price Data: It uses Bright Data (or a similar web scraping service, though Bright Data is indicated by the directory name) to scrape the current price from the Google Shopping URL.
Compares Prices: The workflow compares the newly scraped price with the previously recorded price (presumably stored in the Google Sheet, though not explicitly shown in the JSON, this is a common pattern for such a workflow).
Filters for Price Changes: It identifies products where the price has changed.
Sends Email Alerts: If a price change is detected, an email notification is sent via Gmail, alerting the user to the update.
Updates Google Sheet: The new price and the date of the update are recorded back into the Google Sheet.
Includes Delays: Incorporates a "Wait" step, likely to prevent rate limiting or to space out requests.

Prerequisites/Requirements

To use this workflow, you will need:

n8n Instance: A running n8n instance to host the workflow.
Google Account: For Google Sheets and Gmail integration.
- Google Sheets Credential: To read product URLs and write updated prices.
- Gmail Credential: To send email alerts.
Bright Data Account: (Implied by directory name, but not explicitly in JSON) A Bright Data account or a similar web scraping service to extract prices from Google Shopping. Note: The provided JSON does not include a Bright Data node, but the workflow's purpose strongly suggests its use.
Google Sheet: A Google Sheet set up with product information, including a column for Google Shopping URLs and potentially columns for previous prices and last updated dates.

Setup/Usage

Import the workflow: Download the workflow JSON and import it into your n8n instance.
Configure Credentials:
- Set up your Google Sheets credential to connect to your Google account.
- Set up your Gmail credential to connect to your Google account.
Update Google Sheets Node:
- Specify the Spreadsheet ID and Sheet Name where your product data is stored.
- Ensure the operation is set to "Read" to get product URLs and "Update" or "Append" to record new prices.
Configure Web Scraper (Bright Data):
- If using Bright Data: Add a Bright Data node (or HTTP Request node configured for Bright Data) to fetch the product prices. You will need to configure it with your Bright Data credentials and the appropriate scraping logic for Google Shopping.
- If using another method: Replace the placeholder for web scraping with your preferred method (e.g., HTTP Request node with a custom scraper).
Adjust "Edit Fields (Set)" Node: Ensure this node correctly extracts and formats the price data from the web scraping output.
Configure "Filter" Node: Set the condition to compare the new price with the old price to detect changes.
Update "Gmail" Node:
- Specify the recipient email address(es) for alerts.
- Customize the email subject and body to include relevant product information and price changes.
Schedule the Workflow: Configure the "Schedule Trigger" node to run at your desired frequency (e.g., every hour, daily).
Activate the Workflow: Save and activate the workflow.

Related Templates

Generate song lyrics and music from text prompts using OpenAI and Fal.ai Minimax

Spark your creativity instantly in any chat—turn a simple prompt like "heartbreak ballad" into original, full-length lyrics and a professional AI-generated music track, all without leaving your conversation. 📋 What This Template Does This chat-triggered workflow harnesses AI to generate detailed, genre-matched song lyrics (at least 600 characters) from user messages, then queues them for music synthesis via Fal.ai's minimax-music model. It polls asynchronously until the track is ready, delivering lyrics and audio URL back in chat. Crafts original, structured lyrics with verses, choruses, and bridges using OpenAI Submits to Fal.ai for melody, instrumentation, and vocals aligned to the style Handles long-running generations with smart looping and status checks Returns complete song package (lyrics + audio link) for seamless sharing 🔧 Prerequisites n8n account (self-hosted or cloud with chat integration enabled) OpenAI account with API access for GPT models Fal.ai account for AI music generation 🔑 Required Credentials OpenAI API Setup Go to platform.openai.com → API keys (sidebar) Click "Create new secret key" → Name it (e.g., "n8n Songwriter") Copy the key and add to n8n as "OpenAI API" credential type Test by sending a simple chat completion request Fal.ai HTTP Header Auth Setup Sign up at fal.ai → Dashboard → API Keys Generate a new API key → Copy it In n8n, create "HTTP Header Auth" credential: Name="Fal.ai", Header Name="Authorization", Header Value="Key [Your API Key]" Test with a simple GET to their queue endpoint (e.g., /status) ⚙️ Configuration Steps Import the workflow JSON into your n8n instance Assign OpenAI API credentials to the "OpenAI Chat Model" node Assign Fal.ai HTTP Header Auth to the "Generate Music Track", "Check Generation Status", and "Fetch Final Result" nodes Activate the workflow—chat trigger will appear in your n8n chat interface Test by messaging: "Create an upbeat pop song about road trips" 🎯 Use Cases Content Creators: YouTubers generating custom jingles for videos on the fly, streamlining production from idea to audio export Educators: Music teachers using chat prompts to create era-specific folk tunes for classroom discussions, fostering interactive learning Gift Personalization: Friends crafting anniversary R&B tracks from shared memories via quick chats, delivering emotional audio surprises Artist Brainstorming: Songwriters prototyping hip-hop beats in real-time during sessions, accelerating collaboration and iteration ⚠️ Troubleshooting Invalid JSON from AI Agent: Ensure the system prompt stresses valid JSON; test the agent standalone with a sample query Music Generation Fails (401/403): Verify Fal.ai API key has minimax-music access; check usage quotas in dashboard Status Polling Loops Indefinitely: Bump wait time to 45-60s for complex tracks; inspect fal.ai queue logs for bottlenecks Lyrics Under 600 Characters: Tweak agent prompt to enforce fuller structures like [V1][C][V2][B][C]; verify output length in executions

By Daniel Nkencho

601

Automate Dutch Public Procurement Data Collection with TenderNed

TenderNed Public Procurement What This Workflow Does This workflow automates the collection of public procurement data from TenderNed (the official Dutch tender platform). It: Fetches the latest tender publications from the TenderNed API Retrieves detailed information in both XML and JSON formats for each tender Parses and extracts key information like organization names, titles, descriptions, and reference numbers Filters results based on your custom criteria Stores the data in a database for easy querying and analysis Setup Instructions This template comes with sticky notes providing step-by-step instructions in Dutch and various query options you can customize. Prerequisites TenderNed API Access - Register at TenderNed for API credentials Configuration Steps Set up TenderNed credentials: Add HTTP Basic Auth credentials with your TenderNed API username and password Apply these credentials to the three HTTP Request nodes: "Tenderned Publicaties" "Haal XML Details" "Haal JSON Details" Customize filters: Modify the "Filter op ..." node to match your specific requirements Examples: specific organizations, contract values, regions, etc. How It Works Step 1: Trigger The workflow can be triggered either manually for testing or automatically on a daily schedule. Step 2: Fetch Publications Makes an API call to TenderNed to retrieve a list of recent publications (up to 100 per request). Step 3: Process & Split Extracts the tender array from the response and splits it into individual items for processing. Step 4: Fetch Details For each tender, the workflow makes two parallel API calls: XML endpoint - Retrieves the complete tender documentation in XML format JSON endpoint - Fetches metadata including reference numbers and keywords Step 5: Parse & Merge Parses the XML data and merges it with the JSON metadata and batch information into a single data structure. Step 6: Extract Fields Maps the raw API data to clean, structured fields including: Publication ID and date Organization name Tender title and description Reference numbers (kenmerk, TED number) Step 7: Filter Applies your custom filter criteria to focus on relevant tenders only. Step 8: Store Inserts the processed data into your database for storage and future analysis. Customization Tips Modify API Parameters In the "Tenderned Publicaties" node, you can adjust: offset: Starting position for pagination size: Number of results per request (max 100) Add query parameters for date ranges, status filters, etc. Add More Fields Extend the "Splits Alle Velden" node to extract additional fields from the XML/JSON data, such as: Contract value estimates Deadline dates CPV codes (procurement classification) Contact information Integrate Notifications Add a Slack, Email, or Discord node after the filter to get notified about new matching tenders. Incremental Updates Modify the workflow to only fetch new tenders by: Storing the last execution timestamp Adding date filters to the API query Only processing publications newer than the last run Troubleshooting No data returned? Verify your TenderNed API credentials are correct Check that you have setup youre filter proper Need help setting this up or interested in a complete tender analysis solution? Get in touch 🔗 LinkedIn – Wessel Bulte

By Wessel Bulte

247

🎓 How to transform unstructured email data into structured format with AI agent

This workflow automates the process of extracting structured, usable information from unstructured email messages across multiple platforms. It connects directly to Gmail, Outlook, and IMAP accounts, retrieves incoming emails, and sends their content to an AI-powered parsing agent built on OpenAI GPT models. The AI agent analyzes each email, identifies relevant details, and returns a clean JSON structure containing key fields: From – sender’s email address To – recipient’s email address Subject – email subject line Summary – short AI-generated summary of the email body The extracted information is then automatically inserted into an n8n Data Table, creating a structured database of email metadata and summaries ready for indexing, reporting, or integration with other tools. --- Key Benefits ✅ Full Automation: Eliminates manual reading and data entry from incoming emails. ✅ Multi-Source Integration: Handles data from different email providers seamlessly. ✅ AI-Driven Accuracy: Uses advanced language models to interpret complex or unformatted content. ✅ Structured Storage: Creates a standardized, query-ready dataset from previously unstructured text. ✅ Time Efficiency: Processes emails in real time, improving productivity and response speed. *✅ Scalability: Easily extendable to handle additional sources or extract more data fields. --- How it works This workflow automates the transformation of unstructured email data into a structured, queryable format. It operates through a series of connected steps: Email Triggering: The workflow is initiated by one of three different email triggers (Gmail, Microsoft Outlook, or a generic IMAP account), which constantly monitor for new incoming emails. AI-Powered Parsing & Structuring: When a new email is detected, its raw, unstructured content is passed to a central "Parsing Agent." This agent uses a specified OpenAI language model to intelligently analyze the email text. Data Extraction & Standardization: Following a predefined system prompt, the AI agent extracts key information from the email, such as the sender, recipient, subject, and a generated summary. It then forces the output into a strict JSON structure using a "Structured Output Parser" node, ensuring data consistency. Data Storage: Finally, the clean, structured data (the from, to, subject, and summarize fields) is inserted as a new row into a specified n8n Data Table, creating a searchable and reportable database of email information. --- Set up steps To implement this workflow, follow these configuration steps: Prepare the Data Table: Create a new Data Table within n8n. Define the columns with the following names and string type: From, To, Subject, and Summary. Configure Email Credentials: Set up the credential connections for the email services you wish to use (Gmail OAuth2, Microsoft Outlook OAuth2, and/or IMAP). Ensure the accounts have the necessary permissions to read emails. Configure AI Model Credentials: Set up the OpenAI API credential with a valid API key. The workflow is configured to use the model, but this can be changed in the respective nodes if needed. Connect the Nodes: The workflow canvas is already correctly wired. Visually confirm that the email triggers are connected to the "Parsing Agent," which is connected to the "Insert row" (Data Table) node. Also, ensure the "OpenAI Chat Model" and "Structured Output Parser" are connected to the "Parsing Agent" as its AI model and output parser, respectively. Activate the Workflow: Save the workflow and toggle the "Active" switch to ON. The triggers will begin polling for new emails according to their schedule (e.g., every minute), and the automation will start processing incoming messages. --- Need help customizing? Contact me for consulting and support or add me on Linkedin.

By Davide

1616