The flow
Starts it 1Service 16
The steps in the order they run, from what starts it.
- 1Get ChromeOS deviceG Suite Admin ToolService
- 2Get many ChromeOS devicesG Suite Admin ToolService
- 3Update ChromeOS deviceG Suite Admin ToolService
- 4Change status of ChromeOS deviceG Suite Admin ToolService
- 5Create a groupG Suite Admin ToolService
- 6Delete a groupG Suite Admin ToolService
- 7Get a groupG Suite Admin ToolService
- 8Get many groupsG Suite Admin ToolService
- 9Update a groupG Suite Admin ToolService
- 10Add user to groupG Suite Admin ToolService
- 11Create a userG Suite Admin ToolService
- 12Delete a userG Suite Admin ToolService
- 13Get a userG Suite Admin ToolService
- 14Get many usersG Suite Admin ToolService
- 15Remove user from groupG Suite Admin ToolService
- 16Update a userG Suite Admin ToolService
- 17Google Workspace Admin Tool MCP ServerMcp triggerStarts it
How it's built
- Starts on
- An event in a connected app
- Steps
- 17
- 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. 17 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 17 steps before you point it at anything that matters.