HumationHuman + Automation
Back to Catalog

Track website changes with Firecrawl, GPT-5-Mini, Notion, and Gmail

ScoutNowScoutNow
116 views
2/3/2026
Event CreationOAuth2AutomationAPIGoogle Calendar
Official Page

Stay Updated on Website Changes Automatically

Manually checking websites for updates or competitor changes can be tedious. This workflow automates the process by scraping target pages, capturing screenshots, and analyzing content changes using Firecrawl and GPT-5-mini. All updates are saved in Notion, and you can optionally receive email alerts — keeping you informed without lifting a finger.

Key Features

  • Automated Website Monitoring
    Tracks changes on multiple target URLs on a daily schedule.

  • Visual & Text-Based Updates
    Captures screenshots and generates concise text summaries for each change.

  • Notion Integration
    Stores snapshots, comparisons, and summaries directly in Notion for easy reference.

  • GPT-Powered Comparison
    Highlights meaningful changes between snapshots using GPT-5-mini.

  • Change Criteria Input
    Define what type of updates matter to you — focus on specific content changes or ignore minor differences.

  • Email Alerts via Gmail
    Sends notifications when updates occur, so you never miss important changes.

  • Reusable Notion Page Template
    Includes a structured template for consistent tracking and reporting: View Template

Email Updates:
Email Update
Notion Page Template:
Notion Page
Notion Update Example:
Notion Update

Setup Instructions

1. Add Target URLs

Paste one or more websites you want to monitor. The workflow accepts multiple URLs in JSON format for scalable tracking.

2. Setup Firecrawl Credential

Use Firecrawl to scrape website data without dealing with complex API setups.

Steps:

  1. Go to firecrawl.dev/app and sign up.
  2. Copy your API Key from the dashboard.
  3. In n8n, open the Firecrawl node, add a new credential, and paste the key.
  4. Test the node to ensure the connection works.

3. Setup OpenAI API Key

The workflow uses GPT-5-mini to analyze and summarize website changes.

Steps:

  1. Sign up at OpenAI if you haven’t already.
  2. Generate a new API Key in your OpenAI dashboard.
  3. In n8n, open the GPT node, add a new credential, and paste the API key.
  4. Test the node to ensure it can successfully call the API.

4. Setup Gmail for Email Alerts

  1. In n8n, open the Gmail node.
  2. Click Add New Credentials and select OAuth2.
  3. Follow the Google OAuth setup to allow n8n to send emails on your behalf.
  4. Choose the recipient and customize the alert formatting to include snapshots and summaries.

5. Configure the Workflow

  1. Import the workflow into n8n.
  2. Add your target URLs in JSON format.
  3. Paste your Firecrawl API Key into the Firecrawl node.
  4. Add your OpenAI API key to the GPT node.
  5. Authenticate Gmail if email notifications are desired.
  6. Set your preferred change criteria to filter meaningful updates.
  7. Adjust the schedule for daily execution or your preferred frequency.

How It Works

  1. Schedule Trigger: Runs daily or on-demand.
  2. Fetch Pages: Scrapes target websites using Firecrawl.
  3. Capture & Compare: Screenshots and text are stored and compared using GPT-5-mini.
  4. Apply Change Criteria: Only updates that meet your defined criteria are logged.
  5. Save Updates: Changes are stored in Notion with visual and text summaries.
  6. Optional Alerts: Sends Gmail notifications with updates.

Example Use Cases

  • Monitor competitor websites for product, pricing, or design changes.
  • Track updates on blogs, documentation, or landing pages.
  • Automatically log changes for research, reporting, or team awareness.
  • Get notified instantly when key pages are updated.

Requirements

| Tool | Purpose | |------|----------| | Firecrawl API Key | Scrape website content | | OpenAI API Key | Generate summaries and compare changes with GPT-5-mini | | n8n | Run and schedule the automation | | Notion | Store snapshots, summaries, and comparisons | | Gmail (OAuth2) | Send alert emails |

