The flow
Starts it 1Logic 7Service 6
The steps in the order they run, from what starts it.
- 1When Every Day at 5AMSchedule triggerStarts it
- 2Fetch SitemapHttp RequestService
- 3Extract Sitemap URLsCodeLogic
- 4Notify Sitemap Failure on SlackSlackService
- 5Loop Over Sitemap URLsSplit In BatchesLogic
- 6Log Findings to Google SheetsGoogle SheetsService
- 7Build Error Page ReportCodeLogic
- 8Analyze Page for Error ContentSnapshot SiteService
- 9Check for Error PagesIfLogic
- 10Check for API ErrorIfLogic
- 11Record Unreachable URLSetLogic
- 12Notify Error Pages on SlackSlackService
- 13Notify All Clear on SlackSlackService
- 14Detect Error PageCodeLogic
How it's built
- Starts on
- A clock
- Steps
- 14, with 2 branches, 1 loop or waits
- Size
- Medium: a working afternoon
- Connects to
- Google Sheets, Slack
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own 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. 14 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 itNothing 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 14 steps before you point it at anything that matters.