Google Meet

GOOGLE WORKSPACE · CALENDAR

Create and look up meetings tied to the user’s own account.

Connect Google Meet with Fabriq Developer

Your user consents at Google Meet. The credential lands in a vault your agent cannot read, and the tool list it gets back is the intersection of that user’s grant and the agent’s own scopes.

provider “meet”

from af_sdk import AgenticFabriq

af = AgenticFabriq()                      # reads AF_APP_ID / AF_APP_SECRET

url = await af.initiate_connection(request, provider="meet")   # consent at Google Meet
return redirect(url)

async with await af.for_user(request) as session:
    tools = await session.get_tools()     # only what this user granted

Provider names are surfaces, not vendors, and the authoritative list is the capabilities endpoint rather than any page including this one — an unknown name returns 400 with the valid list. Fabriq Developer is free to start and needs no provider paperwork. Start free or read the quickstart.

Connecting Google Meet in practice

Creating a meeting is metered separately from everything else: spaces.create is a "reduced write" allowed 10 times per minute per user against 100 for ordinary writes, so a scheduling agent is limited by space creation rather than by reads. Transcript entries are only available for 30 days after the conference ends, which puts a hard clock on anything that mines meeting text.

Scopes that draw scrutiny

https://www.googleapis.com/auth/meetings.space.created The scope spaces.create requires. As the name says, it covers spaces the app itself created, so it cannot manage a meeting somebody scheduled in the Calendar UI.

Rate limits

Read requests: 6,000 per minute per project, 600 per minute per user per project.
Write requests: 1,000 per minute per project, 100 per minute per user per project.
Reduced write requests (spaces.create): 100 per minute per project, 10 per minute per user per project.
No daily limits apply; only per-minute quotas are enforced.

Worth knowing

Transcript entries are available for 30 days after the conference ends, so a retrospective agent has a 30-day window and no more.
Google states plainly that the Meet REST API "isn’t intended for performance tracking or user evaluation within your domain" and that Meet data should not be collected for that purpose — relevant to anything that summarises attendance.
The 10-per-minute-per-user space creation limit is twenty times tighter than the general write limit, so batch provisioning of meetings needs pacing the rest of the integration does not.
Charges for exceeding quota are planned to begin in 2026, although standard use is free today.

Checked against Meet REST API usage limits (2026-09-29), spaces.create reference (authorization scope) (2026-09-29), Meet REST API overview (2026-09-29)

Acts as the person, not as itself

Each user connects their own account. Every call carries both identities — the agent and the person it is acting for — so the agent can never reach past what that individual can already do.

Credentials never touch the agent

Tokens live in the vault and attach server-side at call time. The agent holds a session, not a secret, and revoking access does not mean rotating a key.

Every call on the record

Who asked, which agent acted, which action ran, and the verdict that let it through — one audit trail across every integration, not one per vendor.

What an agent can do

Each action is granted on its own. An agent allowed to read is not thereby allowed to write, and the scope beside each row is what the acting user must have connected for it to run at all.

google_meet_create_spaceWRITE

Create a new Google Meet meeting space. Returns the meeting URL and details.

meetings.space.created

google_meet_get_spaceREAD

Get details about a Google Meet meeting space including its configuration and state. IMPORTANT: You need the space_id from google_meet_create_space or from the meeting URL.

meetings.space.readonly

google_meet_list_participantsREAD

List participants of a Google Meet meeting (current or past). IMPORTANT: You need the space_id from the meeting URL or google_meet_create_space.

meetings.space.readonly

google_meet_list_recordingsREAD

List recordings for a Google Meet meeting space. IMPORTANT: You need the space_id from the meeting URL or google_meet_create_space.

meetings.space.readonly