The flow
Starts it 2Logic 13Service 7
The steps in the order they run, from what starts it.
- 1Check Every MondaySchedule triggerStarts it
- 2Or Run It NowManual triggerStarts it
- 3SettingsSetLogic
- 4Fetch The SitemapHttp RequestService
- 5Read The SitemapCodeLogic
- 6Is It An Index Of Sitemaps?IfLogic
- 7Fetch Each Child SitemapHttp RequestService
- 8Gather Every Page URLMergeLogic
- 9Read The Child SitemapsCodeLogic
- 10Pick The Pages To CrawlCodeLogic
- 11Fetch Each PageHttp RequestService
- 12Collect Every LinkCodeLogic
- 13Check Each Link OnceHttp RequestService
- 14Judge Every LinkCodeLogic
- 15Read What You ReportedData TableService
- 16Only The New ProblemsCodeLogic
- 17Anything New To Report?IfLogic
- 18Build The ReportCodeLogic
- 19Nothing New This WeekNo OpLogic
- 20Post The ReportSlackService
- 21One Row Per ProblemCodeLogic
- 22Remember What You ReportedData TableService
How it's built
- Starts on
- A clock
- Steps
- 22, with 2 branches
- Size
- Large: read it before trusting it with anything live
- Connects to
- Slack, n8n data table
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own Slack account. 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?
Take your time. At 22 steps it is large: read it before trusting it with anything live.
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 22 steps before you point it at anything that matters.