The flow
Starts it 2Logic 11Service 7
The steps in the order they run, from what starts it.
- 1inputExecute Workflow triggerStarts it
- 2Start testingManual triggerStarts it
- 3Get drive urlHttp RequestService
- 4hasFileIfLogic
- 5Get fileHttp RequestService
- 6Convert to FileConvert To FileService
- 7No file ErrorStop And ErrorLogic
- 8Convert file to base64 stringExtract From FileService
- 9getFileSizeInBytesCodeLogic
- 10Upload fileExecute WorkflowLogic
- 11createSessionHttp RequestService
- 12MergeMergeLogic
- 13isGraterThenMaxIfLogic
- 14No free disk spaceStop And ErrorLogic
- 15SplitFileToChunksCodeLogic
- 16Convert parts to FileConvert To FileService
- 17Loop Over File ChunksSplit In BatchesLogic
- 18resultLimitLogic
- 19getUrlSetLogic
- 20loadFileHttp RequestService
How it's built
- Starts on
- An event in a connected app
- Steps
- 20, with 2 branches, 1 loop 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. 20 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 20 steps before you point it at anything that matters.