---
title: "Google Meet"
description: "Find accessible completed Google Meet conferences. Read participants of a selected Google Meet conference. Requires a Google OAuth access token with meetings.space.readonly and access to the meeting artifacts. Artifact a"
---

> Documentation Index
> Fetch the complete documentation index at: https://help.tooluse.net/llms.txt
> Use this file to discover all available pages before exploring further.

# Google Meet

<p>Find completed Google Meet conferences and inspect attendance for a meeting follow-up.</p>

<h2>Example workflows</h2>

<p>Copy a prompt into your connected AI client after connecting this integration. Choose resources you can access and review the supported command before running it.</p>

<h3>Find the meeting to follow up</h3>

<pre><code class="language-text" data-workflow-prompt>Read one page of up to 20 accessible completed Google Meet conference records. Show their returned start and end times and conference resource names so I can choose the correct meeting. Tell me if another page is available. Do not infer a meeting title or decisions when those fields are absent.</code></pre>
<p><a href="https://tooluse.net/tools/integrations/google-meet?command=google-meet.conference-records.list">Explore this command: google-meet.conference-records.list</a></p>

<h3>Prepare an attendance handoff</h3>

<pre><code class="language-text" data-workflow-prompt>Ask me to choose a conference resource name from my completed meetings. Read one page of up to 20 participants and prepare an attendance list from the returned identity fields. Distinguish signed-in, anonymous and telephone participants when the response does. Preserve participant resource names and flag further pages. Do not claim access to transcripts, meeting notes or participant email addresses unless returned.</code></pre>
<p><a href="https://tooluse.net/tools/integrations/google-meet?command=google-meet.participants.list">Explore this command: google-meet.participants.list</a></p>

<details data-command-index><summary>What you can do (2)</summary>
<h2>What you can do</h2>
<p>Available commands: 2 (2 read, 0 write). Enable only the commands your application needs.</p>
<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Command</th>
<th>Effect</th>
</tr>
</thead>
<tbody><tr>
<td><a href="https://help.tooluse.net/integrations/google-meet#command-google-meet-conference-records-list">Find accessible completed Google Meet conferences</a> — <code>google-meet.conference-records.list</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/google-meet#command-google-meet-participants-list">Read participants of a selected Google Meet conference</a> — <code>google-meet.participants.list</code></td>
<td>Read</td>
</tr>
</tbody></table>
</div>
</details>
<h2>Connect and use</h2>

<p><a href="https://tooluse.net/tools/integrations/google-meet?connect=own">Connect and use</a></p>
<p>This connection uses your provider account.</p>
<p>Connect this integration, enter your provider credentials, choose commands and save. Complete provider authorization if prompted.</p>
<h2>Get your provider credentials</h2>
<p>Follow these steps for Google Meet, then enter the issued values in the connection form below.</p>
<ol>
<li>Requires a Google OAuth access token with meetings.space.readonly and access to the meeting artifacts. Artifact availability depends on Workspace edition and retention. Token renewal is customer-managed. Open the official API documentation, create credentials limited to this workflow, then enter the values shown below. Select only the commands you need. Revoking credentials at the provider disconnects access.</li>
</ol>
<p><a href="https://developers.google.com/workspace/meet/api/reference/rest">Official credential setup</a></p>
<h2>Where to enter credentials</h2>
<p>In the integration page, sign in, choose your workspace and open Connect. If a <strong>Credentials</strong> choice is shown, select <strong>Use my credentials</strong>. Fill the following connection fields and save. Provider credentials belong in this form, never in an MCP configuration or tool input.</p>
<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Connection field</th>
<th>Requirement</th>
</tr>
</thead>
<tbody><tr>
<td>Customer-managed OAuth access token</td>
<td>Required</td>
</tr>
</tbody></table>
</div><p>Open API keys and create a Tooluse.net key for the enabled commands.</p>
<p>Set TOOLUSE_API_KEY in your client and use the shared MCP configuration.</p>
<p><a href="https://help.tooluse.net/clients">Configure Claude Code, Codex or Cursor once</a></p>

<h2>Permissions and results</h2>

<p>If you have more than one workspace, check the selected workspace in the connection or API-key dialog before saving. Roles, enabled commands, expiry and revocation use Tooluse.net&#39;s existing permissions. Disabling a connection or revoking a key immediately prevents new calls.</p>

<p>Send one Claude tool_use block per request. Keep the same Idempotency-Key when retrying the same request; use a new key for a new call. The response includes the shared Tooluse.net receipt and Claude tool_result. Check both HTTP status and the returned tool result before treating a call as successful.</p>

<p>Your connection&#39;s daily allowance and key permissions also apply. Adding a connection does not make a provider request.</p>

