Open troubleshooting index CMD K

Gmail, Calendar, Drive, Docs, Sheets

Hermes Agent Google Workspace workflows

Google Workspace workflows can be high-value for Hermes Agent, but they need narrow OAuth scopes, draft-first outputs, and careful review. Fold Gmail, Calendar, Drive, Docs, Sheets, and Google Meet notes into one business-workflow cluster until there is enough tested depth to split them.

Install path Security model

Agent Guide is an independent editorial resource. It is not affiliated with, endorsed by, or sponsored by Nous Research, Hermes Agent, or Hermes/Hermes brand owners. Product names and marks belong to their respective owners.

Intent hermes-agent-google-workspace

Sources 4

Schema 2

Links 4

Direct answer

Use Hermes Agent with Google Workspace for draft-first workflows: calendar prep, inbox summaries, research notes, document drafts, spreadsheet summaries, and meeting-note organization. Avoid unsupervised send, delete, share, or customer-facing actions.

Google Meet notes belong here for now because the searcher job is the same: turn workspace signals into reviewed notes, summaries, and follow-up drafts.

Best for

Calendar preparation and client-call research drafts.
Gmail summaries that a human reviews before reply.
Drive/Docs organization with explicit folder boundaries.
Sheets summaries or reports where source data is understood.

Avoid if

You cannot limit OAuth scopes or workspace folders.
The workflow can send emails, share files, or invite people without review.
You handle regulated, legal, medical, or confidential client data without policy approval.
You want Google Meet notes to become unsupervised decision records.

What this page covers

Gmail, Calendar, Drive, Docs, Sheets, and Google Meet notes as one canonical Workspace workflow intent.
OAuth, review, folder scope, and customer-facing caution.

What this page does not cover

Step-by-step Google Cloud project screenshots.
Separate Google Meet page or per-app page split.
Compliance or legal approval for Workspace automation.

Quick steps

Read the Google Workspace skill docs and decide the smallest useful scope.
Start with read-only or draft-only tasks.
Use a test folder/calendar/mailbox label before broad account access.
Write outputs to drafts or private documents for human review.
Add scheduled workflows only after manual outputs are stable.

Known breakpoints

Breakpoint	Why it happens	Safer response
Too much account access	OAuth scope chosen too broadly	Use the narrowest scope and test account/folder first.
Email sends prematurely	Workflow allowed external action without approval	Use draft-only outputs and manual send.
Meeting notes overclaim accuracy	Transcript or summary quality not reviewed	Mark notes as drafts and keep source transcript when available.
Shared Drive leak	Agent can access broader folders than intended	Limit folder access and use dedicated workspaces.

Security notes

OAuth scopes, shared folders, and email send permissions are the security boundary.
Do not allow unsupervised legal, HR, finance, or customer email actions.
Store meeting notes and summaries where the intended audience is explicit.
Use test accounts or labels before exposing a primary mailbox.

Changelog

2026-06-02: Added as canonical Google Workspace workflow page.

Agent Guide judgment

Google Workspace is valuable only when scopes and outputs are narrow. Gmail, Calendar, Drive, Docs, Sheets, and meeting notes all become risky when the agent can read broadly or send externally.

The safe first pattern is read-only or draft-first: summarize, prepare, organize, and draft. Human approval should stay between Hermes and any real recipient, shared file, invite, or customer-facing document.

Workspace smoke test

Area	Pass condition	Stop if
Scope	Access is limited to a test label, folder, calendar, or account.	Primary mailbox or full Drive is exposed on day one.
Output	Generated content lands as a private draft.	Hermes can send, share, or invite without review.
Meeting notes	Notes are marked as drafts with source context.	Summaries are treated as official records without review.
Schedule	Manual workflow passes before recurring runs.	Automation starts before scope and output are verified.

Workspace command risk map

Surface	Low-risk first use	Do not start with
Gmail	Search unread messages or draft a private summary.	Send/reply commands to real recipients.
Calendar	List upcoming events with timezone-aware output.	Create/delete events for other people.
Drive	Search inside a test folder.	Broad Drive search across client or company data.
Sheets	Read a known range.	Append/update production rows before review.
Docs	Read a test document or draft notes.	Overwrite shared documents or publish unreviewed summaries.
Contacts	List a small test set.	Use contacts for outreach automation.

OAuth failure packet

NOT_AUTHENTICATED: rerun setup instead of retrying commands blindly.
REFRESH_FAILED: token may be revoked; re-authorize before scheduling.
HttpError 403: Insufficient Permission: scope is missing; do not broaden scopes without recording why.
Access Not Configured: enable the relevant API in Google Cloud before blaming Hermes.
ModuleNotFoundError: install dependencies through the documented setup path.

Google Workspace setup triage

Official Google Workspace skill docs list the setup path and troubleshooting codes. Recent community setup threads add a practical operator lesson: token paths, gws availability, python/python3 invocation, shared calendars, and OAuth reauthorization can all fail in ways that look like an agent reasoning problem.

Do not diagnose these from the chat transcript alone. Build a small setup packet before changing scopes or models.

Symptom	Likely class	First operator response
`NOT_AUTHENTICATED`	OAuth setup missing or token unavailable.	Run the documented setup again and confirm where the token is written.
`REFRESH_FAILED`	Token revoked or refresh path broken.	Reauthorize before widening scopes.
`HttpError 403: Insufficient Permission`	Missing scope for the requested service.	Add only the smallest required service scope and reauthorize.
`HttpError 403: Access Not Configured`	Google API not enabled in the Cloud project.	Enable the specific API instead of recreating the whole account.
`ModuleNotFoundError` or `python` missing	Local dependency or interpreter mismatch.	Run setup dependencies and confirm whether the environment calls `python` or `python3`.
Gmail works but shared calendars do not	Account, calendar, or scope boundary issue.	Test primary calendar first, then document shared-calendar access separately.

Official sources reviewed

Source	Used for	Last checked	Confidence
Hermes Agent Google Workspace skill docs	Gmail, Calendar, Drive, Docs, Sheets, and OAuth workflow context.	2026-06-05	high
Hermes Agent security guide	Approval modes, gateway authorization, Docker terminal backend hardening, and credential cautions.	2026-06-05	high
Hermes Agent messaging docs	Gateway-supported messaging surfaces, 20+ platform context, setup boundaries, and chat-platform workflow risk.	2026-06-05	high
Reddit Hermes Agent Google Workspace setup issue	Community friction signal around Google Workspace OAuth, token paths, python invocation, and shared-calendar setup; not used as product truth.	2026-06-05	low

Known caveats: Workspace and OAuth behavior can change. Agent Guide did not run a Google Workspace setup in this batch.

FAQ

Should Google Meet notes have a separate page?

Not yet. Meeting notes are folded into Google Workspace because the same OAuth, review, and document-boundary risks apply.

Can Hermes Agent send Gmail replies automatically?

A workflow may be able to draft or send, but Agent Guide recommends draft-first review for anything involving real recipients.

Operator checklist

Get the Agent Guide launch checklist

Receive the smoke-test order for install path, sandbox boundary, provider setup, source review, and production checks.