The flow
Starts it 1Logic 7Service 5
The steps in the order they run, from what starts it.
- 1Start migrationManual triggerStarts it
- 2Set config variablesSetLogic
- 3Get SmartSuite recordsHttp RequestService
- 4Split out recordsSplit OutLogic
- 5Extract files from recordsCodeLogic
- 6Loop over filesSplit In BatchesLogic
- 7Find matching Monday itemHttp RequestService
- 8Extract Monday item IDCodeLogic
- 9Item found?IfLogic
- 10Get file download URLHttp RequestService
- 11Download file from SmartSuiteHttp RequestService
- 12Upload file to MondayHttp RequestService
- 13Rate limit delayWaitLogic
How it's built
- Starts on
- An event in a connected app
- Steps
- 13, with 1 branch, 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 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. 13 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 13 steps before you point it at anything that matters.