Automation library · Data collection

Track daily PageSpeed scores with Google PageSpeed API

Started by a clock, and works across Gmail and Google Sheets. 13 steps, 1 branch: a working afternoon to understand properly.

Medium

13 stepsMedium: a working afternoon
1Branch: places the flow splits
0Loops or waits
2Services it connects to

The flow

Starts it 1Logic 7Service 5

The steps in the order they run, from what starts it.

  1. 1Schedule TriggerSchedule triggerStarts it
  2. 2ConfigurationSetLogic
  3. 3HTTP Request MobileHttp RequestService
  4. 4HTTP Request DesktopHttp RequestService
  5. 5Merge PageSpeed ResultsCodeLogic
  6. 6Save Metrics to Google SheetsGoogle SheetsService
  7. 7Check Performance ThresholdIfLogic
  8. 8Generate Success EmailHtmlLogic
  9. 9Generate Alert EmailHtmlLogic
  10. 10Send Success EmailGmailService
  11. 11Send Alert EmailGmailService
  12. 12No Operation, do nothing1No OpLogic
  13. 13No Operation, do nothingNo OpLogic

How it's built

Starts on
A clock
Steps
13, with 1 branch
Size
Medium: a working afternoon
Connects to
Gmail, Google Sheets
Model
None. This is plumbing, not judgement

Questions

What does it need to run?

An n8n account, plus your own Gmail and Google Sheets accounts. You connect your own accounts after importing it; none are included.

What starts it?

It starts on a clock.

Does it use AI?

No. Every step is fixed logic or a call to a service, so it does the same thing every time.

How long does it take to set up?

Plan an afternoon. 13 steps is enough that you should read each one before running it.

How do I import it?

Copy the workflow, open a new workflow in n8n and paste. The steps appear on the canvas, ready for your own accounts.

Before you run it

Nothing here has been tested by us. It is somebody's working automation, read and described from its own steps. Treat the connections it wants as a list of accounts it will touch, and read the 13 steps before you point it at anything that matters.