HumationHuman + Automation
Back to Catalog

Monitor dynamic website changes with Firecrawl, Sheets & Gmail alerts

FranzFranz
1320 views
2/3/2026
Email ValidationWebhookHubSpotSubscriptionCRM
Official Page

🕸️ Dynamic Website Change Monitor with Smart Email Alerts

Never miss important website updates again! This workflow automatically tracks changes on dynamic websites (think React apps, JavaScript-heavy sites) and sends you instant email notifications when something changes. Perfect for keeping tabs on competitors, monitoring product updates, or staying on top of important announcements.

✨ What makes this special?

🚀 Handles Dynamic Websites: Uses Firecrawl API to scrape JavaScript-rendered content that basic scrapers can't touch 📧 Smart Email Alerts: Only sends notifications when content actually changes (no spam!) 📊 Historical Tracking: Keeps a complete log of all changes in Google Sheets 🛡️ Bulletproof: Continues working even if one part fails ⚡ Ready to Deploy: Webhook-triggered, perfect for cron jobs or external schedulers

🎯 Perfect for monitoring:

  • Competitor pricing pages
  • Job board postings
  • Product availability updates
  • News sites for breaking stories
  • API documentation changes
  • Terms of service updates

🛠️ What you'll need to get started:

API Accounts & Keys:

  1. Firecrawl Account 🔥

    • Sign up at firecrawl.dev
    • Grab your API key from the dashboard
    • Create a "Bearer Auth" credential in n8n

  2. Google Cloud Setup ☁️

    • Enable Google Sheets API
    • Enable Gmail API
    • Set up OAuth2 credentials
    • Add both as credentials in n8n

  3. Google Sheets Document 📋

    • Create a new spreadsheet
    • Add two tabs: "Log" and "comparison"
    • Follow the structure outlined in the workflow notes

🚀 How it works:

  1. Webhook receives trigger → Starts the monitoring process
  2. Firecrawl scrapes website → Gets fresh content (even JavaScript-rendered!)
  3. Smart comparison → Checks against previously stored content
  4. Change detected? → If yes, send email + log everything
  5. Update storage → Prepares for next monitoring cycle

⚙️ Setup Steps:

  1. Import this workflow into your n8n instance
  2. Configure credentials for Firecrawl, Google Sheets, and Gmail
  3. Update the target URL in the Firecrawl node
  4. Set your email address in the Gmail node
  5. Create your Google Sheets with the required structure
  6. Test it manually first, then activate!

🎨 Customize it your way:

  • Target any website by updating the URL
  • Change email templates to match your style
  • Adjust monitoring frequency with external cron jobs
  • Switch between markdown/HTML extraction formats
  • Fine-tune change detection sensitivity

🔧 Troubleshooting:

  • Firecrawl errors? Check your API key and rate limits
  • Google Sheets issues? Verify OAuth permissions and sheet structure
  • Email not sending? Check Gmail API quotas and spam folders
  • Webhook problems? Make sure the workflow is activated

Ready to never miss another website change? Let's get this automation running! 🎉

Monitor Dynamic Website Changes with Firecrawl, Google Sheets & Gmail Alerts

This n8n workflow monitors a dynamic website for changes using Firecrawl, tracks these changes in Google Sheets, and sends email alerts via Gmail when significant updates are detected.

It's ideal for keeping an eye on competitor websites, product pages, news sources, or any web content that frequently updates and requires timely notifications.

What it does

  1. Receives a Webhook Trigger: The workflow is activated by an incoming webhook, which can be triggered by a scheduled job or an external system.
  2. Fetches Website Content with Firecrawl: It makes an HTTP request to the Firecrawl API to scrape the content of a specified URL. Firecrawl is used for its ability to handle dynamic content and provide structured output.
  3. Processes Scraped Data: A Code node extracts relevant information from the Firecrawl response, likely including the main content and a timestamp.
  4. Retrieves Previous State from Google Sheets: It queries a Google Sheet to fetch the last recorded state (content hash and timestamp) of the monitored website.
  5. Compares Current and Previous States: An "If" node compares the newly scraped content with the previously stored content. It likely uses a hashing mechanism to detect changes efficiently.
  6. Updates Google Sheets (if changed): If a change is detected, the workflow updates the Google Sheet with the new content's hash and timestamp, maintaining a history of modifications.
  7. Sends Gmail Alert (if changed): If the website content has changed, a Gmail node sends an email notification to a specified recipient, detailing the detected changes.
  8. Responds to Webhook: The workflow sends a response back to the triggering webhook, indicating success or failure.

