> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tess.im/llms.txt
> Use this file to discover all available pages before exploring further.

# Google Meet

The **Google Meet** connector integrates Tess with Google Meet. Once connected, the AI can help create meeting spaces and work with conference-related information inside chats and agents.

Google Meet is part of the Tess [Connectors](/en/connectors) ecosystem and uses **OAuth** authentication for Apps connectors.

## Prerequisites

<Info>
  * A Google account with access to Google Meet.
  * Permission to authorize Meet-related OAuth scopes for that account.
</Info>

## How to connect

<Tip>
  On some Apps connectors, the OAuth consent screen may show a third-party connection bridge name rather than Tess. That is normal—review the requested permissions and continue if they match what you expect.
</Tip>

<Steps>
  <Step title="Open the Connectors panel">
    In chat, click the **+** next to the message box and select **Connectors**. You can also manage connectors while editing an agent in Agent Studio.

    <Frame>
      <img src="https://mintlify.s3.us-west-1.amazonaws.com/tess-dfe1edf0/images/connectors/google-meet/01-connect-panel.png" alt="PRINT: (Connectors panel with Google Meet highlighted and the Connect button visible)" />
    </Frame>
  </Step>

  <Step title="Find Google Meet and click Connect">
    Under **Apps**, locate **Google Meet** and click **Connect** to start authentication.

    <Frame>
      <img src="https://mintlify.s3.us-west-1.amazonaws.com/tess-dfe1edf0/images/connectors/google-meet/02-oauth-consent.png" alt="PRINT: (Provider authorization / consent screen for Google Meet)" />
    </Frame>
  </Step>

  <Step title="Authorize access">
    Sign in with the account you want to use and review the requested permissions before confirming.
  </Step>

  <Step title="Confirm it is active">
    Back in Tess, **Google Meet** should appear under **Connected**, ready for chats and agents.

    <Frame>
      <img src="https://mintlify.s3.us-west-1.amazonaws.com/tess-dfe1edf0/images/connectors/google-meet/03-connected.png" alt="PRINT: (Tess callback or Connectors list showing Google Meet as Connected with a success state)" />
    </Frame>
  </Step>
</Steps>

## What you can do

* **Create Meet spaces** for calls and working sessions
* **Retrieve meeting details** such as join links and space identifiers
* **Support conference follow-up** when records, participants, or recordings are available to the account
* **Combine with Calendar** when you also need to attach meetings to events
* **Reduce tab switching** for scheduling and meeting prep

## Example prompts

> 1. Create a Google Meet space for a 30-minute sync and give me the join link.
> 2. Generate a Meet link for tomorrow's product review and summarize how to share it.
> 3. List recent conference records I can access and summarize who joined the latest one.
> 4. Create a Meet space with a clear name for the client onboarding call.

## Best practices

* If the meeting must appear on the calendar, say that explicitly (Calendar connector may also be needed).
* Confirm who should receive the link before broadcasting it.
* In agents, define whether Meet is only for link creation or also for post-meeting follow-up.

## Troubleshooting

<AccordionGroup>
  <Accordion title="App blocked / consent error" icon="circle-question">
    Reconnect and ensure the Google account can authorize Meet. Workspace admins may need to allow the app.
  </Accordion>

  <Accordion title="401 / connection dropped" icon="circle-question">
    Reconnect Google Meet in Connectors after password, 2FA, or admin policy changes.
  </Accordion>

  <Accordion title="Cannot access recordings or participants" icon="circle-question">
    Those resources may be unavailable for the account or meeting type. Verify access in Google Meet/Drive.
  </Accordion>
</AccordionGroup>

<Note>
  Tess uses the permissions of the connected account. It does not expand access beyond what that account can already do.

  Connectors involve access to external systems. Only connect accounts that fit the usage context, and review permissions carefully.
</Note>