HumationHuman + Automation
Back to Catalog

Monitor website performance with PageSpeed Insights and send alerts

DahianaDahiana
1077 views
2/3/2026
Cloud StorageAutomationAttachmentsEmailFile Upload
Official Page

Monitor website performance with PageSpeed Insights and save to Google Sheets with alerts

This n8n template automatically monitors website performance using Google's PageSpeed Insights API, compiles detailed reports, and tracks performance trends over time in Google Sheets.

Use cases: Agency client monitoring, competitor analysis, performance regression detection, SEO reporting, site migration monitoring, A/B testing performance impact, and maintaining performance SLAs.

Who's it for

  • Digital agencies monitoring client websites
  • SEO professionals tracking site performance
  • DevOps teams maintaining performance SLAs
  • Business owners wanting automated site monitoring

How it works

  • Automated Testing: Scheduled audits of multiple websites using PageSpeed Insights API
  • Core Web Vitals: Tracks LCP, FID, CLS, and overall performance scores
  • Historical Tracking: Maintains performance history for trend analysis
  • Alert System: Sends notifications when performance drops below thresholds
  • Detailed Reporting: Captures specific recommendations and optimization opportunities

Two Workflow Paths

  1. Scheduled Audit: Automatically tests all URLs from Google Sheet on schedule
  2. On-Demand Testing: Webhook endpoint for immediate single-URL testing

How to set up

  1. Get a free PageSpeed Insights API key from Google Cloud Console
  2. Create Google Sheet with columns: URL, Site Name, Category, Alert Threshold, Last_Processed_Date and Device.
  3. Set up Google Sheets API credentials
  4. Configure notification preferences (Slack, email, etc.)
  5. Set audit schedule (daily, weekly, or custom)
  6. Define performance thresholds for alerts

Requirements

  • Google PageSpeed Insights API key (free)
  • Google Sheets API access
  • n8n instance (cloud or self-hosted)
  • Optional: Slack/email for notifications

Google Sheet Structure

Input Sheet ("sites"):

  • URL, Site_Name, Category, Alert_Threshold, Last_Processed_Date and Device.

Results Sheet ("audit_results"):

  • Date, URL, Site_Name, Device, Performance_Score, LCP, FID, CLS, Recommendations, Full_Report_URL

API Usage (On-Demand)

POST to webhook:

{
  "url": "https://example.com",
  "site_name": "Example Site",
  "alert_threshold": 75
}

How to customize

  • Add custom performance thresholds per site
  • Include additional metrics (accessibility, SEO, best practices)
  • Connect to other dashboards (Data Studio, Grafana)
  • Add competitor benchmarking
  • Integrate with project management tools for issue tracking
  • Set up different notification channels based on severity
  • Sample Google Sheet Included

Monitor Website Performance with PageSpeed Insights and Send Alerts

This n8n workflow automates the process of monitoring website performance using Google PageSpeed Insights and sending alerts based on predefined thresholds. It allows you to regularly check the performance of specified URLs and receive notifications if scores fall below acceptable levels.

What it does

This workflow performs the following key steps:

  1. Triggers on a Schedule: The workflow starts at a scheduled interval, allowing for regular performance checks.
  2. Fetches URLs from Google Sheets: It reads a list of website URLs from a Google Sheet, which acts as the central repository for sites to monitor.
  3. Executes PageSpeed Insights API Calls: For each URL, it makes an HTTP request to the Google PageSpeed Insights API to retrieve performance data.
  4. Processes PageSpeed Results: A Code node extracts relevant performance metrics (e.g., performance score, FCP, LCP, CLS, TBT, SI) from the API response.
  5. Checks Performance Thresholds: An If node evaluates if the performance score for either desktop or mobile falls below a specified threshold (e.g., 50).
  6. Sends Email Alerts (if thresholds are met): If a performance score is below the threshold, it sends an email notification via Gmail to alert stakeholders.
  7. Responds to Webhook (optional): The workflow is also set up to respond to a webhook, potentially allowing for manual triggers or integration with other systems.
  8. No Operation (if thresholds are not met): If performance scores are above the threshold, the workflow simply proceeds without sending an alert.

Prerequisites/Requirements

To use this workflow, you will need:

  • n8n Instance: A running n8n instance.
  • Google Sheets Account: A Google Sheets spreadsheet containing the URLs you wish to monitor.
  • Google PageSpeed Insights API Key: An API key for the Google PageSpeed Insights API.
  • Gmail Account: A Gmail account configured as a credential in n8n for sending email alerts.
  • Google Sheets Credential: A Google Sheets credential configured in n8n to access your spreadsheet.

Setup/Usage

  1. Import the Workflow: Import the provided JSON into your n8n instance.
  2. Configure Google Sheets Node (Node 18):
    • Set up your Google Sheets credential.
    • Specify the Spreadsheet ID and Sheet Name where your website URLs are listed. Ensure your URLs are in a column that can be easily read.
  3. Configure HTTP Request Node (Node 19):
    • Update the URL to include your Google PageSpeed Insights API Key.
    • Ensure the request method is GET and the URL is correctly constructed to query the PageSpeed Insights API for each URL from your Google Sheet.
  4. Configure Code Node (Node 834):
    • Review the JavaScript code to ensure it correctly parses the PageSpeed Insights API response and extracts the desired metrics. Adjust property names if your API response structure differs.
  5. Configure If Node (Node 20):
    • Adjust the conditions to define your desired performance score thresholds for both mobile and desktop. For example, {{ $json.performanceScoreMobile < 50 }}.
  6. Configure Gmail Node (Node 356):
    • Set up your Gmail credential.
    • Customize the To, Subject, and Body fields of the email alert. Include relevant performance metrics from the previous nodes using expressions (e.g., {{ $json.url }}, {{ $json.performanceScoreMobile }}).
  7. Configure Schedule Trigger Node (Node 839):
    • Set your desired schedule for how often the workflow should run (e.g., daily, weekly).
  8. Activate the Workflow: Once configured, activate the workflow to start monitoring your website performance.

Optional: Webhook Trigger (Node 47) and Respond to Webhook (Node 535) The workflow includes a Webhook trigger and a "Respond to Webhook" node. This allows you to manually trigger the workflow or integrate it with other systems by sending an HTTP POST request to the webhook URL. The "Respond to Webhook" node can be used to send a custom response back to the trigger.

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://&lt;your-instance&gt;.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