The flow
Starts it 1Logic 6Service 6
The steps in the order they run, from what starts it.
- 1Weekly Monday 8AM TriggerSchedule triggerStarts it
- 2Calculate Date RangesCodeLogic
- 3Fetch GSC Recent 7 DaysHttp RequestService
- 4Fetch GSC Previous 28 DaysHttp RequestService
- 5Compare Periods and Detect DecayCodeLogic
- 6Filter Only Decaying PagesFilterLogic
- 7Log All Results to Decay SheetGoogle SheetsService
- 8Build Weekly Decay ReportCodeLogic
- 9Check If Any Critical PagesFilterLogic
- 10Post Report to SlackSlackService
- 11Email Weekly ReportEmail SendService
- 12Generate Fix Tasks for Critical PagesCodeLogic
- 13Log Fix Tasks to SheetGoogle SheetsService
How it's built
- Starts on
- A clock
- Steps
- 13
- Size
- Medium: a working afternoon
- Connects to
- Email, Google Sheets, Slack
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own Email, Google Sheets and Slack 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.
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.