Sema4.ai Google Workspace integration
What this application is and what it's for
Sema4.ai is an enterprise platform for building and running AI agents — software assistants that carry out real work for the people who use them.
The purpose of this application is to let a Sema4.ai agent complete Google Workspace tasks on your behalf. Once you connect your Google account, an agent can help you get through everyday work across Gmail, Google Drive, Google Docs, Google Sheets, and Google Calendar — for example, finding and summarizing email, drafting and sending replies, creating and editing documents and spreadsheets, locating and organizing files, and checking availability and scheduling meetings.
Sema4.ai requests access to your Google data for a single reason: so that an agent can read and act on the Gmail, Drive, Docs, Sheets, and Calendar items you ask it to work with. The agent acts only after you sign in with Google and grant consent, only when one of your tasks calls for it, and only within your own Google permissions — never more.
This page is published by Sema4.ai, Inc. on our own verified domain, sema4.ai (opens in a new tab), and is viewable without signing in. The rest of it explains exactly which Google data the application uses, why each piece is needed, and how that data is handled.
About Sema4.ai
Sema4.ai, Inc. is an enterprise software company that builds a platform for creating, running, and governing AI agents. Agents follow instructions from their human users to complete real work, using tools — connections to systems such as email, calendars, file storage, and business applications — to do so.
- Company and product overview: sema4.ai (opens in a new tab) and sema4.ai/products (opens in a new tab)
- The Google Workspace integration is one of the tools Sema4.ai makes available to agents. It is delivered as a set of MCP servers — one per Google product — from the Sema4.ai MCP Gallery.
What the integration does
When a user connects their Google account, an agent can perform the following actions as that user, scoped to whatever that user is already permitted to access in Google. Nothing happens automatically — the agent only takes an action when the user's task calls for it.
| Google product | What an agent can do |
|---|---|
| Gmail | Search and read messages and attachments; create and update drafts; apply, remove, and move labels; send email. |
| Google Drive | Search, read, and download files and metadata; upload files; share files; read file comments. |
| Google Docs | Create, search, read, and edit documents; read document comments. |
| Google Sheets | Read spreadsheet data and structure; create spreadsheets and worksheets; append and update rows. |
| Google Calendar | List calendars; list and read events; create and update events. |
An agent is given only the specific tools its builder selects, so a given agent may be able to do less than the full list above. See Tools with MCP.
Google data we access, and why
The integration requests access through Google OAuth 2.0. Each Google product uses the minimum scopes its features require, and requests them only for the products you choose to connect. Below is every scope the integration can request, what it allows, and why it is needed.
Gmail
| Scope | Allows | Why the integration needs it |
|---|---|---|
https://www.googleapis.com/auth/gmail.readonly | Read and search messages and attachments | So an agent can find and summarize emails the user asks about. |
https://www.googleapis.com/auth/gmail.modify | Create and update drafts; apply, remove, move labels | So an agent can prepare drafts and organize the mailbox at the user's request. This scope does not permanently delete messages. |
https://www.googleapis.com/auth/gmail.send | Send email and send drafts | So an agent can send a message the user has asked it to send. |
Google Drive
| Scope | Allows | Why the integration needs it |
|---|---|---|
https://www.googleapis.com/auth/drive.readonly | Read and search files and metadata | So an agent can find and read the files the user references. |
https://www.googleapis.com/auth/drive.file | Create and manage files the integration opens or creates | So an agent can save outputs (for example a generated document or upload) the user requested. |
https://www.googleapis.com/auth/drive | Read, organize, and share files across the user's Drive | So an agent can locate, share, and act on existing files when the user's task spans their Drive. |
Google Docs
| Scope | Allows | Why the integration needs it |
|---|---|---|
https://www.googleapis.com/auth/documents | Create, read, and edit documents | So an agent can draft and update documents the user is working on. |
https://www.googleapis.com/auth/drive.readonly | Locate documents to open | So an agent can find a document by name or recency before editing it. |
https://www.googleapis.com/auth/drive.file | Create and manage documents it makes | So an agent can create a new document and keep working with it. |
Google Sheets
| Scope | Allows | Why the integration needs it |
|---|---|---|
https://www.googleapis.com/auth/spreadsheets | Read and write spreadsheet data and structure | So an agent can read data and create or update spreadsheets and rows. |
https://www.googleapis.com/auth/drive.file | Create and manage spreadsheets it makes | So an agent can create a new spreadsheet and keep working with it. |
Google Calendar
| Scope | Allows | Why the integration needs it |
|---|---|---|
https://www.googleapis.com/auth/calendar | List calendars; read, create, and update events | So an agent can check availability and schedule or update events the user requests. |
How you connect and control access
- You sign in and consent. The first time you use a Google tool, Google asks you to sign in and approve the access listed above. The agent receives access only after you approve.
- Acts as you, within your permissions. The agent operates with your Google identity, so it can never reach data you couldn't reach yourself.
- Least privilege by design. A builder can attach just a subset of an integration's tools to an agent, and the integration requests only the scopes those products need.
- You can revoke access at any time. Remove Sema4.ai's access to your Google account from your Google Account's Apps with access to your account (opens in a new tab) page. The agent then loses access immediately.
To set the integration up for an organization, see Set up OAuth for MCPs.
Privacy and data handling
- Privacy policy. Read how Sema4.ai collects, uses, and protects information in the Sema4.ai Privacy Policy (opens in a new tab).
- Used only to perform the user's task. Google data is accessed solely to carry out the actions a user asks an agent to perform. It is not sold, and it is not used to train generative AI or machine-learning models.
- Limited Use. Sema4.ai's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy (opens in a new tab), including the Limited Use requirements.
Questions about this integration or our handling of Google data? Contact Sema4.ai at sema4.ai (opens in a new tab) or see the Privacy Policy (opens in a new tab).