Google Workspace user accounts
Connect Google Workspace user accounts to the rest of your business: accounts, files, mail and calendars kept in step.
2 ways to read, 1 way to write, each write switched on by you.
Quality checks
Built and tested with example responses.
- Ready to connect: doneEvery listed action is built in.
- Built and tested with example responses: doneEach action is built from the provider’s published API and tested against example responses, errors, rate limits and paging.
Connected, approved, proven.
The things teams do most with Google Workspace user accounts, an example flow with a person in the loop, and what Nexra keeps as proof.
Top actions
- Create Workspace user
users.createApproval by rule - List Workspace users
users.listRead
Example flow
- BambooHR · Read employee directory
employee_directory.listDone - Google Workspace user accounts · Create Workspace user
users.createMaker-checker - Nexra · Record the decision and result in the evidence chainProven
Example workflow. Routine runs go through on their own. Only a change your rules flag, such as one over a limit you set, waits for the right person, who sees the exact change and the rule before it reaches Google Workspace user accounts.
What gets logged
- Whether it ran on its own or who approved it, and under which rule
- A fingerprint of the exact request sent to Google Workspace user accounts
- Google Workspace user accounts's reply: what it created or changed
- One entry in the evidence chain, linked to the one before
Try this in the sandbox
Run the whole flow with test data in your sandbox, then connect a Google test account before you go live.
For developers
Technical detail
List and read Google Workspace users, and create a user account for a new starter with their work identity (Admin SDK Directory API).
Google API docs- Source actions
- 2
- Destination actions
- 1
- Data type
- 1
What you can map
Reads are always available. Writes are off until you switch them on for a connection, and governed writes follow your policies.
users3
- Create Workspace userDestinationProvider duplicate protectionApproval before production
Creates a Google Workspace account for a new starter with their name, primary email, organisational unit, job title and department. The password is random, never shown, and must be changed at first sign-in.
- Get Workspace userSource
One user by primary email or user ID.
- List Workspace usersSource
Users of the Workspace account, by primary email.
Access and limits
- Authentication
- Google OAuth client and an administrator's refresh token
- Plans and access
- Google Workspace (and Cloud Identity) editions; not personal Google accounts. The authorising account must be a Workspace administrator with the User Management privilege. On Flexible plans a new user adds to the bill.
- Test environment
- Use a test Google account and an OAuth client in testing mode.
- Rate limits
- Directory API quotas per project and per user; heavy account creation can return 503 or 403 rate-limit reasons, retried with exponential backoff.
- Pagination
- pageToken and nextPageToken, up to 500 users per page.
- Provider events
- The Directory API offers users.watch push channels (create, update, delete), which expire and must be re-created; Nexra does not register them. Flows run on demand, on a schedule, or when a scheduled check finds new or changed records.
Before you build a flow
- Users cannot be filtered by when they were created or changed, so the list is not watchable for changes.
- users.create sets a random temporary password that nobody sees and asks for a change at first sign-in; the person signs in after IT resets the password or through single sign-on.
- Not implemented by design: deleting, suspending or renaming users, admin roles, group membership and licences.
Developer reference
- Create the Google credentials described above with the narrowest permissions your flows need.
- In Nexra, open Connect, then Connections, then New connection, choose Google Workspace user accounts, enter its settings and credentials, and tick only the write actions you need. Connection guide
- Test the connection, then use its actions as flow sources and destinations. Flow guide
Machine-readable detail: GET /api/public/connect/connectors/google-workspace-admin and the Connections API.