Connectors / Google Workspace
What Deixic does with Google Workspace.
Read and act
Help suspend departing employees’ accounts and revoke their access tokens.
How Deixic helps with Google Workspace.
- Read information
- Review calendar, directory and drive from Google Workspace as evidence and to check state.
- Choose the actions
- Deixic supports actions on calendar, directory and drive. Grant only the tools and permissions the task needs.
- Keep your decisions
- Deixic checks your policy before a change; sensitive changes wait for a named approver. The action record keeps the decision and result.
6 of 7 changing operations require approval. See how approvals work.
Example workflow
Suspend a terminated user and prove the account is closed
A person has left. Look up their Google Workspace account, prepare the suspension for the named approver, and after approval confirm the account shows as suspended. Report which accounts lack 2-step verification so the admin can enforce it.
- Take the offboarding trigger from the HR system, then look up the account with the directory user lookup. Match on the exact primary email or user ID, not a display name.
- Prepare the suspension. Suspending a user changes access to Gmail, Drive, and Calendar, so it waits for a named approver who records a reason. Low-risk reads run without approval; the suspension does not.
- After the approver releases it, run the suspension and read the user back with the same lookup. The receipt records the account, the approver, the reason, and the suspended status returned by the read-back (SOC 2 CC6.2).
- For CC6.1, read the directory user records and list the accounts whose 2-step verification enrollment is off. Turning on enforcement is an Admin console setting that this connection does not expose, so the list goes to a Workspace admin as a decision.
Check before you continue: Suspension is not deletion. Data, shared files, and mail delegation stay until an admin transfers or removes them, and an account that is suspended and later restored regains access. Check the read-back status rather than the success message of the write.
Provider reference: Directory API users resourceManage users and suspension
Use your existing agent with Deixic. Calls you route through Deixic follow your access and approval policy.
Provider access
Supported Google Workspace reads and actions.
Choose the reads and actions your task needs. Your connection’s permissions and your agent’s access determine what it can use.
Read data
- Calendar Read
- Directory Read
- Drive Read
- Email Read
- Sheets Read
- Directory Security Read
- Cloud Identity Policies Read
- Directory Domain Read
- Reports Audit Read
Actions
- Calendar Write
- Directory Write
- Drive Write
- Documents Write
- Email Write
- Directory Security Write
Permissions
Choose the access for Google Workspace.
Have the account owner authorize the intended account and permissions, and if data is missing, inspect the authorizing user’s access to the target resource before requesting broader access.
Find Google Workspace in the appManage connected accounts
- Connection
- OAuth
- Supported operations
- Read and act
- Reads
- 9
- Actions
- 6
- Provider permissions
- Grant only the permissions needed for the task.
What you need to connect
- Client ID
- Client secret
- Access token
- Refresh token
Deixic checks calls routed through its gateway and requests approval when your policy requires it.
Reference and troubleshooting
Google Workspace operation reference, troubleshooting, and questionsSOC 2 for Google Workspace
Connectors for related work
Tell us what you need from Google Workspace.
Bring one task. We’ll show you the access it needs and how Deixic helps.
Request early access