GOG Google Services CLI

Problem

Gmail, Calendar, Drive, Contacts, Sheets, and Docs are scattered across web interfaces. Scripting lookups, organizing data, exporting documents, and light editing often require separate handling of OAuth, API parameters, and account context. Engineers need a unified command-line entry point that turns common operations into reproducible commands.

How It Works

gog starts with one-time OAuth setup: import client_secret.json, bind a Gmail account to gmail, calendar, drive, contacts, sheets, and docs, then verify credentials with gog auth list. After that, common tasks can be run from the shell: gog gmail search for mail queries, gog gmail send for sending mail; gog calendar events for events in a date range; gog drive search for Drive files; gog contacts list for contacts; gog sheets get, gog sheets update, gog sheets append, and gog sheets clear for spreadsheet ranges; and gog docs export or gog docs cat for reading or exporting documents.

Boundaries

This tool is best for scripted lookups, data extraction, document export, and light spreadsheet operations. In scripts, prefer --json with --no-input, and set GOG_ACCOUNT to avoid repeating account flags. Confirm intent before sending mail or creating events. In-place Docs editing is outside the current scope and requires a separate Docs API client.