How to connect Zoom 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 Zoom from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded.

Zoom 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 Zoom 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.

The most common Zoom failure we actually see in prod: 10 of the 11 recorded Zoom errors on the ClawLink runtime are this string, and none of them are Zoom errors. The ClawLink account behind the connection is on an inactive plan, so the runtime blocks integration calls before they reach Zoom. Upgrade or reactivate the ClawLink account, and the same calls succeed without touching the Zoom connection.

Ask the agent to diagnose it:

Check whether my ClawLink account plan is active before retrying; if it is not, tell me what upgrading changes.

A real prod error for zoom_list_all_recordings. The tool needs user_id (the Zoom user's ID or email; me works for the connected user's own account), and the agent called it without one. Pass me for the connected account, or a real user ID from a users-listing call. zoom_list_meetings has the same requirement. This is an argument error, not a connection error.

Ask the agent to diagnose it:

Retry with user_id "me" for the connected account. If the agent needs another user's recordings, it must ask me for that user's ID first.

Zoom's own OAuth error string (error 4741 in developers.zoom.us/docs/integrations/oauth-error-messages): with multiple authorizations, the last token issued is considered valid and earlier ones are invalidated. In a hosted flow the equivalent is a stale or revoked grant, and the fix is not token surgery: reconnect Zoom from the ClawLink dashboard, which issues a fresh authorization, and retry. This is the card the manual guides do not have, because their fixes are server-to-server caching and grant-type changes that a hosted connection never exposes.

Ask the agent to diagnose it:

Reconnect Zoom from the dashboard, then retry the same tool call in a fresh chat.

Zoom's error 4738: an admin turned off the app for users under the account. With a hosted connection this surfaces as the connection failing on every tool, and no reconnect fixes it until the admin side is resolved. The user or an account admin needs to re-approve the app, then reconnect from the dashboard.

Ask the agent to diagnose it:

Tell me whether the Zoom account is under an admin who can re-approve the app, and do not keep retrying until that is resolved.

Zoom returns this when the token is authenticated but lacks the scope or entitlement for the specific endpoint. The manual fix taught everywhere is to add scopes in the Zoom Marketplace Scopes tab; in a hosted flow the scope set is fixed at connect time, so a scope gap means the connection cannot do that operation, and the entitlement case is separate: cloud recordings need a paid plan with cloud recording enabled (Zoom error 3301 means no cloud recording exists for the meeting, which is an expected empty result, not a permission problem). If one specific tool 403s while the rest work, check the plan entitlement first, then reconnect from the dashboard, which re-issues the grant.

Ask the agent to diagnose it:

Show me which tool is failing. If it is a recording tool, check whether my Zoom plan includes cloud recording before doing anything else.

Try reconnecting Zoom 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 Zoom: link your Zoom account once in the browser and Hermes Agent can call the Zoom API through 51 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 Zoom 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 Zoom 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 Zoom working from chat.

No. The manual route requires registering a Zoom app in the Zoom App Marketplace, managing scopes, and holding a client secret. ClawLink's Zoom app is already registered and its scopes are fixed at connect time, so you authorize your account in the browser without creating or approving anything in the Marketplace. This is the whole difference from the config-file setups the answer engines teach.

The answers to this query talk about Zoom AI Companion (no training on your content, consent controls), which is a different product. The question for this page is what an external agent can do with your Zoom account, and the answer is bounded by the grant: the connection can create and manage meetings, list and pull recordings, and read meeting/webinar data, and you can revoke it from your Zoom account's authorized-apps settings at any time. The AI Companion privacy features are unrelated to what this connection can access.

51 Zoom tools, covering meetings (create, update, get, list), recordings (get, list all, archived files), webinars (get, list, participants, registrants), and meeting summaries and past-meeting participants. The 30 tabulated on this page are the ones people reach for most; the agent can call all 51. Cloud-recording tools need a paid Zoom plan with cloud recording enabled; with a free account those calls return empty results or entitlement errors.

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.