- Home
- Resources
- Integrations
- Google Workspace Admin
Google Workspace Admin n8n integrationAutomate Google Workspace Admin with n8n.
Directory work is the part of IT nobody schedules and everybody does twice. The Google Workspace Admin n8n integration exposes 16 operations across 3 resources: users, groups and ChromeOS devices. There is no trigger node for this tool, so the workflow starts elsewhere.
Verified Trustpilot reviews · AI, automation & growth agency
What does the Google Workspace Admin n8n integration actually cover?
The Google Workspace Admin n8n integration drives the Google Admin SDK from a workflow, so accounts, mailing groups and Chromebooks get handled without anyone opening the admin console. The node ships with n8n and groups its 16 operations under 3 resources: User, Group and ChromeOS Device. Each one maps to a single API call, with the fields laid out as dropdowns instead of JSON payloads.
Onboarding is the obvious one. A row lands in a spreadsheet, the workflow reads it with Google Sheets, calls user.create with the first name, last name, domain and a starting password, then chains user.addToGroup so the new account already receives the team mailing list on day one. The template gallery has a published onboarding flow that combines the node with Sheets and Gmail for the welcome message.
Offboarding is the same story played backwards, and it is the one that actually protects the company. A form or a Slack message fires the workflow, user.update flips Suspend on so the person cannot sign in, user.removeFromGroup pulls them out of the distribution lists, and device.changeStatus disables the Chromebook they were using. Nothing gets deleted, so the data stays recoverable while HR finishes the paperwork.
The third pattern is inventory. A Schedule Trigger runs device.getAll with Return All enabled every morning, pushes the ChromeOS fleet into a sheet, and flags anything whose annotated user no longer matches an active account pulled from user.getAll. Same idea for groups: group.getAll with the Query filter gives an auditable list of who owns which alias.
Where the node stops, the HTTP Request node takes over. Aliases, org unit management, roles beyond the ones listed in the Roles parameter, mobile device management and reporting are not operations here. HTTP Request calls any Admin SDK endpoint and reuses the same Google credential through predefined authentication, so nothing needs to be rebuilt. Two other limits worth knowing before building: there is no trigger node for this tool, and passwords set through the node have to sit between 8 and 100 characters. Teams that want a walkthrough on the whole pattern can look at the n8n training.
How do you connect Google Workspace Admin to n8n?
- 01
Create the Google Cloud project
Authentication goes through a Google credential, and n8n Cloud users get the short path: click Sign in with Google in the credentials screen and Managed OAuth2 handles the rest, with nothing to configure in the Google Cloud Console. Self-hosted instances do not get Managed OAuth2, so the route is Custom OAuth2: create a Google Cloud Console project, then enable the APIs the node needs access to.
- 02
Configure the consent screen
In APIs & Services > OAuth consent screen, fill in the App name and the User support email, then pick the Audience. Internal covers users inside the organization's Google Workspace, External covers any Google account. Under Branding, add an authorized domain:
n8n.cloudfor the hosted service, or the domain of the instance when self-hosting. - 03
Paste the client ID and secret
Back in Credentials, choose + Create credentials, then OAuth client ID, with Web application as the application type. Copy the OAuth Redirect URL shown in the n8n credential and paste it into Authorized redirect URIs in the Google console. The credential is created once in the Credentials menu and then shows up in the node's dropdown for every workflow.
The 16 operations of the Google Workspace Admin node
The Google Workspace Admin node exposes 16 operations across 3 resources. For each one: the node as you configure it in n8n, the required fields, and our field notes.
| Resource | Create | Get | Get Many | Update | Delete | Add to Group | Change Status | Remove From Group |
|---|---|---|---|---|---|---|---|---|
| ChromeOS Device | ✓ | ✓ | ✓ | ✓ | ||||
| Group | ✓ | ✓ | ✓ | ✓ | ✓ | |||
| User | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
Operations index
ChromeOS Device
4 operationsGet ChromeOS device
device.getWhat you see in n8n
Notes & use cases
Returns one ChromeOS device record, so the rest of the workflow can read its details before deciding anything.
Key parameters
- Device: selects the device to retrieve, picked from the list or passed as an expression such as
{{ $json.deviceId }}when the identifier comes from an earlier node. - Output:
basicleaves custom fields out,fullincludes every field attached to the device.
Get many ChromeOS devices
device.getAllWhat you see in n8n
Notes & use cases
Lists the Chromebooks enrolled in the domain, which is the starting point of any fleet inventory.
Key parameters
- Output: required,
basicleaves custom fields out,fullincludes every field attached to each device. - Return All: on, n8n walks the API pages until every device is collected; off, Limit caps how many come back.
- Include Children: includes devices from organizational units below the one selected.
- Query: filters with Google's querying syntax, and Order By sorts on values such as
lastSyncorserialNumber.
Update ChromeOS device
device.updateWhat you see in n8n
Notes & use cases
Writes the administrative metadata of a Chromebook back to the directory, the part Google calls annotations.
Key parameters
- Device: the device to modify, required.
- Update Fields: Annotated User and Annotated Location record who holds the machine and where it sits, Annotated Asset ID carries the internal asset tag, Notes stores free text, and Move to Organizational Unit Name or ID takes the full path of the target unit.
Change status of ChromeOS device
device.changeStatusWhat you see in n8n
Notes & use cases
Switches a Chromebook between usable and blocked, without touching anything else on the record.
Key parameters
- Device: the device to act on.
- Status:
disabledisables a chromebook,reenablebrings a disabled one back.
Group
5 operationsCreate a group
group.createWhat you see in n8n
Notes & use cases
Opens a new Google group, which becomes both a mailing address and a permission handle.
Key parameters
- Group Email: the group's address, for example
sales@example.com; it has to be unique, and on a multi-domain account the right domain gets picked here. - Group Name: the display name shown to members.
- Description: an extended description explaining who should join and what gets sent there.
Delete a group
group.deleteWhat you see in n8n
Notes & use cases
Removes a group from the directory. The address stops accepting mail and the permissions attached to it disappear with it.
Key parameters
- Group: the group to act on, chosen from the list or resolved from an expression.
group.get first, so the record is logged before it is gone.Get a group
group.getWhat you see in n8n
Notes & use cases
Fetches a single group and its details, which is how a workflow checks that an alias exists before writing to it.
Key parameters
- Group: identifies the group, selected in the dropdown or supplied by a previous node.
Get many groups
group.getAllWhat you see in n8n
Notes & use cases
Reads several groups at once, with filters that decide what the list actually contains.
Key parameters
- Return All: brings back every group across API pages; turned off, Limit sets the maximum.
- Domain: restricts results to one domain, while Customer targets the unique ID of the Workspace account.
- User ID: takes an email or immutable ID and lists the groups that user belongs to.
Update a group
group.updateWhat you see in n8n
Notes & use cases
Edits an existing group in place, keeping its members and history intact.
Key parameters
- Group: the group being modified, required.
- Update Fields: Name changes the display name, Description rewrites the extended description, and Email moves the group to another address, which still has to be unique.
User
7 operationsAdd user to group
user.addToGroupWhat you see in n8n
Notes & use cases
Attaches an existing account to a group, which is how mailing lists and shared access get granted.
Key parameters
- User: the account to add, usually carried over as
{{ $json.primaryEmail }}from the operation that created it. - Group: the destination group.
Create a user
user.createWhat you see in n8n
Notes & use cases
Creates a Workspace account and returns it, ready to receive mail.
Key parameters
- First Name and Last Name: both required, the identity shown in the directory.
- Password: minimum 8 characters, maximum 100.
- Domain Name or ID: the domain the address belongs to, combined with Username, so
n.smithon example.com becomes n.smith@example.com. - Change Password at Next Login: forces a reset on first sign-in.
Delete a user
user.deleteWhat you see in n8n
Notes & use cases
Erases an account from the directory for good, so it belongs at the very end of an offboarding sequence rather than at the start.
Key parameters
- User: the account to delete, selected in the node or resolved from an expression.
Get a user
user.getWhat you see in n8n
Notes & use cases
Reads one account and decides how much of it to return.
Key parameters
- User: the account to look up.
- Output:
simplifiedreturns a short set including primaryEmail, isAdmin, lastLoginTime and suspended;rawreturns the whole API response;selecthands control to Fields. - Custom Fields: set it to Custom and list the schemas in Custom Schema Names or IDs to pull company-specific attributes.
Get many users
user.getAllWhat you see in n8n
Notes & use cases
Exports the directory, which is the operation most reporting workflows start from.
Key parameters
- Output: required,
simplifiedkeeps the payload small on large domains,rawkeeps everything. - Custom Fields: required,
basicexcludes custom fields,custompulls the schemas named in Custom Schema Names or IDs, itself required,fullincludes all of them. - Return All: pages through every account; off, Limit stops the export short.
- Show Deleted: retrieves the list of deleted users instead of the active ones.
- Query: filters using the Admin SDK search syntax.
Remove user from group
user.removeFromGroupWhat you see in n8n
Notes & use cases
Detaches an account from a group while leaving the account itself untouched, which is the difference that matters during a role change.
Key parameters
- User: the member being removed.
- Group: the group losing that member.
Update a user
user.updateWhat you see in n8n
Notes & use cases
Modifies an existing account, and carries the widest set of fields in the node with 11 of them.
Key parameters
- User: the account to modify, required.
- Suspend: on, the user is suspended; off, the user is reactivated; left out, the status stays as it is.
- Primary Email: must stay unique and cannot be an alias of another user.
- Roles: assigns admin roles such as Help Desk Admin or Groups Admin.
Need help automating Google Workspace Admin with n8n?
A person reads every message.
Google Workspace Admin and n8n: common questions
01Is the Google Workspace Admin n8n integration free?
02Which credentials and permissions are needed?
03What are the limits of the Google Workspace Admin node?
04Does the integration react in real time to directory changes?
05n8n or Make for Google Workspace Admin?
Get our weekly integration tips.
No spam. Unsubscribe anytime.


