Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.
| 1 | ## Use Google Super tool slugs with a Google Super connected account |
| 2 | |
| 3 | Google Super is a separate toolkit with its own tool slugs. If the connected account was created for Google Super, run the corresponding GOOGLESUPER_* tool, such as GOOGLESUPER_CREATE_MEET, instead of the GOOGLEMEET_* slug. A separate Google Meet auth config or connected account is not required when the workflow is intentionally using Google Super. |
| 4 | |
| 5 | ## Configure Meet scopes and enable the Google Meet API before creating Meet spaces |
| 6 | |
| 7 | For Meet space creation/settings through Google Super, include the Meet scopes https://www.googleapis.com/auth/meetings.space.created and https://www.googleapis.com/auth/meetings.space.settings in the auth config, then initiate a new connection so the new scopes are granted. Also enable the Google Meet API in the Google Cloud Console project backing the OAuth app. |
| 8 | |
| 9 | ## Fetch transcript entries by first resolving the conference record |
| 10 | |
| 11 | Start with `GOOGLEMEET_LIST_CONFERENCE_RECORDS`. It can filter conference records by meeting code, space name, or time range. Use the resulting conference record ID with `GOOGLEMEET_GET_TRANSCRIPTS_BY_CONFERENCE_RECORD_ID`, then call `GOOGLEMEET_LIST_TRANSCRIPT_ENTRIES` with the transcript resource to retrieve the spoken segments. |
| 12 | |
| 13 | ## 403 permission errors usually mean the conference resource is inaccessible or missing |
| 14 | |
| 15 | For a Google Meet API error like "Permission denied on resource Conference (or it might not exist)", verify that the signed-in connected account has access to the conference/artifact and that the conference record exists. Compare the provider response through a least-privileged Composio tool or Proxy Execute call; provider tokens are redacted from connected-account responses and should not be copied into a support workflow. |
| 16 | |
| 17 | ## Recordings and transcripts require an eligible Google Workspace edition and enabled feature |
| 18 | |
| 19 | Google Meet recordings and transcripts are available on several eligible Google |
| 20 | Workspace editions, not only Enterprise. The meeting host must have the feature, |
| 21 | the organization's administrator must allow it, and recording or transcription |
| 22 | must have been started for the meeting. Free personal accounts do not provide |
| 23 | the same artifact availability. |
| 24 | |
| 25 | Check Google's current [Meet feature matrix](https://support.google.com/meet/answer/10459644) |
| 26 | and [transcript requirements](https://support.google.com/meet/answer/12849897) |
| 27 | when diagnosing a missing recording or transcript. |