Google Workspace Operator

What It Solves

When automating across Gmail, Calendar, Drive, Docs, Sheets, and Slides, thin integrations often require separate APIs and brittle workarounds, especially when a folder name is mistaken for a folder ID. google-workspace-operator targets personal Google account workflows with 24 Direct OAuth tools that call googleapis.com directly, without MCP, third-party gateways, or IMAP app passwords.

How It Works

The skill is organized around query-then-act loops:
- Gmail: gmail_messages_list for search, gmail_message_send for plain-text email, gmail_message_modify for labels or archiving.
- Calendar: create, list, read, and delete events using RFC3339 datetimes.
- Drive: use Drive query language to locate files and folders; listing a folder requires resolving its id by name first, then querying '' in parents.
- Docs / Sheets / Slides: create and read structured content; use docs_append_text for Docs edits and sheets_values_append for row writes.

A key behavioral constraint is state freshness: when the user asks whether something arrived or changed, the tool should be called again instead of reusing a previous result. On errors such as invalid_grant or missing files, the next step should be a corrected call or a narrowly targeted question.

Boundaries

It is suitable for personal-account automation, not Workspace Admin operations or local-file editing; docs_append_text applies to Google Docs only. Current limits include plain-text Gmail sending without attachments, no OCR or image generation, no resource booking, and no full free/busy lookup beyond events.list. drive_permission_create performs real sharing and should only be used when the user explicitly asks.