The flow
Starts it 1Logic 8Service 2
The steps in the order they run, from what starts it.
- 1Start ExecutionExecute Workflow triggerStarts it
- 2Get children folders from folder idGoogle DriveService
- 3If parent folder has nested folders or notIfLogic
- 4Start sub-executionExecute WorkflowLogic
- 5If parent folder has no folderIfLogic
- 6Get all folder idsCodeLogic
- 7Return parent folder idSetLogic
- 8Return parent folder id to sub-workflowSetLogic
- 9Loop Over folder idsSplit In BatchesLogic
- 10Return all file idsSetLogic
- 11Get all files inside a folderGoogle DriveService
How it's built
- Starts on
- An event in a connected app
- Steps
- 11, with 2 branches, 1 loop or waits
- 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.