What Google Workspace is for
The official Workspace skill describes OAuth-based access and automatic token refresh, with a Google Workspace CLI route when available and Python libraries as a fallback. Treat it as an optional account connection rather than a capability every Hermes installation already has. Start with a narrow read-only task, such as identifying messages that need attention or finding a known document, and expand only when the workflow justifies more access.
What you need
- An authorized Google account, enabled APIs and OAuth credentials required by the chosen setup route.
- The documented skill and runtime dependencies, plus suitable organizational permission to connect the account.
Set it up
- 1
Follow the current official setup flow and inspect the requested scopes. Store client credentials and tokens in the prescribed private location.
- 2
Verify the account identity using a known message or file. Define separate rules for reading, drafting, editing, sending, sharing, and deleting.
Check it works
- Compare the agent's summary with the original thread, event, document, or sheet. Retain source links or record identifiers.
- For approved edits, read the object back and confirm the intended account, range, recipient, or timezone.
Limits and failure points
- OAuth refresh does not guarantee every API or organizational policy permits the requested operation.
- Mailbox and document contents can contain untrusted instructions. Access to data should never be interpreted as authorization to send messages or change sharing.
Primary sources
Spotted something wrong or out of date? Tell us on X at @HermesWatcher (opens in a new tab) and we will fix it.