Have questions about this template? Feel free to reach out. Our DMs are always open!

Email: hello@scoutnow.app
X (Twitter): @ScoutNowApp

n8n Website Change Tracker with Firecrawl, GPT-5 Mini, Notion, and Gmail

This n8n workflow automates the process of monitoring website changes, summarizing them with AI, storing the summaries in Notion, and notifying you via Gmail. It's designed to keep you informed about updates to important web pages without manual checking.

What it does

  1. Schedules Website Checks: Periodically triggers to check a predefined list of websites for changes.
  2. Fetches Website Content: Uses an HTTP Request node to fetch the content of specified URLs via the Firecrawl API.
  3. Extracts and Processes Content: A Code node extracts the markdown content from the Firecrawl response.
  4. Splits Content for AI Processing: Divides the fetched content into manageable chunks for the AI model.
  5. Summarizes Changes with OpenAI (GPT-5 Mini): Utilizes OpenAI (configured for GPT-5 Mini) to generate concise summaries of the website content.
  6. Stores Summaries in Notion: Creates new pages or updates existing entries in a specified Notion database with the AI-generated summaries and relevant website information.
  7. Sends Email Notifications: Dispatches a summary email via Gmail, alerting you to the detected changes and their AI-generated summaries.

Prerequisites/Requirements

To use this workflow, you will need:

  • n8n Instance: A running n8n instance.
  • Firecrawl API Key: An API key for Firecrawl to fetch website content.
  • OpenAI API Key: An API key for OpenAI, configured to use the gpt-5-mini model (or a similar capable model).
  • Notion Integration: A Notion integration with access to the database where you want to store the summaries.
  • Gmail Account: A Gmail account configured as a credential in n8n for sending notifications.

Setup/Usage

  1. Import the workflow: Download the provided JSON and import it into your n8n instance.
  2. Configure Credentials:
    • HTTP Request (Firecrawl): Set up an HTTP Header Auth credential for Firecrawl with your API key.
    • OpenAI: Configure your OpenAI API key credential.
    • Notion: Set up your Notion API key credential and ensure the integration has access to your target database.
    • Gmail: Configure your Gmail OAuth2 credential.
  3. Customize Website URLs: In the Code node after the Schedule Trigger, modify the urls array to include the websites you wish to monitor.
  4. Configure Notion Database: In the Notion node, specify the Database ID where the summaries should be stored. Adjust property mappings as needed.
  5. Customize Gmail Notifications: In the Gmail node, set the recipient email address, subject, and body of the notification email.
  6. Activate the workflow: Once configured, activate the workflow to start monitoring your websites. The Schedule Trigger is currently configured to run every 5 minutes, but this can be adjusted.

Related Templates

Track competitor SEO keywords with Decodo + GPT-4.1-mini + Google Sheets

