Google Meet

Communication

Google Meet for AI agents. Managed auth, ready-made tools.

Create meeting spaces and read past meetings, participants, recordings and transcripts in Google Meet on behalf of each of your users.

About Google Meet

With the Google Meet connector, your agent works with the meetings of each user who connects their own Google account. It can create a meeting link, end a running call, and look back at past meetings: who joined, the recordings and the transcripts, using only the tools your project allows.

Google Meet is Google’s video meeting service, part of Google Workspace.

Tools

What your agent can do in Google Meet.

Each tool is a capability the model can call. You decide which ones a project allows, and every call runs with the end user's own Google Meet connection.

  • Create a meeting space

    Write
    google_meet_create_space

    Create a meeting space and get its link.

  • Get a meeting space

    Read
    google_meet_get_space

    Read a meeting space's link, code and settings.

  • End a meeting

    Write
    google_meet_end_conference

    End the call running in a meeting space.

  • List past meetings

    Read
    google_meet_list_conferences

    List past meetings with their start and end times.

  • List participants

    Read
    google_meet_list_participants

    List who joined a past meeting.

  • List recordings

    Read
    google_meet_list_recordings

    List a past meeting's recordings, saved in Google Drive.

  • Read a transcript

    Read
    google_meet_get_transcript

    Read a past meeting's transcript, entry by entry.

Control

Limits you can set.

You decide what your agent may do in Google Meet, and Agent200 runs every call within those limits.

  • Turn single tools on or off

    Allow google_meet_create_space and the reading tools, and switch off google_meet_end_conference if the agent should never end a call.

  • Restrict what the agent reaches

    Choose the endpoints and scopes a project may use, for example creating meetings but not reading transcripts. A call outside them is refused.

Get started

Connect Google Meet
in three steps.

  1. 1

    Set up the SDK

    Add the Agent200 SDK to the codebase you already have and authenticate with your API key. The key covers every connector enabled for the project.

    agent.js
    Conceptual example
    Set up the SDK with the Agent200 API key
    // One Agent200 API key covers every connector enabled for the project.
    const agent200 = new Agent200({
      apiKey: process.env.AGENT200_API_KEY,
    });
  2. 2

    Let your user connect Google Meet

    Each end user authorizes their own Google Meet account once. Agent200 runs the OAuth flow, handles the callback, stores the tokens and refreshes them.

    connect.js
    Conceptual example
    Let an end user connect their account (managed OAuth)
    // Each end user authorizes their own Google Meet account, once.
    const connection = await agent200
      .user("user_123")
      .connect("google_meet");
    
    if (connection.authorizationUrl) {
      // Show this link to your user; Agent200 handles the rest.
      console.log(connection.authorizationUrl);
    }
  3. 3

    Run with the Google Meet tools

    Name the user, the model and the tools. The model decides which Google Meet tools to call, and Agent200 executes them with that user's connection.

    run.js
    Conceptual example
    Run a request with the connector's tools
    const result = await agent200
      .user("user_123")
      .run({
        model: "openai/gpt-5.6-sol",
        input: "Create a Meet link for my call with Alex",
        tools: ["google_meet"],
      });
    
    console.log(result.output);

Access

Sign-in and permissions.

  • Who signs in

    Each of your users, once, with their Google account on Google's own sign-in page. You never see or store their password.

  • What access is requested

    The Google Meet permissions the connection needs, such as creating meeting spaces or reading meeting data, listed on Google's consent screen. Users can remove access later in their Google Account settings.

For agents

Instructions for AI agents.

Using a coding agent? Paste this brief into it, or give it the address of this page. It describes the Google Meet connector and how to use it.

Agent brief
Connector: Google Meet, through Agent200. In code: "google_meet".
What it does: Create meeting spaces and read past meetings, participants, recordings and transcripts in Google Meet on behalf of each of your users.
Page: https://www.agent200.com/tools/google-meet/

1. Get an Agent200 API key. If the developer has none, send them to https://agent200.com/platform/apikeys/ and ask them to choose "Create an API key". Read the key from the AGENT200_API_KEY environment variable. Never ask for it in chat, and never write it into code, prompts or logs.
2. Sign-in is managed OAuth. Each end user approves access once, on Google Meet's own page, through the authorization link Agent200 returns. Never ask a user for a Google Meet password or token in chat.
3. Give every request a stable id for the end user. Agent200 uses only that user's own connection.
4. Read tools: google_meet_get_space, google_meet_list_conferences, google_meet_list_participants, google_meet_list_recordings, google_meet_get_transcript. Write tools: google_meet_create_space, google_meet_end_conference. Name "google_meet" in the tools of a request; the model decides which tool to call.
5. Stay within the project's settings. If a tool is turned off or a call is refused, tell the user. Do not work around it.
6. Before a write, confirm with the user, unless they asked for that exact change.
7. For setup with a specific framework, follow its guide:
   https://www.agent200.com/tools/google-meet/framework/claude/
   https://www.agent200.com/tools/google-meet/framework/chatgpt/
   https://www.agent200.com/tools/google-meet/framework/claude-code/
   https://www.agent200.com/tools/google-meet/framework/muse/
   https://www.agent200.com/tools/google-meet/framework/grok-bot/
   https://www.agent200.com/tools/google-meet/framework/openai-dots/
   https://www.agent200.com/tools/google-meet/framework/claude-duet/
   https://www.agent200.com/tools/google-meet/framework/hermes-agent/
   https://www.agent200.com/tools/google-meet/framework/openclaw/

The code on the connector page is a conceptual example of the SDK. SDK reference: https://docs.igpt.ai/

This page is also available as Markdown, for agents and LLMs: /tools/google-meet.md

Guides

Use Google Meet with the AI you build on.

Step-by-step setup for Google Meet with a specific model, assistant or agent framework.

FAQ

Google Meet and Agent200, answered.

Who handles the Google Meet OAuth flow and the tokens?

Agent200. It runs the authorization, handles the callback on its own domain, stores the tokens and refreshes them. You do not build or maintain an OAuth integration for Google Meet.

Does my agent act as the end user?

Within what that user authorized, yes. Every request names an end user, and Agent200 uses only that user's Google Meet connection, never another user's. It cannot reach anything the user or Google Meet has not authorized.

Can I limit what my agent can do in Google Meet?

Yes. You choose which services, endpoints and authorization scopes are allowed in your Agent200 configuration, and the agent works only within them.

  • Slack

    Slack

    Search conversations and post messages in the workspaces your users connect.

    Managed OAuth Communication
  • Microsoft Teams

    Microsoft Teams

    Read channels and chats, post messages and set up meetings in Microsoft Teams on behalf of each of your users.

    Managed OAuth Communication
  • Discord

    Discord

    Read channels, post messages and start threads in the Discord servers your users connect.

    Managed OAuth Communication
  • Zoom

    Zoom

    Schedule, update and review Zoom meetings and their cloud recordings on behalf of each of your users.

    Managed OAuth Communication
200 OK

Start with Google Meet.
Your agent does the rest.

Your users connect their own Google Meet accounts. Agent200 handles the OAuth, the tokens and every tool call.

Book a demo.
See it in action.

Tell us who you are, then pick a time for a 1:1 session with an expert from our team.

We use your details only to email you about Agent200. See the Privacy Policy.

Pick a time. We'll take it from there.

A 1:1 session with an expert from our team, about what you are building.

Open in Calendly (opens in a new tab)