How to connect Google Meet to Hermes Agent

Pairing is a two-step handshake: run hermes clawlink begin, approve the link in your browser, then run hermes clawlink finish. If you ran finish before approving, or the approval link expired, run hermes clawlink begin again to get a fresh link. Confirm the plugin was installed with --enable, then verify with hermes clawlink test.

Reconnect Google Meet from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded.

Google Meet tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every Google Meet call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again.

Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs.

This is the dominant failure on this integration: 15 of 26 production errors, all on the records list. Meet tool schemas load on demand the first time a tool runs and are cached after that, so the error clears on its own: wait a few seconds and retry the same call. If every Meet call in a fresh chat keeps failing with it, reconnect from the dashboard, and contact support if it still persists. The lazy-load pattern is the reason this specific tool name appears; it is not a permissions problem.

You have more than one Google Meet connection and ClawLink cannot tell which account the call is for. Three production occurrences, and the fix is structural: name or specify the connection when calling, or remove the extra connection in the dashboard so one default remains. The tool call is fine; the ambiguity is yours to resolve.

Two shapes here, and both are account-level, not ClawLink bugs. Either the space belongs to a different account than the one connected (check which Google account the connection holds), or the update touches a setting the connected Workspace edition does not allow. The production evidence for the second shape: the same account that got this on update_space also received updateAutoRecordingGeneration is not available to the user. and updateAttendanceReportGenerationType is not available to the user. Recording-related settings are edition-gated, so personal Gmail accounts fail exactly this way.

The tool exists under a different name. The read path is googlemeet_list_conference_records first, then googlemeet_get_conference_record_by_name with the record's name, then the transcript, recording, and participant tools that hang off the conferenceRecord id. get_conference_data is not one of the 15 tools; ClawLink returns a "Did you mean" line on every miss, and the doubled variant google-meet_googlemeet_list_conference_records (also logged in production) happens when the agent prefixes a tool name that already carries the integration name.

Recording and transcript reads depend on the call having been recorded with cloud recording enabled, and on the connected account having a Workspace edition that supports it. The create-meet schema warns personal accounts may not support recording and transcription options, and production logs updateAutoRecordingGeneration is not available to the user. for a connected account trying to enable it. If the calls were recorded in the Meet UI, the records appear under list_conference_records; if the setting could not be enabled, no record exists for the API to return, and no reconnect changes that.

Try reconnecting Google Meet and complete the consent flow in the same browser session. Partial OAuth approvals or switching accounts mid-flow can leave the connection incomplete.

Yes. ClawLink is the fastest way to connect Hermes to Google Meet: link your Google Meet account once in the browser and Hermes Agent can call the Google Meet API through 15 ready-made tools — no custom code or token handling.

Install the plugin with hermes plugins install ClawLink-HQ/hermes-plugin --enable, then pair once: run hermes clawlink begin, approve the link in your browser, and run hermes clawlink finish. Connect Google Meet in the dashboard and Hermes can use it from the next message — no config files or API keys to manage.

About two minutes. Sign in, click Connect next to Google Meet in the dashboard, authenticate, and Hermes Agent can use it from the next chat message.

The alternative to ClawLink is usually manual OAuth app setup plus your own token handling, permission troubleshooting, and tool plumbing for Hermes Agent. That is fine if you want to build and maintain the integration yourself. Most teams just want Google Meet working from chat.

They are different products. The native plugin (verified in the Hermes repo as plugins/google_meet) is a Playwright browser bot: you hand it a meet.google.com URL and it joins, scrapes live captions to a transcript, and can speak in realtime mode. It never touches the Meet API, and its own description says it only joins URLs you pass in, with no calendar scanning. ClawLink's 15 tools are the Meet REST API: create spaces, end conferences, and read conference records, participants, recordings, and transcripts. Join-and-transcribe is the plugin's job; records-as-data is this page's.

No. googlemeet_create_meet creates a Meet space through the Meet spaces API, and the schema has no calendar fields. The space is joinable by link, but nothing appears on your Google Calendar and nobody gets an invite. If you want a Calendar event with a meeting link, use the Google Calendar integration, where events carry a hangoutLink.

Yes, for calls where cloud recording was on: googlemeet_list_conference_records returns the conferenceRecord ids, then googlemeet_get_transcripts_by_conference_record_id, googlemeet_get_transcript, and googlemeet_list_recordings read the content. The limitation is the account, not the tools: recording and transcription are Workspace-edition features, and the live schema warns personal accounts may not support them. Production logs confirm a connected account getting updateAutoRecordingGeneration is not available to the user. on update_space.

Two scopes from the live auth config: https://www.googleapis.com/auth/meetings.space.created and https://www.googleapis.com/auth/meetings.space.settings. That covers creating spaces and reading conference records for calls the connected account participated in. It is not the Calendar scope and not the Workspace admin scope; the grant is revocable at myaccount.google.com/permissions.

Meet tool schemas load on demand the first time a tool runs, and this integration's most-used tool (googlemeet_list_conference_records, 41 of 85 production calls) hits the load window often: 15 of 26 failures are exactly "Tool schema for googlemeet_list_conference_records is not loaded yet." The fix is to wait and retry the same call; the schema caches after the first success.

Pairing is a two-step handshake: run hermes clawlink begin, approve the link in your browser, then run hermes clawlink finish. If you ran finish before approving, or the approval link expired, run hermes clawlink begin again to get a fresh link. Confirm the plugin was installed with --enable, then verify with hermes clawlink test.