Skip to main content
Connecting Google Drive, Calendar, and Gmail lets Claude read documents, spreadsheets, calendar events, and email in any channel where the connector is on. Claude connects with its own credential, not a person’s. This connector calls Google’s HTTP APIs, and it’s separate from members’ personal claude.ai connectors. A member’s own Google connector applies in one-to-one DMs. Claude can also use it in a channel for that member’s own tasks, after the member allows it.

​
Choose OAuth or a service account

The Add a connector dialog offers two routes to Google: Both routes create a credential and an allowed-websites rule for the Google hosts the connector uses.

​
Add the connector with Google sign-in

Use a dedicated Google account for this connector (for example, claude@yourcompany.example.com), not your own. The connector is shared: anyone in a channel where it’s on can ask Claude to read whatever this account can see in Drive, Calendar, and Gmail. A dedicated account starts with no access until you share the specific folders and calendars Claude needs, and keeps its activity under a separate identity in Google’s audit log.
Go to Organization settings > Claude Tag > Connectors, click Add, and select Google Drive, Google Calendar, or Gmail. The connect form lists the Google hosts the connector can reach; there are no scopes to choose. The first credential you add for a service from the Connectors tab is on in every workspace and channel as soon as you save it. To give it narrower reach, see where a new connector applies before you sign in. Click Sign in with Google Drive (or Sign in with Google Calendar, or Sign in with Gmail), approve the Google consent screen, and the credential is saved. The connector’s reach is whatever the signed-in Google account can see. Share the relevant folders and calendars with that account in Google before testing.

​
Add the connector with a service account

Go to Organization settings > Claude Tag > Connectors, click Add, and select Custom connector. Fill in these fields in the connect form. The first credential you add for a service from the Connectors tab is on in every workspace and channel as soon as you save it. To give it narrower reach, see where a new connector applies before you save the connector. Click Connect to save the connector. For Google Workspace data (Drive, Calendar, Gmail, Docs), the service account needs domain-wide delegation configured in your Google Admin console. In the service account’s domain-wide delegation entry, list every scope you entered in Scopes, or https://www.googleapis.com/auth/cloud-platform if you left Scopes empty. Google’s guide is at developers.google.com/identity/protocols/oauth2/service-account. Google refuses the token request when the domain-wide delegation entry is missing one of the requested scopes. Claude then reports HTTP 502 with a reason that starts with injection failed ("<connection name>"). The Agent Proxy injects the credential at the network boundary; the model and the sandbox are not given the key. See how Agent Proxy works.

​
Verify the connection

In a channel where the connector is on, in a new thread:
Google Drive, Calendar, or Gmail appears in the list once the connector is live. New threads pick up the connector on their own; in an existing thread, ask Claude to use the service by name. To confirm the connector works, ask Claude in the same thread to read something from the service, such as today’s calendar events or a named document.