The flow
Starts it 1Model 2Logic 12Service 4
The steps in the order they run, from what starts it.
- 1When chat message receivedChat triggerStarts it
- 2Parse & Normalise URLsCodeLogic
- 3Early Exit CheckIfLogic
- 4Respond - No Valid URLsCodeLogic
- 5Split Valid URLsItem ListsLogic
- 6Reachability CheckHttp RequestService
- 7Filter ReachableCodeLogic
- 8Second Early ExitIfLogic
- 9AggregateAggregateLogic
- 10Split Reachable URLsItem ListsLogic
- 11Respond to ChatChatModel
- 12LoopSplit In BatchesLogic
- 13Convert to FileConvert To FileService
- 14PageSpeed APIHttp RequestService
- 15Upload to UguuHttp RequestService
- 16WaitWaitLogic
- 17Extract LinkCodeLogic
- 18Extract PageSpeed DataCodeLogic
- 19Final ChatChatModel
How it's built
- Starts on
- Someone opening a chat with it
- Steps
- 19, with 2 branches, 2 loops or waits
- Size
- Medium: a working afternoon
- Connects to
- Nothing by connector; it calls services over plain HTTP
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account. You connect your own accounts after importing it; none are included.
What starts it?
It starts on someone opening a chat with 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.