Google Workspace API Access Setup

$2.99Official

Use when a task needs domain-wide Google Workspace API access (Directory, Reports, Gmail, Drive) and credentials are missing or returning unauthorized_client.

cloudgoogle-workspaceoauthservice-accountdomain-wide-delegationadmin-sdkgcpidentity· by SkillingMain

What you get

✓12-step procedure
✓Runnable Python / Shell / JSON included
✓8-point quality checklist
✓9 pitfalls to avoid
✓Installs into 6 tools

Version: v1 →
Last updated: today
Length: 9 min read
Requires: Best with a strong model (claude-opus-4-6)

Works in: Claude Code, Codex, Cline, opencode, OpenClaw, Hermes · Built for large codebases

What you'll need to set up

Fiddly setup — follow closely · 25-40 min

Create a Google Cloud project with a service account, enable the Workspace APIs you need, then have a Workspace super administrator authorize that service account's numeric OAuth client ID against an explicit scope list in the Admin console.

GOOGLE_CLOUD_PROJECTGWS_SERVICE_ACCOUNT_EMAILGWS_SERVICE_ACCOUNT_CLIENT_IDGWS_DELEGATED_SUBJECTGWS_CUSTOMER_IDGOOGLE_APPLICATION_CREDENTIALS

Full setup guide · 19 API calls →

Preview

When to use

Invoke this skill when a task needs programmatic, domain-wide access to Google Workspace data — Directory (users, groups, org units, roles), Reports/audit logs, Gmail, Drive, or Calendar — acting for many users in a tenant rather than one interactive user, and either the credentials do not exist yet or an existing service account is failing authorization.

Trigger on: "audit every user in our Workspace", "pull login audit logs", "list all shared drives", "read a departed employee's mailbox", "set up a Workspace integration", or any 403 Not Authorized to access this resource/api against admin.googleapis.com.

Do NOT use this skill for:

Consumer accounts (@gmail.com).

…

🔒 Buy once ($2.99) to unlock the full playbook, download it, and install it in every tool you use.