The flow
Starts it 1Logic 12Service 5
The steps in the order they run, from what starts it.
- 1When Every 10 MinutesSchedule triggerStarts it
- 2Read Uptime WatchlistGoogle SheetsService
- 3Loop Over Watched PagesSplit In BatchesLogic
- 4All Pages CheckedNo OpLogic
- 5Analyze Page AvailabilitySnapshot SiteService
- 6Check for API ErrorIfLogic
- 7Record Page DownSetLogic
- 8Evaluate AvailabilityCodeLogic
- 9Detect State ChangeCodeLogic
- 10Check Whether Page Is UpIfLogic
- 11Check for State ChangeIfLogic
- 12Compare Page to BaselineSnapshot SiteService
- 13Notify State Change on SlackSlackService
- 14Build Watchlist RowSetLogic
- 15Check for Compare API ErrorIfLogic
- 16Record Visual Check FailureSetLogic
- 17Update Watchlist StateGoogle SheetsService
- 18Evaluate Visual DriftCodeLogic
How it's built
- Starts on
- A clock
- Steps
- 18, with 4 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. 18 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 18 steps before you point it at anything that matters.