Templates / Monitor weekly PageSpeed scores with Apify, Google Sheets, and Slack

Monitor weekly PageSpeed scores with Apify, Google Sheets, and Slack

Unknown

by PewterDesk · 0 views · created 2026-10-11 · Market Research

Unknown. This template uses community nodes we can't verify statically. Uses community nodes that can't be verified statically (unverified community packages are off by default in 3.0). Static check, last run 2026-10-19.

What this workflow does

This workflow has 7 nodes and runs on a schedule (every week at 07:00). Along the way it connects Google Sheets, Slack and Apify (community).

How it runs

Trigger: On a schedule (every week at 07:00).

  1. Your URLs and alert threshold (Edit Fields (Set)): sets 2 fields: urls, minPerformance
  2. Audit pages with PageSpeed Insights (Apify): run actor and get dataset (actors)
  3. Flatten to one row per page (Code): runs custom JavaScript code
  4. Log every result to Google Sheets (Google Sheets): append
  5. Build alert for slow pages (Code): runs custom JavaScript code
  6. Post alert to Slack (Slack): uses Slack

Services it uses

Google SheetsSlackApify (community)

Before you upgrade to n8n 3.0

We can't fully verify this one: it relies on 1 community package, and n8n 3.0 turns unverified community packages off by default (N8N_UNVERIFIED_PACKAGES_ENABLED=false).

  • Check that @apify/n8n-nodes-apify is verified or supports 3.0 (used in Audit pages with PageSpeed Insights).

Nodes used (6)

From the author

Quick overview Every Monday this workflow audits your list of pages with Google PageSpeed Insights (via the Bulk PageSpeed Insights & Core Web Vitals Checker Apify Actor), logs one row per page to Google Sheets, and posts to Slack only when a page drops below…

Excerpt from PewterDesk's description on n8n.io.

View the original on n8n.io → Check your own copy

Get the weekly “what broke” email

New templates, newly broken ones, and n8n release changes. One short email a week.

Form not loading? Subscribe here.