The flow
Starts it 1Logic 12Service 3
The steps in the order they run, from what starts it.
- 1Every 3 Days At 10AMSchedule triggerStarts it
- 2Generate Random PageCodeLogic
- 3Get 100 Tokens From CMCHttp RequestService
- 4Split OutSplit OutLogic
- 5CLEAN CMC FIELDSSetLogic
- 6CMC SPLIT IN BATCHESSplit In BatchesLogic
- 7DATACodeLogic
- 8Get Token Details From CMCHttp RequestService
- 9CMC Token DATACodeLogic
- 10EXTRACT WEBSITESetLogic
- 11ADD TO CMCSplit In BatchesLogic
- 12CLEAN WEBSITESetLogic
- 13No Operation, do nothing3No OpLogic
- 14ADD TO CMC SheetNoco DbService
- 15Wait 1 MinWaitLogic
- 16Clean up OutputSetLogic
How it's built
- Starts on
- A clock
- Steps
- 16, 3 loops or waits
- Size
- Medium: a working afternoon
- Connects to
- NocoDB
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own NocoDB 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?
Plan an afternoon. 16 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.
Before you run itNothing 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 16 steps before you point it at anything that matters.