Google Workspace through Squiid

What Google Workspace is

Google Workspace exposes APIs for Gmail, Calendar, Drive, Docs, Sheets and Admin. Together they cover reading and sending mail, finding free time and creating events with conference links, listing and downloading files, editing documents programmatically, and treating a spreadsheet as a small database that humans can also edit. Domain-wide delegation exists for tenant-level access, and it is exactly the setting that should not be configured casually.

In AI-coded products these are the integrations that make an assistant feel connected to real work: drafting replies in a shared inbox, scheduling from a conversation, generating a report into a Doc, exporting data to a Sheet the finance team already uses, or pulling a folder of PDFs into a retrieval pipeline. They also involve the most sensitive scopes in this catalog, because mail and file access is effectively access to everything a person has. Drive and Gmail both paginate heavily, so a sync job is written as a resumable background task rather than a single request.

Why connect it through Squiid

Google Workspace is on the Squiid roadmap as a connect service. When it lands, you will link your account through the standard OAuth consent flow with the specific scopes you approve, and Squiid will hold the refresh token and issue scoped access through https://api.squiid.io/v1/google-workspace/... with Authorization: Bearer $SQUIID_API_KEY, with client libraries working by base URL swap (gateway convention). Your Workspace subscription stays billed by Google at the provider's listed price, and the connection can be revoked from the Squiid dashboard. Incremental sync tokens let a job pick up only what changed, which keeps a mailbox or drive integration affordable.

• One account, one key, one bill, one dashboard. Google Workspace sits beside every other service your project uses, on the same invoice and the same credit balance.
• Key custody. Squiid holds the Google Workspace credentials. Your code carries SQUIID_API_KEY, so GOOGLE_CLIENT_ID, GOOGLE_CLIENT_SECRET, GOOGLE_REFRESH_TOKEN, GOOGLE_SERVICE_ACCOUNT_JSON never land in a repository, a preview deployment or an agent’s context.
• Metering you can see. Every call is counted per service and per day, so you know what Google Workspace costs before the month ends.
• Pause on zero. When prepaid credits run out the gateway stops authorizing usage instead of running up a bill you did not fund.
• One rotation. Rotating the Squiid key cuts off every agent, worker and deployment at once, with no provider key to hunt down.

What you get

• Your existing Workspace account connected, not replaced
• Gmail, Calendar, Drive, Docs and Sheets access
• Scopes you approve rather than a service account file
• Refresh tokens held by Squiid
• Workspace seats stay billed by Google

How to connect Google Workspace

One variable replaces the provider credentials this service would normally need. Requests go to the gateway and the official SDKs work by pointing their base URL at it (gateway convention).

# .env
# replaces GOOGLE_CLIENT_ID, GOOGLE_CLIENT_SECRET, GOOGLE_REFRESH_TOKEN, GOOGLE_SERVICE_ACCOUNT_JSON
SQUIID_API_KEY=sq_live_xxxxxxxxxxxxxxxxxxxxxxxx

# every request: https://api.squiid.io/v1/google-workspace/...
# header:       Authorization: Bearer $SQUIID_API_KEY

Pricing through Squiid

Google bills your Workspace subscription directly at the provider's listed price, with no Squiid margin. Squiid passes that through at par: one dollar of prepaid credit is one dollar of Google Workspace usage, with no markup and no per-request margin.

Google Workspace has no subscription attached on Squiid today. If a plan is required for a feature you need, it passes through at the provider’s listed price with no Squiid fee.

Squiid adds no markup to provider prices. There is a free plan at $0 a month with a 15% fee when you top up credits, Solo at $19.97 a month with a top-up fee that starts at 8% and falls to 3.5% as your spend grows, Team from $29.97 a seat a month with the same ladder one point lower, and Custom with a rate of 3% or less. Credits are prepaid, so Google Workspace usage stops when the balance reaches zero rather than producing an invoice you did not fund. Auto top-up with a cap keeps production running without handing anyone an open-ended card.

If you leave

Your own account: the Google Workspace account was always yours and Squiid only holds an authorised connection, so revoking it leaves nothing behind. Squiid never owns your code, your schema or your domain, and the gateway speaks Google Workspace's own API, so the client change is a base URL. The handover page lists what happens for every provider in the catalogue.

Works with every coding agent

Google Workspace through Squiid is just an HTTP call with a bearer token, so every agentic coding tool can use it with the single key already in your environment:

• Claude Code
• Cursor
• ChatGPT
• Codex
• Grok
• Gemini CLI
• GitHub Copilot
• Windsurf
• Perplexity
• Devin
• Replit
• v0
• Lovable
• Cline

Vibe coding a feature on Google Workspace usually means asking for it in plain language and letting the agent write the integration. Because the key is Squiid’s rather than the provider’s, it can do that without ever holding a credential that could be leaked, logged or committed.