Google Workspace

Your bot can work across six Google services — Gmail, Calendar, Drive, Search Console, Analytics, and Ads. Each one is driven by your bot on your behalf, and they all share the same connect-and-delegate setup and the same reconnect flow. This page is a quick reference for what your bot can do with each, and whether that access is read-only or read+write.

How you connect (shared across all six)

You connect each Google service once, then hand it to specific bots:

1. You (the bot's master) open the dashboard → Settings → Google, click Connect, and complete Google's sign-in.
2. You then delegate that connection to the specific bot that should use it.
3. The bot confirms by checking which connections it can see for that service.

Your Google tokens never live in GATE — they stay with GATE's integration provider. GATE only keeps a record of the connection. See Credentials and delegation for the full picture, and Connect your accounts for the walkthrough.

Reconnecting: if a connection is disconnected, was never delegated, or its token expired or was revoked by Google, your bot will tell you it can't act on your behalf. Either way the fix is the same: your bot DMs you a reconnect link, and that one link reconnects all of your Google services, not just Gmail.

Gmail

Full mailbox automation. Your bot can search and read messages, download attachments, send mail, manage drafts (create, send, delete), apply or remove labels, and archive messages. Read + write.

If your bot has more than one Gmail account delegated to it, anything that acts as an account — send, draft, send-draft, delete-draft — must specify which account with --account <email>. Reads quietly fall back to the newest account, but a send or draft in the wrong account lands in the wrong mailbox, so the account flag is required for those.

Calendar

Your bot can list events on a delegated calendar and create, update, and delete events (title, start/end times, description, location, timezone). Read + write.

Drive

Full file management. Read + write. Your bot can:

• Find and read — list a folder's contents, search the whole drive by name or content, and fetch file metadata.
• Download — save a file's bytes to disk. Google-native types (Docs, Sheets, Slides, Drawings) have no raw bytes, so they export to a real file instead — Docs and Slides to PDF, Sheets to xlsx, Drawings to PNG — with an override available for a different format.
• Upload — put a local file into Drive (root or a specific folder), up to 5 MB per file.
• Organize — create folders and move files between folders (a real move, not a copy).
• Remove — send a file to the trash (reversible), or permanently delete it. Permanent deletion refuses to run without an explicit confirmation flag, so trash is the default.

Like the other Google services, your bot can list the connections delegated to it — that's the first health-check step when Drive misbehaves.

Search Console

SEO and search-performance tooling.

Your bot can list your verified sites, run Search Analytics queries (by date range, dimensions like query and page, search type, and more), list and inspect sitemaps, and inspect individual URLs.

It can also submit a sitemap. Read + write (everything is read except sitemap submission).

When you point the bot at a site, give it the exact identifier your bot's site list returns — a URL-prefix property keeps its trailing slash, and a domain property uses the sc-domain: prefix.

Analytics

Your bot can list your GA accounts and properties, read audience configurations, and run reports (runReport) over metrics and dimensions for a date range. Read-only / reporting — the available commands list and report data; no GA write operations are exposed.

Ads

Your bot can read a delegated Google Ads customer's campaigns (spend and performance), ad groups, ads, keywords, budgets, and user lists — and now manage them too: pause or enable campaigns, ad groups, ads, and keywords; create new campaigns, ad groups, and ads; change budgets; add keywords; and upload offline click conversions. Read + write. Customer IDs can be passed with or without dashes.

Anything that touches money — a budget change, or creating a new campaign or ad group — is always previewed as a dry run first, and your bot only applies it once you explicitly confirm in chat. Other changes can be previewed the same way on request.

Going deeper

See the Integrations matrix for a full read/write breakdown across every integration, or Connect your accounts to get set up. For the non-Google services — Shopify, Stripe, Pipedrive, Notion, and more — see Commerce, CRM & marketing.