Google Workspace CLI: Control Gmail, Docs, and Sheets From Claude Code

Gmail

Read messages, send with formatting, apply labels, move to trash, search threads, set up auto-responders. Filter by sender, subject, or date range. Triage thousands of emails without token waste.

Google Docs

Create new documents with real formatting (headings, bold, italics, tables). Insert content without fighting markdown. Update existing docs. No more raw HTML or weird encoding issues.

Google Sheets

Read ranges, write data, append rows, create sheets, execute queries. Works with structured data. Perfect for reports and data pipelines.

Google Slides

Build presentation decks programmatically. Add slides, insert text, format layouts. Automate status reports and stakeholder updates.

Google Calendar

Find free time slots, schedule meetings, check availability. Coordinate across calendars without manual back-and-forth.

Google Drive

Search files, upload documents, share with teams, organize folders. Manage your entire workspace programmatically.

Step 1: Create a Google Cloud Project

1. Go to console.cloud.google.com
2. Click "Create Project" in the top navigation
3. Name it something memorable (e.g., "Claude Workspace")
4. Click Create and wait 1-2 minutes for provisioning

Step 2: Enable Required APIs

1. In the Cloud Console, go to "APIs & Services" > "Library"
2. Search for and enable: Gmail API, Google Docs API, Google Sheets API, Google Slides API, Google Calendar API, Google Drive API
3. For each, click the result, then click the blue "Enable" button
4. Wait for all six to show "Status: Enabled"

Step 3: Create a Service Account

1. Go to "APIs & Services" > "Credentials"
2. Click "Create Credentials" > "Service Account"
3. Fill in the account name (e.g., "claude-workspace-bot")
4. Click Create and Continue
5. Skip optional steps and click Done

Step 4: Generate and Store Credentials

1. Click the service account you just created
2. Go to the "Keys" tab and click "Add Key" > "Create new key"
3. Choose JSON format and click Create
4. Save the downloaded file securely (it contains your credentials)
5. Set the environment variable: export GOOGLE_APPLICATION_CREDENTIALS="/path/to/key.json"

Step 5: Install the Workspace CLI

1. In your Claude Code environment, run: pip install google-workspace-cli
2. Verify installation: gworkspace --version
3. You should see a version number like v0.8.2

Step 6: Test Your Setup

Run your first command to verify everything works:

gworkspace mail list --max-results 5

You should see your 5 most recent emails. If you do, you're ready to start building automations.

⚠️ Important Caveats

This is pre-v1.0 software. Google has released it, but it is not officially supported. Expect rough edges. APIs may change. Documentation may lag reality.

Do not use with SOC 2, HIPAA, or other regulated data. This is still experimental. If you're handling healthcare records, financial data, or other sensitive information that requires compliance certification, wait for official v1.0 release and audit results.

Service account limitations. The CLI uses a service account, not your personal account. This means you cannot access shared drives or documents shared with you personally — only documents you have direct ownership of or that are shared with the service account's email.

Rate limits apply. Google still enforces rate limits on API calls. High-volume operations (triage 10,000 emails, write 1,000 sheets rows) can hit limits. Build in backoff logic or split large operations.

Cost considerations. Using the service account requires a Google Cloud project, which has a free tier but will incur costs at scale. Monitor your API usage in the Cloud Console.

Credential security. Your Google Application Credentials JSON file is sensitive. Never commit it to version control. Use environment variables and restrict file permissions to your user only.

Can I use this with my personal Google account?

You need a Google Cloud Project and a service account, which requires a Google Workspace account or a personal Google account with billing enabled. You can set this up for free within the GCP free tier limits.

Will this work with Claude's web interface or only Claude Code?

This requires Claude Code, since it needs to run bash commands. The web interface doesn't have local bash execution, so it can't use the CLI directly.

How does this compare to Zapier or Make?

Zapier and Make are for non-technical users and simple workflows. This CLI is for developers and power users who want programmatic control directly from Claude. You can build much more complex logic with less money spent on third-party subscriptions.

What if Google's Workspace API changes?

The CLI abstracts the underlying API, so minor API changes won't affect your scripts. However, since this is pre-v1.0, larger breaking changes are possible. Pin the version in your requirements file and test before updating.

Can I schedule automation to run on a timer?

The CLI itself doesn't have scheduling. But Claude Code environments can run cron jobs or use task schedulers. You can also deploy these workflows as cloud functions (Google Cloud, AWS Lambda) that trigger on schedules.

Is there documentation for the 100 workflow recipes?

Yes, they ship with the CLI in the recipes/ directory. Run gworkspace recipes list to see them all, and gworkspace recipes show email-triage to view a specific one.

What's the difference between pre-v1.0 and the final version?

Pre-v1.0 is a public beta. The final version will have official support, stability guarantees, compliance certifications (SOC 2, HIPAA), and a public SLA. For production use with sensitive data, wait for v1.0.

Can I contribute new workflows or features?

Yes, the project is open source. Check the GitHub repository for contribution guidelines. User-contributed recipes are encouraged, especially for domain-specific use cases.

Ready to get started?

Follow the 6-step setup walkthrough above and run your first command in 10 minutes.