Google Workspace Admin Make integrationAutomate Google Workspace Admin with Make.
Can Make take user and role chores off your Google Workspace console? The Google Workspace Admin Make integration offers 23 modules: 1 scheduled trigger, 17 actions and 5 searches. This page takes an IT or ops lead from connection to a first live scenario.
Verified Trustpilot reviews · AI, automation & growth agency
What can the Google Workspace Admin Make integration automate?
The integration links your Google Workspace admin account to Make, the no-code tool where you build a scenario: an automation made of modules, each module being one brick such as a trigger, an action or a search. Make can then create users, hand out roles and manage organizational units while you work on something else.
Onboarding that starts on its own. Watch Users spots each account created in your domain and hands it to the next module, for example Assign a User to a Role, so a new IT hire gets the right admin role without a ticket.
A clean offboarding path. When your HR tool marks a departure, Get a User pulls the account details, Update a User changes what needs changing, and Delete a User removes the account once the handover is done.
A readable map of your admin setup. List Roles, List Role Assignments and List Privileges return what exists today, ready to be written into a sheet that your security review can read without console access.
What the listed modules do not cover, Make an API Call can reach with the same connection. The same app also has a Google Workspace Admin n8n integration, and the n8n vs Make comparison helps you choose. For the basics of the editor, the Make training starts from zero.
How do you connect Google Workspace Admin to Make?
- 01
Add a module and start the connection
Open your scenario, add any Google Workspace Admin module, then click Create a connection. A connection is your admin account linked to Make once; every module of this app reuses it afterward.
- 02
Name it so you recognize it later
Giving the connection a name is optional, but it helps when several admins share one Make organization. Something like the domain plus the account that signs in keeps the list readable.
- 03
Authorize Make and save
Authorize Make on the page the app opens (or paste the key it gives you, if that is what it asks for), then click Save. From then on, every module of the app can work with your users, roles and organizational units.
Your first scenario: give every new user a role
GoalWhen a new user appears in Google Workspace, Make assigns that user to the role you chose.
- 01
Create the scenario and add Watch Users
On the Scenarios page, create a new scenario and click the +. Search for Google Workspace Admin, pick Watch Users and select your connection.
- 02
Fill in the trigger
Complete the fields Make shows for Watch Users. Once the connection exists, Make lists what it can read in your domain, so you choose from a list instead of typing values.
- 03
Add Assign a User to a Role
Click the + on the right of Watch Users and add Assign a User to a Role. Map the user coming from the first module, then choose the role to hand out.
- 04
Test with Run once
Create a test user in your domain, then click Run once. Open the bubble above each module to read the bundles it received, a bundle being one item passed along, here one user.
- 05
Schedule it and switch it on
On the first module, open the clock: a new scenario runs every 15 minutes by default, and 15 minutes is also the shortest interval on the Free plan. Then switch the scenario on.
What starts a Google Workspace Admin scenario
1 module starts a scenario when something happens in Google Workspace Admin. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Google Workspace Admin as soon as it happens.
Watch Users
Scheduled triggerIn Make“Triggers when a new user is created.”
Watch Users gives your scenario a starting point each time a new account is created in your Google Workspace domain, so onboarding steps begin without anyone copying names from the console. Each new user reaches the next module as its own bundle.
Every Google Workspace Admin module, and when to pick it
Google Workspace Admin gives you 22 modules. For each one: what it does for you, when to reach for it, and what to watch out for.
Assign a User to a Role
ActionIn Make“Assigns a user to a specific role.”
This module puts one account into one admin role, so the person gets their rights without someone opening the Admin console. It is the natural follow-up to Watch Users in an onboarding flow.
Create an Organizational Unit
ActionIn Make“Creates a new organizational unit.”
A new organizational unit appears in your domain straight from the scenario, ready to receive users and settings. Handy when your structure follows something that already lives in another tool.
Create a Role
ActionIn Make“Creates a new role.”
With Create a Role, a custom admin role is born from the scenario, which keeps role creation consistent when several domains or teams follow the same model. Pair it with List Privileges to see what can go into it.
Create a User
ActionIn Make“Creates a new user.”
Accounts get created for you from data that already exists elsewhere, such as a signed offer or an HR form, so nobody retypes names and addresses. Of all 23 modules, this one saves the most manual clicks at onboarding.
Delete an Organizational Unit
ActionIn Make“Deletes an organizational unit.”
Removing an organizational unit from a scenario keeps your structure in step with reality once a team or site closes. The unit disappears from your domain without a manual pass through the console.
Delete a Role
ActionIn Make“Deletes a role.”
Old custom roles leave your domain through this module, which trims the list admins scroll through and removes profiles nobody should be handed anymore.
Delete a Role Assignment
ActionIn Make“Deletes a role assignment.”
Here the link between one person and one role is cut, while the account itself stays active. That is the clean way to take admin rights back from someone who changes job inside the company.
Delete a User
ActionIn Make“Deletes a user.”
Offboarding ends with the account removed from your domain, triggered by the event you choose rather than a reminder in someone's calendar.
Get an Organizational Unit
ActionIn Make“Gets the details of an organizational unit.”
You receive the details of one organizational unit, ready to map into the next module or into a report. Useful when a later step needs facts about the unit rather than just its name.
Get a Role
ActionIn Make“Gets the details of a role.”
One role comes back with its details, which lets the scenario check what it is about to assign or change. Think of it as a quick look before acting.
Get a Role Assignment
ActionIn Make“Gets the details of a role assignment.”
Pick one role assignment and the module returns its details: who holds which role. This gives an audit trail or an approval step something precise to show.
Get a User
ActionIn Make“Gets the details of a user.”
The full record of one account arrives in the scenario, so the following modules can use its details without asking anyone. It often sits between a trigger from another app and an update in Workspace.
Make an API Call
ActionIn Make“Performs an arbitrary authorized API call.”
Anything the Google Workspace Admin API offers but the other modules do not cover becomes reachable, using the connection you already set up. No extra login to manage.
Make a User a Super Admin
ActionIn Make“Makes a user a super administrator.”
This module gives an account the highest level of admin rights in your domain. Having it in a scenario means the promotion follows a recorded approval instead of an informal request.
Update an Organizational Unit
ActionIn Make“Updates an existing organizational unit.”
Changes to an existing organizational unit are applied from the scenario, which keeps your domain structure in sync with the source you trust, such as an org chart kept in a sheet.
Update a Role
ActionIn Make“Updates an existing role.”
An existing custom role is adjusted without rebuilding it. It keeps role changes documented when they come from a request process.
Update a User
ActionIn Make“Updates an existing user.”
Account details stay current because the scenario writes changes as soon as the source changes, instead of waiting for someone to notice an outdated detail.
List Organizational Units
SearchIn Make“Retrieves a list of all organizational units for an account.”
All the organizational units of your account come back as a list, one bundle per unit. That gives you a clear inventory to export or to compare with your org chart.
List Privileges
SearchIn Make“Retrieves a list of all privileges for a customer.”
You get the catalog of privileges available for your customer account, the raw material custom roles are made of. It answers the question of what a role could contain before anyone designs one.
List Role Assignments
SearchIn Make“Retrieves a list of all role assignments.”
Every role assignment in the domain comes back, showing who holds which admin role. It is the starting point of any access review you want to run from a scenario.
List Roles
SearchIn Make“Retrieves a list of all roles in a domain.”
The roles defined in your domain arrive one by one, one bundle each, so the scenario can pick the right one or record them all.
List Users
SearchIn Make“Retrieves a list of users in a domain.”
The users of your domain are returned as bundles, which turns a manual export into a step of your scenario. From there you can sync a directory, a sheet or a CRM.
Need help automating Google Workspace Admin with Make?
A person reads every message.