This workflow automates competitor keyword research using OpenAI LLM and Decodo for intelligent web scraping. Who this is for SEO specialists, content strategists, and growth marketers who want to automate keyword research and competitive intelligence. Marketing analysts managing multiple clients or websites who need consistent SEO tracking without manual data pulls. Agencies or automation engineers using Google Sheets as an SEO data dashboard for keyword monitoring and reporting. What problem this workflow solves Tracking competitor keywords manually is slow and inconsistent. Most SEO tools provide limited API access or lack contextual keyword analysis. This workflow solves that by: Automatically scraping any competitor’s webpage with Decodo. Using OpenAI GPT-4.1-mini to interpret keyword intent, density, and semantic focus. Storing structured keyword insights directly in Google Sheets for ongoing tracking and trend analysis. What this workflow does Trigger — Manually start the workflow or schedule it to run periodically. Input Setup — Define the website URL and target country (e.g., https://dev.to, france). Data Scraping (Decodo) — Fetch competitor web content and metadata. Keyword Analysis (OpenAI GPT-4.1-mini) Extract primary and secondary keywords. Identify focus topics and semantic entities. Generate a keyword density summary and SEO strength score. Recommend optimization and internal linking opportunities. Data Structuring — Clean and convert GPT output into JSON format. Data Storage (Google Sheets) — Append structured keyword data to a Google Sheet for long-term tracking. Setup Prerequisites If you are new to Decode, please signup on this link visit.decodo.com n8n account with workflow editor access Decodo API credentials OpenAI API key Google Sheets account connected via OAuth2 Make sure to install the Decodo Community node. Create a Google Sheet Add columns for: primarykeywords, seostrengthscore, keyworddensity_summary, etc. Share with your n8n Google account. Connect Credentials Add credentials for: Decodo API credentials - You need to register, login and obtain the Basic Authentication Token via Decodo Dashboard OpenAI API (for GPT-4o-mini) Google Sheets OAuth2 Configure Input Fields Edit the “Set Input Fields” node to set your target site and region. Run the Workflow Click Execute Workflow in n8n. View structured results in your connected Google Sheet. How to customize this workflow Track Multiple Competitors → Use a Google Sheet or CSV list of URLs; loop through them using the Split In Batches node. Add Language Detection → Add a Gemini or GPT node before keyword analysis to detect content language and adjust prompts. Enhance the SEO Report → Expand the GPT prompt to include backlink insights, metadata optimization, or readability checks. Integrate Visualization → Connect your Google Sheet to Looker Studio for SEO performance dashboards. Schedule Auto-Runs → Use the Cron Node to run weekly or monthly for competitor keyword refreshes. Summary This workflow automates competitor keyword research using: Decodo for intelligent web scraping OpenAI GPT-4.1-mini for keyword and SEO analysis Google Sheets for live tracking and reporting It’s a complete AI-powered SEO intelligence pipeline ideal for teams that want actionable insights on keyword gaps, optimization opportunities, and content focus trends, without relying on expensive SEO SaaS tools.

Ranjan DailataBy Ranjan Dailata
161

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

Daniel NkenchoBy Daniel Nkencho
601

Automate invoice processing with OCR, GPT-4 & Salesforce opportunity creation

PDF Invoice Extractor (AI) End-to-end pipeline: Watch Drive ➜ Download PDF ➜ OCR text ➜ AI normalize to JSON ➜ Upsert Buyer (Account) ➜ Create Opportunity ➜ Map Products ➜ Create OLI via Composite API ➜ Archive to OneDrive. --- Node by node (what it does & key setup) 1) Google Drive Trigger Purpose: Fire when a new file appears in a specific Google Drive folder. Key settings: Event: fileCreated Folder ID: google drive folder id Polling: everyMinute Creds: googleDriveOAuth2Api Output: Metadata { id, name, ... } for the new file. --- 2) Download File From Google Purpose: Get the file binary for processing and archiving. Key settings: Operation: download File ID: ={{ $json.id }} Creds: googleDriveOAuth2Api Output: Binary (default key: data) and original metadata. --- 3) Extract from File Purpose: Extract text from PDF (OCR as needed) for AI parsing. Key settings: Operation: pdf OCR: enable for scanned PDFs (in options) Output: JSON with OCR text at {{ $json.text }}. --- 4) Message a model (AI JSON Extractor) Purpose: Convert OCR text into strict normalized JSON array (invoice schema). Key settings: Node: @n8n/n8n-nodes-langchain.openAi Model: gpt-4.1 (or gpt-4.1-mini) Message role: system (the strict prompt; references {{ $json.text }}) jsonOutput: true Creds: openAiApi Output (per item): $.message.content → the parsed JSON (ensure it’s an array). --- 5) Create or update an account (Salesforce) Purpose: Upsert Buyer as Account using an external ID. Key settings: Resource: account Operation: upsert External Id Field: taxid_c External Id Value: ={{ $json.message.content.buyer.tax_id }} Name: ={{ $json.message.content.buyer.name }} Creds: salesforceOAuth2Api Output: Account record (captures Id) for downstream Opportunity. --- 6) Create an opportunity (Salesforce) Purpose: Create Opportunity linked to the Buyer (Account). Key settings: Resource: opportunity Name: ={{ $('Message a model').item.json.message.content.invoice.code }} Close Date: ={{ $('Message a model').item.json.message.content.invoice.issue_date }} Stage: Closed Won Amount: ={{ $('Message a model').item.json.message.content.summary.grand_total }} AccountId: ={{ $json.id }} (from Upsert Account output) Creds: salesforceOAuth2Api Output: Opportunity Id for OLI creation. --- 7) Build SOQL (Code / JS) Purpose: Collect unique product codes from AI JSON and build a SOQL query for PricebookEntry by Pricebook2Id. Key settings: pricebook2Id (hardcoded in script): e.g., 01sxxxxxxxxxxxxxxx Source lines: $('Message a model').first().json.message.content.products Output: { soql, codes } --- 8) Query PricebookEntries (Salesforce) Purpose: Fetch PricebookEntry.Id for each Product2.ProductCode. Key settings: Resource: search Query: ={{ $json.soql }} Creds: salesforceOAuth2Api Output: Items with Id, Product2.ProductCode (used for mapping). --- 9) Code in JavaScript (Build OLI payloads) Purpose: Join lines with PBE results and Opportunity Id ➜ build OpportunityLineItem payloads. Inputs: OpportunityId: ={{ $('Create an opportunity').first().json.id }} Lines: ={{ $('Message a model').first().json.message.content.products }} PBE rows: from previous node items Output: { body: { allOrNone:false, records:[{ OpportunityLineItem... }] } } Notes: Converts discount_total ➜ per-unit if needed (currently commented for standard pricing). Throws on missing PBE mapping or empty lines. --- 10) Create Opportunity Line Items (HTTP Request) Purpose: Bulk create OLIs via Salesforce Composite API. Key settings: Method: POST URL: https://<your-instance>.my.salesforce.com/services/data/v65.0/composite/sobjects Auth: salesforceOAuth2Api (predefined credential) Body (JSON): ={{ $json.body }} Output: Composite API results (per-record statuses). --- 11) Update File to One Drive Purpose: Archive the original PDF in OneDrive. Key settings: Operation: upload File Name: ={{ $json.name }} Parent Folder ID: onedrive folder id Binary Data: true (from the Download node) Creds: microsoftOneDriveOAuth2Api Output: Uploaded file metadata. --- Data flow (wiring) Google Drive Trigger → Download File From Google Download File From Google → Extract from File → Update File to One Drive Extract from File → Message a model Message a model → Create or update an account Create or update an account → Create an opportunity Create an opportunity → Build SOQL Build SOQL → Query PricebookEntries Query PricebookEntries → Code in JavaScript Code in JavaScript → Create Opportunity Line Items --- Quick setup checklist 🔐 Credentials: Connect Google Drive, OneDrive, Salesforce, OpenAI. 📂 IDs: Drive Folder ID (watch) OneDrive Parent Folder ID (archive) Salesforce Pricebook2Id (in the JS SOQL builder) 🧠 AI Prompt: Use the strict system prompt; jsonOutput = true. 🧾 Field mappings: Buyer tax id/name → Account upsert fields Invoice code/date/amount → Opportunity fields Product name must equal your Product2.ProductCode in SF. ✅ Test: Drop a sample PDF → verify: AI returns array JSON only Account/Opportunity created OLI records created PDF archived to OneDrive --- Notes & best practices If PDFs are scans, enable OCR in Extract from File. If AI returns non-JSON, keep “Return only a JSON array” as the last line of the prompt and keep jsonOutput enabled. Consider adding validation on parsing.warnings to gate Salesforce writes. For discounts/taxes in OLI: Standard OLI fields don’t support per-line discount amounts directly; model them in UnitPrice or custom fields. Replace the Composite API URL with your org’s domain or use the Salesforce node’s Bulk Upsert for simplicity.

Le NguyenBy Le Nguyen
942