The flow
Starts it 2Logic 22
The steps in the order they run, from what starts it.
- 1Schedule TriggerSchedule triggerStarts it
- 2➡️ First, Rename Me!No OpLogic
- 3➡️ Let's add a new nodeNo OpLogic
- 4➡️ Select these three nodesNo OpLogic
- 5➡️ Now select everythingNo OpLogic
- 6Execute Set NodeManual triggerStarts it
- 7Node ANo OpLogic
- 8Test NodeNo OpLogic
- 9➡️ Now, Edit Me!SetLogic
- 10Node 2No OpLogic
- 11➡️ Zoom out to see it allNo OpLogic
- 12➡️ Pin My DataSetLogic
- 13Node BNo OpLogic
- 14Test IFIfLogic
- 15➡️ This one is extra. Deactivate Me!No OpLogic
- 16Node 3No OpLogic
- 17➡️ Open the Execution Data PanelNo OpLogic
- 18Node CNo OpLogic
- 19Test Node (1)No OpLogic
- 20Test Node (2)No OpLogic
- 21➡️ We need another one. Duplicate Me!No OpLogic
- 22➡️ Copy MeNo OpLogic
- 23➡️ Delete me!No OpLogic
- 24➡️ Add a Sticky NodeNo OpLogic
How it's built
- Starts on
- A clock
- Steps
- 24, with 1 branch
- Size
- Large: read it before trusting it with anything live
- 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 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 24 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 24 steps before you point it at anything that matters.