The flow
Starts it 2Logic 7Service 2
The steps in the order they run, from what starts it.
- 1When clicking ‘Test workflow’Manual triggerStarts it
- 2When Executed by Another WorkflowExecute Workflow triggerStarts it
- 3Dummy input dataSetLogic
- 4Split the desired pathCodeLogic
- 5Create desired pathCodeLogic
- 6Check if top folder existsGoogle DriveService
- 7If top folder doesn't existIfLogic
- 8Create new subfolderGoogle DriveService
- 9Set parameters for next runCodeLogic
- 10If path has been completely createdIfLogic
- 11Return the ID of the last folderSetLogic
How it's built
- Starts on
- An event in a connected app
- Steps
- 11, with 2 branches
- Size
- Medium: a working afternoon
- Connects to
- Google Drive
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own Google Drive 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. 11 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 11 steps before you point it at anything that matters.