Resources · n8n integration

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

Why automate

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.

Connect

How do you connect Google Workspace Admin to n8n?

  1. 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.

  2. 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.cloud for the hosted service, or the domain of the instance when self-hosting.

  3. 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.

Actions

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.

Resources × operations matrix
ResourceCreateGetGet ManyUpdateDeleteAdd to GroupChange StatusRemove From Group
ChromeOS Device
Group
User

ChromeOS Device

4 operations
01

Get ChromeOS device

device.get

What 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: basic leaves custom fields out, full includes every field attached to the device.
Use cases
a helpdesk ticket that automatically carries the full record of the Chromebook it is about.
02

Get many ChromeOS devices

device.getAll

What 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, basic leaves custom fields out, full includes 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 lastSync or serialNumber.
Use cases
a weekly export of devices that have not synced recently.
03

Update ChromeOS device

device.update

What 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.
Use cases
tagging a laptop with its new owner when a loan is recorded.
04

Change status of ChromeOS device

device.changeStatus

What 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: disable disables a chromebook, reenable brings a disabled one back.
Use cases
a lost laptop reported in a form gets disabled in seconds, and re-enabled by the same workflow when it turns up in a drawer two days later.

Group

5 operations
05

Create a group

group.create

What 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.
Use cases
spinning up a per-project alias when a deal is marked won.
06

Delete a group

group.delete

What 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.
Use cases
a quarterly cleanup that deletes the project aliases archived in a tracking sheet, after a human approval step in the workflow. Worth pairing with group.get first, so the record is logged before it is gone.
07

Get a group

group.get

What 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.
Use cases
an approval flow that shows the group name and description in a Slack message before anyone confirms adding a contractor to it.
08

Get many groups

group.getAll

What 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.
Use cases
an access review listing every group one employee can read.
09

Update a group

group.update

What 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.
Use cases
renaming a team alias after a reorg, driven by a single row edited in a spreadsheet.

User

7 operations
10

Add user to group

user.addToGroup

What 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.
Use cases
giving a new hire the three aliases their role requires, with one node per group in the onboarding workflow.
11

Create a user

user.create

What 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.smith on example.com becomes n.smith@example.com.
  • Change Password at Next Login: forces a reset on first sign-in.
Use cases
provisioning an account the day a signed contract lands.
12

Delete a user

user.delete

What 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.
Use cases
a retention workflow that waits a fixed delay after a departure, checks that the mailbox has been transferred, then closes the account permanently.
13

Get a user

user.get

What 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: simplified returns a short set including primaryEmail, isAdmin, lastLoginTime and suspended; raw returns the whole API response; select hands control to Fields.
  • Custom Fields: set it to Custom and list the schemas in Custom Schema Names or IDs to pull company-specific attributes.
Use cases
checking lastLoginTime before flagging a dormant account.
14

Get many users

user.getAll

What you see in n8n

Notes & use cases

Exports the directory, which is the operation most reporting workflows start from.

Key parameters

  • Output: required, simplified keeps the payload small on large domains, raw keeps everything.
  • Custom Fields: required, basic excludes custom fields, custom pulls the schemas named in Custom Schema Names or IDs, itself required, full includes 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.
Use cases
a monthly headcount reconciliation against the HR tool.
15

Remove user from group

user.removeFromGroup

What 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.
Use cases
someone moves from support to sales, so the workflow strips the support aliases and adds the sales ones in the same run, with no mailbox interruption.
16

Update a user

user.update

What 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.
Use cases
suspending an account the hour a departure is announced.
Need help

Need help automating Google Workspace Admin with n8n?

A person reads every message.

FAQ

Google Workspace Admin and n8n: common questions

01Is the Google Workspace Admin n8n integration free?
Yes on the n8n side. The node ships with n8n, so there is nothing to install and no extra cost, whether the workflows run on n8n Cloud or on a self-hosted instance under the Community Edition and its Sustainable Use license. A workflow built on one runs identically on the other. What the Google Workspace subscription itself costs is a separate matter, and it depends on the plan the organization already holds. The credential is created once in the Credentials menu and reused by every workflow that touches the directory, so the setup cost is paid a single time rather than per automation.
02Which credentials and permissions are needed?
A Google credential. On n8n Cloud, Managed OAuth2 is the quickest route: click Sign in with Google in the credentials screen, and nothing else needs configuring in the Google Cloud Console. Self-hosted instances use Custom OAuth2 instead, which means creating a project in the Google Cloud Console, enabling the APIs, configuring the OAuth consent screen with an App name, a User support email and an Audience, then generating a Web application OAuth client ID and pasting the client ID and client secret into n8n. Service Account credentials are documented too, but Google recommends OAuth2 for most cases because it is easier to set up.
03What are the limits of the Google Workspace Admin node?
Three worth planning around. The node exposes 16 operations across 3 resources, so anything outside users, groups and ChromeOS devices needs the HTTP Request node, which calls any Admin SDK endpoint and reuses the same Google credential through predefined authentication. Listing operations return a capped number of items unless Return All is enabled, in which case n8n pages through the API until the list is complete. And passwords set through the node have to be at least 8 characters and at most 100, so a generator feeding that field needs to respect both ends of the range.
04Does the integration react in real time to directory changes?
No, because this tool has no trigger node in n8n. A workflow that touches Google Workspace Admin has to start somewhere else: a Schedule Trigger that runs at a fixed interval, an n8n Webhook that a third-party service calls, or the trigger of another tool in the stack. In practice, most directory automations are driven by the system that holds the truth about people. An HR tool posting to a webhook, a spreadsheet row, a form submission or a message in a chat tool all work as entry points, and the Google Workspace Admin node then does the directory work.
05n8n or Make for Google Workspace Admin?
It depends on four things. Hosting first: n8n runs self-hosted through Docker or npm, or on n8n Cloud, while Make is hosted only. Data control follows from that, and directory data is about employees, which makes the question less theoretical than usual. Cost model next: Make bills per operation, so a nightly export of every user and device is priced very differently from one platform to the other. Visual logic last, since both build workflows on a canvas and the preference is genuinely personal. Teams already running containers usually land on n8n, teams with no infrastructure appetite often do not.
Hack'celeration Lab

Get our weekly integration tips.

No spam. Unsubscribe anytime.