<p>Calls return the shared execution receipt and a Claude tool_result. Provider output varies by operation; consult the provider documentation for its response fields. Unconfirmed calls should be checked before retrying.</p>

<h2>Call from your client</h2>

<p>Use the shared MCP configuration. Refresh your client&#39;s tool list after saving the connection or changing key permissions, then call the returned tool name with the example input below.</p>

<p><a href="https://help.tooluse.net/clients">Configure Claude Code, Codex or Cursor once</a></p>

<h2>Discover your enabled tools</h2>

<p>List permitted tools in Claude format. Read every page using page and size (maximum 100) until all results have been received. Use the returned name, not a catalog capability identifier, in the tool_use block.</p>

<pre><code class="language-bash">curl 'https://api.tooluse.net/v1/tools' \
  -H "Authorization: Bearer $TOOLUSE_API_KEY"
</code></pre>

<p>Find this command in the tool list permitted by your key. Replace svc_FROM_YOUR_TOOL_LIST with its returned name. Use a new Idempotency-Key for each new call and retain it when retrying that same call.</p>

<h2>HTTP call</h2>

<pre><code class="language-bash">curl 'https://api.tooluse.net/v1/tool-calls' \
  -H "Authorization: Bearer $TOOLUSE_API_KEY" \
  -H 'Content-Type: application/json' \
  -H 'Idempotency-Key: replace-with-a-new-call-id' \
  --data '{
  "type": "tool_use",
  "id": "toolu_example",
  "name": "svc_FROM_YOUR_TOOL_LIST",
  "input": {
    "query": {
      "pageSize": 20
    }
  }
}'
</code></pre>

<p>Send one Claude tool_use block per request. Keep the same Idempotency-Key when retrying the same request; use a new key for a new call. The response includes the shared Tooluse.net receipt and Claude tool_result. Check both HTTP status and the returned tool result before treating a call as successful.</p>

<h2>Commands</h2>

<details id="command-google-meet-conference-records-list">
<summary><span>Find accessible completed Google Meet conferences — <code>google-<wbr>meet.<wbr>conference-<wbr>records.<wbr>list</code></span></summary>
<p>Find accessible completed Google Meet conferences. One explicit provider request; no retries or automatic follow-up pages. Customer permissions and quotas apply.</p>
<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://tooluse.net/tools/integrations/google-meet?connect=own&amp;command=google-meet.conference-records.list">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>query</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.pageSize</code></td>
<td>integer</td>
<td>Required</td>
<td></td>
<td><code>minimum: 1; maximum: 100</code></td>
</tr>
<tr>
<td><code>query.pageToken</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td><code>minLength: 1; maxLength: 2048</code></td>
</tr>
<tr>
<td><code>query.filter</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td><code>minLength: 1; maxLength: 500</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/google-meet/commands/google-meet.conference-records.list">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "query": {
    "pageSize": 20
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-google-meet-participants-list">
<summary><span>Read participants of a selected Google Meet conference — <code>google-<wbr>meet.<wbr>participants.<wbr>list</code></span></summary>
<p>Read participants of a selected Google Meet conference. One explicit provider request; no retries or automatic follow-up pages. Customer permissions and quotas apply.</p>
<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://tooluse.net/tools/integrations/google-meet?connect=own&amp;command=google-meet.participants.list">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.conference</code></td>
<td>string</td>
<td>Required</td>
<td></td>
<td><code>minLength: 1; maxLength: 200</code></td>
</tr>
<tr>
<td><code>query</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.pageSize</code></td>
<td>integer</td>
<td>Required</td>
<td></td>
<td><code>minimum: 1; maximum: 100</code></td>
</tr>
<tr>
<td><code>query.pageToken</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td><code>minLength: 1; maxLength: 2048</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/google-meet/commands/google-meet.participants.list">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "conference": "conf1"
  },
  "query": {
    "pageSize": 20
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<h2>Errors</h2>

<p>Check the key&#39;s expiry, revocation, workspace and allowed operations.</p>

<p>Reuse the same idempotency key only for the same request.</p>

<p>The connection or provider limit has been reached. Check the receipt before retrying.</p>

<h2>Test the connection</h2>

<p>Open the integration&#39;s commands below to inspect parameters and examples. Start with a read command for an account or resource you can access. Refresh your client&#39;s tool list, use the returned tool name, and check the execution result and usage. Provider charges and permissions still apply. Never test a write against production data without reviewing it.</p>

<p><a href="https://developers.google.com/workspace/meet/api/reference/rest">Official provider documentation</a></p>

Source: https://help.tooluse.net/integrations/google-meet/index.mdx
