Skip to content
Integrations Google Admin SDK

Google Admin SDK + Finn.

Google Admin SDK integration with Finn. Google Admin SDK provides administrative access to Google Workspace users, groups, devices, and directory resources.

What you can do with Google Admin SDK.

Google Admin SDK provides administrative access to Google Workspace users, groups, devices, and directory resources.

Get a new employee into Google Workspace

Finn turns the accepted new-hire record into a working Workspace account and the group memberships the employee needs.

Typically handled byWorkspace administrator

Starts when

Workday records an accepted hire with a start date and role.

What Finn handles

  1. Read the employee's confirmed name, manager, location, and role from connected Workday.
  2. Create the Workspace user in the correct organizational unit and add the role's group memberships.
  3. Send the account setup instructions through the organization's verified new-hire channel and follow completion of the first sign-in.
  4. Record the account and memberships in the onboarding request and tell the manager which setup steps are complete.

The result

The employee has a Workspace account, the required groups, and a documented onboarding result.

Change Workspace access after a role move

Finn updates the directory and group access when an employee changes teams, keeping the change tied to the HR decision.

Typically handled byWorkspace administrator

Starts when

An accepted Workday role or department change takes effect.

What Finn handles

  1. Read the new role and compare it with the employee's current directory details and group memberships.
  2. Identify the role's additions and removals and obtain approval for access that requires a resource owner's decision.
  3. Update the organizational unit, profile fields, and accepted group memberships.
  4. Confirm the resulting directory state and notify the employee and manager through the connected communication channel.

The result

Workspace reflects the employee's current role and the request records the completed access changes.

Complete Workspace departure access removal

Finn carries out the scheduled Workspace access changes and records the separate work required to preserve business information.

Typically handled byIT offboarding coordinator

Starts when

HR confirms an employee's departure and effective access-removal time.

What Finn handles

  1. Read the departure decision and any retention or business-owner instructions from the offboarding record.
  2. At the accepted time, suspend the Workspace account and sign the user out of Google sessions.
  3. Remove the designated group memberships and revoke the specified third-party application grants where the departure policy requires it.
  4. Record each result and coordinate document ownership through connected Google Drive under the retention decision.

The result

The departure record shows completed Workspace access removal and the status of business-document handling.

Resolve a verified Workspace sign-in problem

Finn investigates the account problem and completes the recovery steps allowed by the organization's identity-verification process.

Typically handled byWorkspace service desk technician

Starts when

An employee reports that they cannot sign in to Workspace.

What Finn handles

  1. Complete the organization's verification flow before inspecting or changing the employee's account.
  2. Read the account status and sign-in evidence to distinguish a password problem from suspension or an identity-provider issue.
  3. Perform the accepted password recovery or authorized account correction, keeping two-step verification requirements in place.
  4. Guide the employee through sign-in and close the service request with the recovery result, excluding recovery secrets.

The result

The verified employee's sign-in problem has a documented resolution or a precise unresolved owner.

Fulfill a Google group access request

Finn collects the resource owner's decision, updates the group membership, and confirms the request is complete.

Typically handled byWorkspace access coordinator

Starts when

An employee requests membership in a team or resource access group.

What Finn handles

  1. Read the requested group, the employee's identity, and the business purpose from the access request.
  2. Get the group owner's decision on membership and role when the request needs approval.
  3. Add or update the accepted membership through Directory and check the resulting group record.
  4. Tell the employee how to use the resource and finish the service request with the owner decision and membership result.

The result

The accepted membership is in place and the access request contains its decision and completion evidence.

Correct employee directory information

Finn resolves a directory correction using the trusted employee record and carries the update through the affected Workspace fields.

Typically handled byPeople operations administrator

Starts when

An employee or HR reports an incorrect name, manager, department, or contact detail.

What Finn handles

  1. Compare the reported discrepancy with connected Workday and identify which system owns the field.
  2. Obtain the HR correction where the source record is wrong, then update the corresponding Workspace profile fields.
  3. Check the user record and explain any separate email-address change that needs an administrator's decision.
  4. Send the employee the completed correction and update the originating request.

The result

The Workspace profile matches the accepted employee record and the correction is documented.

Contain a confirmed Workspace account incident

Finn gathers the account evidence and executes the security team's selected containment steps through the administrative APIs.

Typically handled bySecurity operations analyst

Starts when

The security team confirms suspicious activity involving a Workspace account.

What Finn handles

  1. Collect the Reports audit events, account state, and third-party application grants for the incident.
  2. Record the security owner's containment decision, including whether the account must be suspended.
  3. Sign the user out, revoke the specified application grants, and apply the accepted account restriction.
  4. Attach the action results to connected ServiceNow and coordinate recovery through the organization's verification flow.

The result

The security incident contains the evidence, completed containment actions, and the named recovery decision.

Keep meeting-room records accurate

Finn updates the directory's room information so employees can find and choose resources that match the workplace.

Typically handled byWorkplace systems coordinator

Starts when

Facilities accepts a change to a room's name, location, capacity, or equipment.

What Finn handles

  1. Read the accepted facilities change and the existing building and calendar-resource records.
  2. Update the resource description, capacity, location, or equipment fields through the Directory API.
  3. Check the resulting resource record and identify any bookings that need attention through connected Google Calendar.
  4. Notify the facilities owner and finish the request with the updated resource and any separate booking changes.

The result

The room directory reflects the accepted workplace change and the facilities request records the result.

Set up the connection around your work.

Contact Finn to discuss the records your workflow needs and the actions you want it to perform.

Your team chooses what Finn can access, what agents can change, and when a person must approve the work. The connection needs the appropriate account access and permissions from Google Admin SDK.

Put your Google Admin SDK integration to work.

Tell us which records, actions, and teams the connection needs to support.