Google

Vibe is an AI assistant built by Mistral AI. It connects to Google services through Connectors: secure OAuth 2.0 integrations that let users interact with their Google data using natural language.

When a user connects a Google service, Vibe can read and search data in that service, and act on it with explicit user approval. Every write action requires the user's confirmation before it is executed. Passwords and credentials are never stored by Vibe; authentication is handled entirely through Google's OAuth 2.0 flow.

Supported Google services

Supported Google services

Vibe integrates with the following Google services:

ServiceWhat Vibe does
GmailSearch email threads, read messages, create drafts and send emails on request, and organize emails with labels.
Google CalendarList calendars, search events, create, update, or delete events, and respond to invitations.
Google DriveSearch files, read file content (including Google Docs and Sheets), view file metadata and permissions, and create and copy files.
Google BigQueryExplore datasets and tables, and run SQL queries to analyze data.
Google Workspace (admin)Sync Google Groups with Vibe's role-based access control for enterprise customers.
Gmail

Gmail

Vibe uses the Gmail API to help users manage their email through natural language (for example, "Summarize my unread emails from the legal team" or "Draft a reply to the last message from Alice and send it once I approve").

Scopes requested:

  • gmail.readonly: Search email threads, read message content, list drafts, and list labels. These read-only operations are the foundation of every email-related task.
  • gmail.compose: Create email drafts for the user to review, and send emails or drafts at the user's request. Vibe never sends automatically: an email is sent only after the user approves its recipients, subject, and body.
  • gmail.modify: Organize emails by creating, updating, and deleting labels, and by applying or removing labels on individual messages and threads. The readonly and compose scopes cannot modify labels or message metadata, so modify is required for these organizational actions.
Google Calendar

Google Calendar

Vibe uses the Google Calendar API to help users manage their schedule (for example, "What meetings do I have tomorrow?" or "Create a team meeting for Friday at 2 pm").

Scope requested:

  • calendar (full access): List the user's calendars, search and retrieve events, create new events, update existing events, delete events, and respond to invitations (accept, decline, tentative). The calendar.readonly scope is insufficient because Vibe also creates, updates, and deletes events on behalf of the user.
Google Drive

Google Drive

Vibe uses the Google Drive API to help users work with their files (for example, "Find the latest Q3 revenue deck and summarize it" or "Create a folder for the project review documents").

Scopes requested:

  • drive.readonly: Search files by title, content, type, or owner; list recently accessed files; read file content including Google Docs and Sheets via export; retrieve file metadata; and check file permissions.
  • drive.file: Create folders, create files, upload content, and copy files on the user's behalf. This scope only covers files created or opened by Vibe, so drive.readonly is also requested for searching and reading the rest of the user's Drive. Like every write action, file creations and copies only run after the user approves them.
Google BigQuery

Google BigQuery

Vibe uses the BigQuery API to help users explore and query their data warehouses (for example, "Show me the top 10 customers by revenue from the sales dataset").

Scope requested:

  • bigquery: Explore datasets and tables, and execute SQL queries on the user's behalf. The bigquery.readonly scope is insufficient because users also need to run queries that create temporary tables and manage job execution.
Google Workspace (Admin Directory)

Google Workspace (Admin Directory)

Vibe offers a Google Workspace integration for enterprise customers. Organization administrators can sync their Google Groups with Vibe's internal permission system so that team memberships are automatically reflected in Vibe's access controls.

Scopes requested:

  • admin.directory.user.readonly: List users in the customer's Google Workspace domain to map Workspace identities to Vibe accounts. Only user metadata (email, name, organizational unit) is read; user accounts are never modified.
  • admin.directory.group.readonly: List Google Groups in the customer's domain and enumerate group members. This lets administrators automatically map Google Groups to Vibe permission roles. Groups are never created, modified, or deleted.
Use your own Google OAuth client

Use your own Google OAuth client

i
Information

Coming soon. You can't bring your own OAuth client to the built-in Google Connectors yet: they authenticate through the Mistral AI client, and Vibe doesn't expose fields for your own client credentials. The sections below describe the flow as it will work when the feature is available.

By default, the Google Connectors authenticate through the Mistral AI OAuth client. To control the consent screen, scopes, and access policies yourself, create an OAuth client in your own Google Cloud project.

Before you start, make sure that you have the Owner or Editor role on a Google Cloud project. If your users are on Google Workspace, create the project in your Workspace organization.

