
Gog
Google Workspace CLI for Gmail, Calendar, Drive, Contacts, Sheets, and Docs
Gog is a community skill providing a Google Workspace CLI, covering Gmail management, Google Calendar operations, Google Drive file handling, Contacts management, Sheets editing, and Docs interaction for terminal-based Google Workspace productivity.
What Is This?
Overview
Gog provides a command-line interface for interacting with Google Workspace services directly from the terminal. It covers Gmail management that sends, reads, searches, and organizes emails with label and filter operations, Google Calendar operations that create, list, update, and delete events across multiple calendars, Google Drive file handling that uploads, downloads, shares, and organizes files and folders in Drive storage, Contacts management that searches, creates, and updates Google Contacts entries, Google Sheets editing that reads and writes cell data, creates spreadsheets, and manages sheet formatting, and Google Docs interaction that creates and edits documents programmatically. The skill helps developers and power users manage Google Workspace efficiently from the command line without switching to browser interfaces, making it particularly valuable for those who spend most of their working day in a terminal environment.
Who Should Use This
This skill serves developers who prefer terminal workflows over browser interfaces, automation engineers building Google Workspace integrations, and AI agents that need programmatic access to Google services. System administrators managing multiple Google Workspace accounts will also find it useful for scripting repetitive tasks.
Why Use It?
Problems It Solves
Switching between terminal and browser to manage emails and calendar events breaks developer workflow concentration. Automating Google Workspace tasks through the raw Google API requires complex OAuth setup and verbose HTTP request code. Batch operations on Gmail labels, Drive files, or Calendar events are tedious when done manually through web interfaces. AI agents cannot interact with Google Workspace services without a structured command-line interface layer.
Core Highlights
Gmail controller sends, reads, searches, and organizes emails with full label support. Calendar manager creates, lists, and modifies events across multiple calendars. Drive handler uploads, downloads, shares, and organizes files and folders. Sheets editor reads and writes cell data with formatting support.
How to Use It?
Basic Usage
gog gmail list --limit 10
gog gmail read <message-id>
gog gmail send \
--to user@example.com \
--subject "Report" \
--body "Attached."
gog calendar list \
--from today \
--to "next week"
gog calendar create \
--title "Team Sync" \
--date 2025-03-15 \
--time 10:00
gog drive list
gog drive upload report.pdf
gog drive download <file-id>Real-World Examples
gog gmail search \
"from:client@co.com \
after:2025/01/01" \
--format json \
> client_emails.json
gog calendar list \
--calendar work \
--from "this monday" \
--to "this friday" \
--format table
gog contacts search \
"John Smith"
gog sheets read \
<spreadsheet-id> \
--range "A1:D10"Advanced Tips
Use JSON output format to pipe results into other tools and scripts for automated workflows. Combine Gmail search with Drive upload to automatically archive important email attachments. Schedule calendar events programmatically by reading data from spreadsheets to automate recurring meeting setups. When building automation pipelines, store frequently used spreadsheet and calendar IDs in environment variables to keep scripts clean and maintainable across different environments.
When to Use It?
Use Cases
Manage Gmail, Calendar, and Drive from the terminal without opening a browser. Build automation scripts that create calendar events from spreadsheet data sources, such as generating weekly team meetings from a project schedule. Enable AI agents to send emails, check schedules, and access files through structured command-line operations.
Related Topics
Google Workspace API, Gmail automation, Google Calendar, Google Drive CLI, productivity tools, and office automation.
Important Notes
Requirements
Google Workspace account with API access enabled for the services you plan to use. OAuth credentials configured for authenticating CLI commands against Google services. The gog CLI tool installed and available in your system PATH.
Usage Recommendations
Do: use JSON output format for scripting and automation to get structured parseable results. Configure OAuth credentials once and store them securely for reuse across sessions. Test commands with read-only operations before running write operations that modify your Workspace data.
Don't: share OAuth tokens or credentials in scripts committed to version control repositories. Run bulk delete operations without first verifying the target items with a list command. Assume all Google Workspace features are available since some require specific account subscription tiers.
Limitations
Google API rate limits apply and may throttle operations when processing large volumes of data or many concurrent requests. Some advanced Gmail and Calendar features available in the web interface may not have CLI equivalents. OAuth token refresh may require manual re-authentication periodically depending on token lifetime configuration. Monitoring your API quota usage through the Google Cloud Console is recommended when running high-frequency automated scripts.
More Skills You Might Like
Explore similar skills to enhance your workflow
Epic Games Automation
Automate Epic Games operations through Composio's Epic Games toolkit
Accelerate
Accelerate development cycles through automated performance optimization and seamless tool integration
Torch Geometric
Integrate and automate Torch Geometric for deep learning on irregular structures like graphs and point clouds in PyTorch
Phoenix
Automate and integrate scalable web application workflows using Phoenix framework
Playwright Cli
Automate and integrate Playwright CLI browser testing and scripting workflows
Asana Automation
Automate Asana tasks via Rube MCP (Composio): tasks, projects, sections, teams, workspaces. Always search tools first for current schemas