The flow
Starts it 1Service 10
The steps in the order they run, from what starts it.
- 1Create a new BucketGoogle Cloud Storage ToolService
- 2Delete an empty BucketGoogle Cloud Storage ToolService
- 3Get a BucketGoogle Cloud Storage ToolService
- 4Get a list of Buckets for a given projectGoogle Cloud Storage ToolService
- 5Update the metadata of a BucketGoogle Cloud Storage ToolService
- 6Create an objectGoogle Cloud Storage ToolService
- 7Delete an object from a bucketGoogle Cloud Storage ToolService
- 8Get object data or metadataGoogle Cloud Storage ToolService
- 9Get a list of objectsGoogle Cloud Storage ToolService
- 10Update an object's metadataGoogle Cloud Storage ToolService
- 11Google Cloud Storage Tool MCP ServerMcp triggerStarts it
How it's built
- Starts on
- An event in a connected app
- Steps
- 11
- 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. 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.
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 11 steps before you point it at anything that matters.