The flow
Starts it 1Service 17
The steps in the order they run, from what starts it.
- 1Copy fileGoogle Drive ToolService
- 2Create file from textGoogle Drive ToolService
- 3Delete a fileGoogle Drive ToolService
- 4Download fileGoogle Drive ToolService
- 5Move fileGoogle Drive ToolService
- 6Share fileGoogle Drive ToolService
- 7Update fileGoogle Drive ToolService
- 8Upload fileGoogle Drive ToolService
- 9Search files and foldersGoogle Drive ToolService
- 10Create folderGoogle Drive ToolService
- 11Delete folderGoogle Drive ToolService
- 12Share folderGoogle Drive ToolService
- 13Create shared driveGoogle Drive ToolService
- 14Delete shared driveGoogle Drive ToolService
- 15Get shared driveGoogle Drive ToolService
- 16Get many shared drivesGoogle Drive ToolService
- 17Update shared driveGoogle Drive ToolService
- 18Google Drive Tool MCP ServerMcp triggerStarts it
How it's built
- Starts on
- An event in a connected app
- Steps
- 18
- 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. 18 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 18 steps before you point it at anything that matters.