How to connect Zoom to OpenClaw

The ClawHub skill teaches OpenClaw about Zoom, but the calls run through the ClawLink plugin and your connected account. Make sure Zoom is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.

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.

This error string gets a wrong answer in search results, and the wrongness matters. Most "invalid token" fixes for Zoom-on-OpenClaw discuss OpenClaw's gateway device token and the AUTH_TOKEN_MISMATCH error, which is a pairing problem between OpenClaw and its gateway, not a Zoom problem, and does not apply to a hosted connection. In this setup the only token is the Zoom OAuth grant, held server-side. If every Zoom call fails with an invalid-token error, the connection's grant was revoked, which happens when the Zoom account password or security settings change, and reconnecting from the dashboard re-runs the consent flow. If only some calls fail, the account simply lacks the role the endpoint needs, which is a 403-shaped problem, not a token one.

Ask the agent to diagnose it:

Call zoom_get_user to check which Zoom account the connection acts as, then quote the exact error from the failed call. If it is an invalid-token error I will reconnect Zoom from the dashboard; do not retry before then.

The causes the search engines teach for this error are scope-level: an OAuth app missing a scope, a user role too low for the endpoint, or a deactivated app owner. In a hosted connection the app's scopes are fixed and complete, so the real checks are account-level. The connected account's role in the Zoom account decides what it can do: a member without host rights cannot create or update meetings, and some endpoints, like recording downloads, are restricted to the owner or admins. Second, the agent may have sent a placeholder or guessed id (like "YOUR_ID" or a meeting id from documentation) instead of a real one: ask it to run zoom_list_meetings first and retry with the real meeting id from those results.

Ask the agent to diagnose it:

Run zoom_get_user and zoom_list_meetings and show me the real account and meeting ids. Quote the exact 403 text, then retry the failing action with a real id from that list.

Zoom's published ceiling is 100 meetings created per day per user, with plan-tier rate limits on top, and an agent asked to create meetings in a loop is the traffic shape that meets it. The 429 response is the signal to change the shape of the work, not to retry faster: confirm each meeting is actually needed before creating it, batch the reads instead of paging one at a time, and spread a bulk operation across the day if it is genuinely large. The meeting-creation cap resets per day, so a stalled bulk import is usually finished the next day rather than by retrying.

Ask the agent to diagnose it:

Tell me how many Zoom calls you have made and how many meetings you have created today. Quote the exact error text. Do not create another meeting until I confirm it is needed.

Two different failures. If OpenClaw shows no Zoom tools at all, the connection or pairing is incomplete: confirm the skill was installed, that Zoom shows as connected in the dashboard, and start a fresh chat so the tool catalog reloads. If most tools work and a single name fails, that name is wrong rather than missing: the error lists the closest real tools, and clawlink_list_tools --integration zoom shows the exact catalog. There is also a first-call timing case unique to this setup: schemas load on demand, so the opening Zoom call in a fresh session can arrive before the catalog and needs one retry.

Ask the agent to diagnose it:

List the Zoom tools you actually have access to. If there are none, run clawlink_list_integrations and say so plainly. If there are, tell me which one lists meetings and use that exact name.

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 OpenClaw to Zoom: link your Zoom account once in the browser and OpenClaw can call the Zoom API through 51 ready-made tools — no custom code or token handling.

Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Zoom skill from ClawHub, then you click Connect in the dashboard to authorize Zoom. OpenClaw calls the tools 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 OpenClaw 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 OpenClaw. 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 the guides teach is to create a Marketplace OAuth or Server-to-Server app, grant scopes like meeting:read/write and user:read, and paste the client id, client secret, and account id into environment variables. This page uses a hosted Zoom OAuth app instead: you click Connect in the dashboard, approve Zoom's consent screen, and the connection is stored server-side. The Marketplace app already exists, and the agent calls the 51 tools through the connection rather than through credentials on your machine.

The plugin is OpenClaw's native route and its ceiling is joining: it joins calls as a guest using a Chrome profile and can attend and transcribe, but it does not create meetings and does not use the Zoom API, per the OpenClaw docs. Anything API-level, creating meetings, listing them, pulling recordings, managing registrants, needs a different route, which is what this page is. Both work from OpenClaw chat, and they are complementary: the plugin for being in the room, this connection for everything the API can do around the room.

Yes, and that is the exact constraint this flow answers. The search engines answer "create meetings without your own app" with "someone must own a Zoom app", naming integration platforms as the hosted-connector category. ClawLink is that category for OpenClaw: the Zoom OAuth app is hosted, you approve the connection once in the browser, and zoom_create_a_meeting works from your next chat. There is no client secret in any environment file, and the meeting is created under your Zoom account, so it appears in your calendar and your meeting list.

The 51 tools cover the meeting surface: create, update, list, and get meetings, meeting registrants, recordings and past-meeting participants, users and their settings, plus webinars and the AI summary surface (meeting summaries and IQ content analysis). Creating meetings is the write to be deliberate about, since a meeting invites real people at a real time; recordings and summaries are the read surface that makes the connection useful after the fact.

The ClawHub skill teaches OpenClaw about Zoom, but the calls run through the ClawLink plugin and your connected account. Make sure Zoom is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.