Prerequisites/Requirements

  • n8n Instance: A running n8n instance (cloud or self-hosted).
  • Firecrawl API Key: An API key for the Firecrawl service to scrape website content.
  • Google Account: A Google account with access to Google Sheets to store website states.
  • Gmail Account: A Gmail account configured as an n8n credential to send email alerts.

Setup/Usage

  1. Import the workflow: Download the JSON provided and import it into your n8n instance.
  2. Configure Credentials:
    • Firecrawl: Set up an HTTP Request credential for Firecrawl, using your API key.
    • Google Sheets: Configure a Google Sheets OAuth2 credential, granting access to your Google Sheets.
    • Gmail: Configure a Gmail OAuth2 credential, granting access to send emails.
  3. Set up the Webhook Trigger:
    • Activate the "Webhook" node and copy its URL. This URL will be used to trigger the workflow.
  4. Configure the HTTP Request (Firecrawl):
    • Update the URL in the "HTTP Request" node to the website you wish to monitor.
    • Ensure the Firecrawl API key is correctly configured in the HTTP Request node's authentication settings.
  5. Configure Google Sheets:
    • Specify the Spreadsheet ID and Sheet Name in the "Google Sheets" node where the website's state will be stored. You'll need a sheet with columns for the URL, content hash, and timestamp.
  6. Configure Gmail:
    • In the "Gmail" node, set the recipient email address, subject, and customize the email body to include details about the detected changes.
  7. Activate the workflow: Save and activate the workflow.
  8. Schedule the workflow: Set up a schedule (e.g., using an n8n Schedule Trigger or an external cron job) to periodically call the Webhook URL of this workflow.

Related Templates

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

Wessel BulteBy 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.

DavideBy Davide
1616

Synchronizing WooCommerce inventory and creating products with Google Gemini AI and BrowserAct

Synchronize WooCommerce Inventory & Create Products with Gemini AI & BrowserAct This sophisticated n8n template automates WooCommerce inventory management by scraping supplier data, updating existing products, and intelligently creating new ones with AI-formatted descriptions. This workflow is essential for e-commerce operators, dropshippers, and inventory managers who need to ensure their product pricing and stock levels are synchronized with multiple third-party suppliers, minimizing overselling and maximizing profit. --- Self-Hosted Only This Workflow uses a community contribution and is designed and tested for self-hosted n8n instances only. --- How it works The workflow is typically run by a Schedule Trigger (though a Manual Trigger is also shown) to check stock automatically. It reads a list of suppliers and their inventory page URLs from a central Google Sheet. The workflow loops through each supplier: A BrowserAct node scrapes the current stock and price data from the supplier's inventory page. A Code node parses this bulk data into individual product items. It then loops through each individual product found. The workflow checks WooCommerce to see if the product already exists based on its name. If the product exists: It proceeds to update the existing product's price and stock quantity. If the product DOES NOT exist: An If node checks if the missing product's category matches a predefined type (optional filtering). If it passes the filter, a second BrowserAct workflow scrapes detailed product attributes from a dedicated product page (e.g., DigiKey). An AI Agent (Gemini) transforms these attributes into a specific, styled HTML table for the product description. Finally, the product is created in WooCommerce with all scraped details and the AI-generated description. Error Handling: Multiple Slack nodes are configured to alert your team immediately if any scraping task fails or if the product update/creation process encounters an issue. Note: This workflow does not support image uploads for new products. To enable this functionality, you must modify both the n8n and BrowserAct workflows. --- Requirements BrowserAct API account for web scraping BrowserAct n8n Community Node -> (n8n Nodes BrowserAct) BrowserAct templates named “WooCommerce Inventory & Stock Synchronization” and “WooCommerce Product Data Reconciliation” Google Sheets credentials for the supplier list WooCommerce credentials for product management Google Gemini account for the AI Agent Slack credentials for error alerts --- Need Help? How to Find Your BrowseAct API Key & Workflow ID How to Connect n8n to Browseract How to Use & Customize BrowserAct Templates How to Use the BrowserAct N8N Community Node --- Workflow Guidance and Showcase STOP Overselling! Auto-Sync WooCommerce Inventory from ANY Supplier

Madame AI Team | KaiBy Madame AI Team | Kai
600