Gog Google Workspace CLI

Problem

When automating Gmail, Calendar, Drive, Sheets, and Docs, scripts often have to handle OAuth tokens, API endpoints, and parameter shapes separately. Manually copying message bodies, spreadsheet ranges, or event details is error-prone and hard to wire into workflows.

How It Works

• Auth: complete a one-time OAuth setup, then access Google Workspace by account and service.
• Lookup: gmail search can retrieve mail with filters such as newer_than:7d; calendar events lists schedules; drive search finds files; contacts list reads contacts.
• Read/write: sheets get, sheets update, sheets append, sheets clear, and sheets metadata work with spreadsheet ranges; docs export and docs cat read document content.

For scripting, prefer --json and --no-input, and use GOG_ACCOUNT to avoid repeating the account. For Sheets writes, pass structured values with --values-json rather than concatenating inline text.

Boundaries

It is well suited for lookup, export, and lightweight updates, not complex in-place Docs editing; document editing requires a separate Docs API client. Add confirmation logic in the business layer before sending mail or creating events.