The flow
Starts it 3Logic 11Service 5
The steps in the order they run, from what starts it.
- 1Deploy HookWebhookStarts it
- 2SettingsSetLogic
- 3Pick The URLs To CheckCodeLogic
- 4One Item Per URLSplit OutLogic
- 5Ask For robots.txtHttp RequestService
- 6Ask For The SitemapHttp RequestService
- 7Fetch Each PageHttp RequestService
- 8Read robots.txtCodeLogic
- 9Read The SitemapCodeLogic
- 10Check Every PageCodeLogic
- 11Put The Checks TogetherMergeLogic
- 12Decide Pass Or FailCodeLogic
- 13How Did It Go?SwitchLogic
- 14Write The Blocking MessageCodeLogic
- 15Write The Warning MessageCodeLogic
- 16Let The Deploy ThroughRespond To WebhookStarts it
- 17Tell The Channel It FailedSlackService
- 18Tell The Channel About The WarningsSlackService
- 19Fail The DeployRespond To WebhookStarts it
How it's built
- Starts on
- Another system calling it
- Steps
- 19, with 1 branch
- Size
- Medium: a working afternoon
- Connects to
- Slack
- 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 another system calling it.
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. 19 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 19 steps before you point it at anything that matters.