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
Writegoogle_meet_create_spaceCreate a meeting space and get its link.
-
Get a meeting space
Readgoogle_meet_get_spaceRead a meeting space's link, code and settings.
-
End a meeting
Writegoogle_meet_end_conferenceEnd the call running in a meeting space.
-
List past meetings
Readgoogle_meet_list_conferencesList past meetings with their start and end times.
-
List participants
Readgoogle_meet_list_participantsList who joined a past meeting.
-
List recordings
Readgoogle_meet_list_recordingsList a past meeting's recordings, saved in Google Drive.
-
Read a transcript
Readgoogle_meet_get_transcriptRead a past meeting's transcript, entry by entry.
No tool matches that search.
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_spaceand the reading tools, and switch offgoogle_meet_end_conferenceif 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
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.jsConceptual exampleSet 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
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.jsConceptual exampleLet 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
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.jsConceptual exampleRun 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.
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.
-
Google Meet + Claude
How to connect Google Meet to Claude
-
Google Meet + ChatGPT
How to connect Google Meet to ChatGPT
-
Google Meet + Claude Code
How to connect Google Meet to Claude Code
-
Google Meet + Muse
How to connect Google Meet to Muse
-
Google Meet + Grok Bot
How to connect Google Meet to Grok Bot
-
Google Meet + OpenAI Dots
How to connect Google Meet to OpenAI Dots
-
Google Meet + Claude Duet
How to connect Google Meet to Claude Duet
-
Google Meet + Hermes Agent
How to connect Google Meet to Hermes Agent
-
Google Meet + OpenClaw
How to connect Google Meet to OpenClaw
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.