Hugh Google API Access (hugh-ai@ubiworks.ca)

State

ACTIVE — Hugh has full Google API access for hugh-ai@ubiworks.ca via OAuth refresh token (as of 2026-04-23). No re-auth needed unless token is revoked.

Scopes

• Gmail (read + send)
• Google Drive
• Google Docs
• Google Calendar (read)
• Contacts (read)

How It Was Set Up

Liam Wilkinson completed a two-attempt OAuth flow on 2026-04-23 via agent-hugh Slack channel. Hugh ran a local OAuth server on port 8765. First code expired; second code (submitted ~08:10 PDT) was captured successfully. Tokens saved to Hugh’s credential store. [Source: Slack session, 2026-04-23]

Access Account

• Email: hugh-ai@ubiworks.ca
• Type: Google Workspace (UBI Works domain)

Back-links

• liam-wilkinson — completed the OAuth flow
• floyd-marinescu — authorized the setup

Known Issues

• 2026-04-28 | Multiple heartbeat sessions reported invalid_client error when trying to exchange refresh token. This may indicate the client secret in google-oauth-client.json was rotated or revoked. When using the correct client_id/secret from google-oauth-hugh-ai.json directly, the token exchange succeeds. [Source: Sessions 47accf13, 30b5c817, 2026-04-28]
• Root cause suspicion: Some sessions used wrong credentials file (/Users/OpenClaw/.openclaw/credentials/google-oauth-client.json instead of the Hugh-specific one). Working path: /Users/OpenClaw/.openclaw/workspaces/hugh/.secrets/google-oauth-hugh-ai.json

Timeline

• 2026-04-23 | OAuth completed by Liam. Hugh confirmed access to Gmail, Drive, Docs, Calendar. [Source: Slack session dcebed40, 2026-04-23]
• 2026-04-28 | Token exchange worked in session 6cfe0afc (using correct credentials file). Multiple other sessions failed with invalid_client when using wrong credentials. [Source: Sessions 6cfe0afc, 47accf13, 2026-04-28]