1. Enable the APIs

  1. In the Google Cloud console, select or create a project.
  2. Go to APIs & Services > Library.
  3. Search for and enable the API of each service that you plan to connect: Gmail API, Google Calendar API, Google Drive API, or BigQuery API.

2. Configure the consent screen

  1. Go to Google Auth platform > Branding. If you see Google Auth platform not configured yet, click Get started.
  2. Under App information, enter an App name (for example, Vibe), select a User support email, and click Next.
  3. Under Audience, select a user type and click Next:
    • Internal (recommended): only users in your Workspace organization can connect. You don't need Google verification or test users.
    • External: any Google account can connect, subject to the publishing limits for External apps.
  4. Under Contact information, enter an email address and click Next.
  5. Under Finish, select I agree to the Google API Services: User Data Policy, click Continue, and then click Create.

3. Add the scopes

  1. Go to Google Auth platform > Data Access and click Add or remove scopes.
  2. Under Manually add scopes, paste the scopes of the services that you enabled, then click Add to table and Update.
  3. Click Save.

The Google Connectors use the following scopes:

https://www.googleapis.com/auth/gmail.readonly
https://www.googleapis.com/auth/gmail.compose
https://www.googleapis.com/auth/gmail.modify
https://www.googleapis.com/auth/calendar
https://www.googleapis.com/auth/drive.readonly
https://www.googleapis.com/auth/drive.file
https://www.googleapis.com/auth/bigquery

4. Create the OAuth client

Warning

The redirect URI domain depends on your Vibe deployment. On a Mistral-managed deployment (for example, a private cloud) or a self-hosted deployment, replace callback.mistral.ai with the domain of your deployment:

https://callback.<your-mistral-deployment-domain>/v1/integrations_auth/oauth2_callback
  1. Go to Google Auth platform > Clients and click Create client.

  2. Set Application type to Web application and enter a Name (for example, Vibe Connectors).

  3. Under Authorized redirect URIs, click Add URI and enter the following URI exactly:

    https://callback.mistral.ai/v1/integrations_auth/oauth2_callback
  4. Select Use this client for an AI-powered agent.

  5. Click Create.

  6. In the confirmation dialog, copy the Client ID and Client secret, or click Download JSON.

Warning

Google shows the client secret only once. Store it in a secret manager. If you lose it, open the client and click Add secret to generate a new one.

5. Connect with your client

To use your client, enter the Client ID and Client secret when you configure the Google Connector in Vibe, then connect your account. The Google consent screen shows your app name instead of Mistral AI.

Publishing limits for External apps

Publishing limits for External apps

While the publishing status of an External app is Testing, the following limits apply:

  • Only test users can connect. To add them, go to Google Auth platform > Audience > Test users and click Add users. You can add up to 100 test users.
  • Google expires each authorization after 7 days, so users must reconnect every week.

To lift these limits, click Publish app in Audience. The Gmail scopes and drive.readonly are restricted scopes: Google requires app verification and an annual security assessment before users outside your test list can use your app.

Tip

If your Workspace admin restricts third-party app access, they must trust your client ID in the Google Admin console under Security > Access and data control > API controls.

Troubleshooting

Troubleshooting

The following table lists common errors when users connect through your own client:

ErrorFix
redirect_uri_mismatchCheck that the redirect URI matches exactly, with no trailing slash.
org_internalThe app is Internal and the user is outside your Workspace organization.
access_denied or "app hasn't been verified"The app is External in Testing and the user isn't a test user.
API has not been used in projectEnable the API for that service in APIs & Services > Library, then retry.

Vibe follows a strict consent model:

  1. OAuth consent: Users authenticate directly with Google and see exactly which permissions Vibe requests before granting access.
  2. Per-action approval: Every write action (sending a draft, creating an event, modifying a label) requires the user's explicit approval inside Vibe before it is executed. Users can approve, decline, or pre-authorize specific actions. See Safety and approvals for details.
  3. Disconnect at any time: Users can revoke Vibe's access from the Connectors page or from their Google Account permissions. Disconnecting immediately stops all access.
Data handling and privacy

Data handling and privacy

  • Real-time Connectors (Gmail, Google Calendar, BigQuery): data is fetched in real time for the current request and is not stored on our servers. Disconnecting revokes access immediately.
  • No training: data accessed through Connectors is never used to train or fine-tune Mistral AI models, regardless of the user's plan.
  • Encryption: all communication with Google APIs uses TLS encryption in transit.

For full details, see the Mistral AI terms and Trust Center.

Google API Services User Data Policy

Google API Services User Data Policy

Vibe's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.