The flow
Starts it 1Logic 10Service 4
The steps in the order they run, from what starts it.
- 1A Workflow Asks For A PageExecute Workflow triggerStarts it
- 2SettingsSetLogic
- 3Read The RequestCodeLogic
- 4Look In The CacheData TableService
- 5Is It Still Fresh?CodeLogic
- 6Serve From Cache?IfLogic
- 7Straight From The CacheNo OpLogic
- 8Fetch The PageHttp RequestService
- 9Build The AnswerCodeLogic
- 10Read What Came BackCodeLogic
- 11Keep It For Next TimeData TableService
- 12Does It Need A Browser?IfLogic
- 13Try Again In A BrowserHttp RequestService
- 14The First Fetch Was FineNo OpLogic
- 15Read The Rendered PageCodeLogic
How it's built
- Starts on
- An event in a connected app
- Steps
- 15, with 2 branches
- Size
- Medium: a working afternoon
- Connects to
- n8n data table
- 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 an event in a connected app.
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. 15 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 15 steps before you point it at anything that matters.