Skip to main content
Per-app Google setup is deprecated. All Google apps now share one Google OAuth client and one Redirect URI. To use your own client, follow the Google setup guide. Credentials saved for one Google app apply to all of them.

​
Overview

OneCLI connects AI agents to Google Meet through Google’s OAuth flow. Agents can create meeting rooms, generate meeting links, and list recordings. The gateway injects OAuth credentials into requests to the Google Meet REST API automatically. This is useful for scheduling agents that need to generate meeting links, or agents that need to access meeting recordings for note-taking.

​
Connect Google Meet

This applies on OneCLI Cloud and self-hosted alike. One Google client serves every Google app in OneCLI, so you set it up once. If you already did it for another Google app, skip to step 2.

1. Set up your Google client

Follow the Google setup guide. It enables the Google APIs, sets up the consent screen, creates the OAuth client, and adds the Redirect URI.
Open Connections > Google Meet, select Connect Google Meet, pick your Google account, and click Allow.
OneCLI connect window for Google Meet showing Configuration required, the setup guide link, and the Configure credentials button.

The Google Meet connect window before a Google client is set up.

​
What agents can do

  • Create new meeting spaces with unique meeting links
  • Get details for an existing meeting space
  • List meeting recordings and their download URLs
  • Read meeting participant lists and join/leave times
  • End active meetings

​
Controlling access

Access is per agent: grant the connection to each agent that needs it, choosing per tool what runs freely, what needs human approval, and what stays blocked — a read-only agent is a single grant. Organization rules add guardrails on top, like rate limits and blanket blocks. Everything is checked before credential injection, so a blocked request never reaches Google Meet.