--- import Layout from "../layouts/Layout.astro"; const googleServices = [ { index: "01", name: "Google Calendar", purpose: "Executor can read, create, update, or remove calendars and events, and manage calendar sharing rules, when you ask an agent to manage your schedule.", scope: "googleapis.com/auth/calendar", }, { index: "02", name: "Gmail", purpose: "Executor can read, search, compose, send, organize, trash, and permanently delete messages, and manage filters and other basic Gmail settings, only when you explicitly instruct an agent to work with your email.", scope: "mail.google.com · gmail.settings.basic", }, { index: "03", name: "Google Sheets", purpose: "Executor can read spreadsheet data, update cells, ranges, and worksheets, and write Drive-file smart chips when you ask an agent to work with a spreadsheet.", scope: "googleapis.com/auth/spreadsheets · drive.file", }, { index: "04", name: "Google Drive", purpose: "Executor can find, create, download, organize, share, or delete files and folders when you ask an agent to manage your Drive.", scope: "googleapis.com/auth/drive", }, { index: "05", name: "Google Docs, Slides, and Forms", purpose: "Executor can read and edit documents and presentations, and create or read forms and responses, when you ask an agent to work with that content.", scope: "documents · presentations · forms.body · forms.responses.readonly", }, { index: "06", name: "Google Contacts and Tasks", purpose: "Executor can read or update contacts and contact groups, read available profile fields, other contacts, or a Workspace directory, and manage task lists and tasks when you ask an agent to organize people or work.", scope: "contacts · user profile fields · directory.readonly · tasks", }, { index: "07", name: "Google Meet", purpose: "Executor can create and configure meeting spaces or read meeting records, participants, recordings, and transcripts when you request meeting-related work.", scope: "meetings.space.created · readonly · settings", }, { index: "08", name: "Google Photos", purpose: "Executor can upload and manage app-created media or read media that you explicitly select through Google Photos Picker.", scope: "photoslibrary.app-created read/write · photospicker.readonly", }, { index: "09", name: "Google Search Console", purpose: "Executor can inspect verified sites, sitemaps, indexed URLs, and search-performance data when you request website analysis.", scope: "googleapis.com/auth/webmasters", }, ] as const; ---
Google Workspace connections

Executor

Executor is an integration platform and MCP gateway for AI agents. It lets you securely connect Google Workspace and related Google services so an agent can read data and take the actions you request.

One connection Explicit permission User-directed actions

01 / Google data

What Executor accesses—and why

You choose which Google service to connect. Executor requests only the permissions needed for that connection and uses them to carry out your instructions.

{ googleServices.map((service) => (
{service.index}

{service.name}

{service.purpose}

{service.scope}
)) }

02 / Your control

Your Google account stays yours

Connecting Google does not give Executor permission to act on its own. An agent can use a Google tool only when you direct it to, subject to the policies and approvals you configure in Executor.

See the action

Executor exposes concrete Google actions with their inputs, not an open-ended account session.

Set the policy

Allow an action, require approval, or block it before an agent can run it.

03 / Privacy

Clear limits on Google data

Executor does not sell Google user data. We use Google data only to provide and improve the user-facing integration features you request, in accordance with our Privacy Policy. Executor's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.