google-workspace

You can automate Google Workspace tasks by using a Hermes-friendly CLI wrapper that centralizes control over Gmail, Calendar, Drive, Docs, and Sheets. It exposes Google Workspace APIs through the gws command or a bundled Python client fallback.

Setting up OAuth2 for Google Workspace requires a client secret stored at ~/.hermes/google_client_secret.json. After running the setup process to authorize access, an OAuth2 token is generated and stored locally at ~/.hermes/google_token.json for seamless re-authentication.

Yes, you can manage Google Drive and Docs files through Telegram, Discord, or any channel Hermes supports. The skill operates across these channels, allowing you to upload files, read messages, and manage Docs content using gws commands.

No, the Google Workspace automation skill does not strictly require the gws backend. It uses gws when installed for unified control, but automatically falls back to a bundled Python client to ensure broad API coverage for Gmail, Calendar, and Drive operations.

The best way to read Gmail messages and list Calendar events programmatically is by issuing gws commands within Hermes. This approach wraps Google Workspace APIs to handle reading emails, listing events, and retrieving contacts directly.

Using the Python client fallback instead of gws for Google Workspace provides broad coverage but may lack the unified control optimizations of the native gws backend. Both methods require valid local OAuth2 tokens and depend on the google-api-python-client library.