# How to connect Zoom to Grok Bot (no API keys) > Connect Zoom to Grok Bot with ClawLink in one click — 51 tools your AI agent can call from chat via hosted OAuth. No API keys, no manual setup. Web version: https://claw-link.dev/grokbot/zoom Grok Bot runs on its own cloud computer, so most Zoom guides send you to register an OAuth app and paste keys into a sandbox that resets. ClawLink gives Grok Bot a more practical Zoom setup: it runs one CLI command, you approve once in the browser, and Grok Bot can call real Zoom actions from chat with no auth, token refresh, or tool wiring to build yourself. **Start here — paste this into Grok Bot to set up ClawLink:** > Set up ClawLink for me and tell me when it's ready. > 1. Pair this machine. It prints an approval link, so show me the link and stop, don't wait: `npx -y @useclawlink/cli login` > 2. I'll approve it in my browser, then reply "approved". > 3. When I say approved, connect the app: `npx -y @useclawlink/cli connect zoom` > 4. Then run `npx -y @useclawlink/cli whoami` and tell me whether ClawLink is ready. ## Setup It takes three steps to connect Grok Bot to Zoom. 1. **Pair from the terminal** — ask Grok Bot to run `npx -y @useclawlink/cli login` and approve the link it prints. 2. **Connect Zoom** — `npx -y @useclawlink/cli connect zoom`, then approve in the browser. 3. **Use it from chat** — ask Grok Bot in plain English. **The same CLI works from any agent with shell access:** ```bash npx -y @useclawlink/cli login # sign in via browser — no API key to paste npx -y @useclawlink/cli connect zoom # connect Zoom (browser OAuth) npx -y @useclawlink/cli actions zoom # list available actions npx -y @useclawlink/cli run zoom --input '' # execute (add --confirm for writes) ``` ### Install by command The prompt above does all of this. By hand, it is two commands Grok Bot runs in its own terminal, and one browser approval: ```bash npx -y @useclawlink/cli login # prints an approval link, approve it in your browser npx -y @useclawlink/cli connect zoom ``` Pair once and it sticks: the key is written to ~/.clawlink/credentials.json inside Grok Bot's sandbox, so it survives between sessions. Prefer native tools over shell commands? Add `https://claw-link.dev/api/mcp` as a custom connector at grok.com/connectors and approve the ClawLink sign-in. Same account, no CLI. Verify the connection by asking Grok Bot: > Use Zoom to add a meeting registrant and walk me through the result in plain English. ### Using a different agent? The CLI above is not specific to Grok Bot. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account the same way: ```bash npx -y @useclawlink/cli login ``` `login` opens the same browser approval and stores a credential locally. Once Zoom is connected in the dashboard, that agent calls the same 51 Zoom tools over MCP. Full setup for MCP clients and shell agents: [connect apps to any AI agent](https://claw-link.dev/learn/connect-apps-to-any-ai-agent). ## Zoom MCP for Grok Bot Looking for a Zoom MCP server for Grok Bot? ClawLink connects Zoom to Grok Bot and exposes 51 Zoom tools your agent can call over [MCP](https://claw-link.dev/learn/what-is-an-mcp-server), with [hosted auth](https://claw-link.dev/learn/oauth-for-ai-agents) and nothing to run or maintain yourself. Using a different agent? The [OpenClaw Zoom integration](https://claw-link.dev/openclaw/zoom) and the [Hermes Zoom integration](https://claw-link.dev/hermes/zoom) connect the same ClawLink account the same way. ## What the Grok Bot Zoom integration can do 51 Zoom tools are ready for Grok Bot once the account is connected. The 30 below are the ones people reach for most; your agent can call all 51. ### 30 of 51 Zoom tools for Grok Bot | Tool | What it does | |---|---| | **Add a meeting registrant** `zoom_add_a_meeting_registrant` | Register a participant for a Zoom meeting | | **Create a meeting** `zoom_create_a_meeting` | Create a Zoom meeting | | **Get a meeting** `zoom_get_a_meeting` | Get details for a specific Zoom meeting | | **Get meeting recordings** `zoom_get_meeting_recordings` | Get recordings for a Zoom meeting | | **Get past meeting participants** `zoom_get_past_meeting_participants` | Get participants from a past Zoom meeting | | **List meetings** `zoom_list_meetings` | List upcoming or recent Zoom meetings | | **Update a meeting** `zoom_update_a_meeting` | Update a Zoom meeting | | **Get a meeting summary** `zoom_get_a_meeting_summary` | IMPORTANT: This action requires a PAID Zoom account (Pro, Business, or Enterprise plan) | | **Get a webinar** `zoom_get_a_webinar` | Access Zoom Webinar details requires Pro or higher plan and Webinar add-on | | **Get iq conversation content analysis** `zoom_get_iq_conversation_content_analysis` | Retrieve content analysis for a Zoom IQ conversation by its ID | | **Get iq deal** `zoom_get_iq_deal` | Get details of a specific deal in Zoom Revenue Accelerator (formerly Zoom IQ) | | **Get user** `zoom_get_user` | Retrieves detailed information about a specific Zoom user by ID, email, or 'me' | | **Get zra conversation comments** `zoom_get_zra_conversation_comments` | Retrieve comments for a specific Zoom Revenue Accelerator (ZRA) conversation | | **Get zra conversation interactions** `zoom_get_zra_conversation_interactions` | Retrieves interaction details for a specific Zoom Revenue Accelerator (ZRA) conversation | | **Get zra conversation scorecards** `zoom_get_zra_conversation_scorecards` | Retrieve scorecards for a specific conversation in Zoom Revenue Accelerator | | **Get zra deal activities** `zoom_get_zra_deal_activities` | Retrieve activities associated with a Zoom Revenue Accelerator (ZRA) deal | | **List all recordings** `zoom_list_all_recordings` | This text details how to list Zoom cloud recordings for a user, notably by using "me" for | | **List archived files** `zoom_list_archived_files` | Lists archived meeting and webinar files within a specified date range (max 7 days) | | **List meeting summary templates** `zoom_list_meeting_summary_templates` | Retrieve a list of meeting summary templates for a specified user | | **List past meeting instances** `zoom_list_past_meeting_instances` | Retrieve all UUIDs for past instances of a given meeting | | **List users collaboration devices** `zoom_list_users_collaboration_devices` | List collaboration devices associated with a user | | **List users settings** `zoom_list_users_settings` | Retrieve a user's settings including meeting scheduling, in-meeting features, email | | **List webinar participants** `zoom_list_webinar_participants` | Get a list of past webinar participants with a Pro plan or above plus an add-on | | **List webinar registrants** `zoom_list_webinar_registrants` | Retrieves the list of registrants for a webinar with registration enabled | | **List webinars** `zoom_list_webinars` | The API lists all scheduled webinars for Zoom users with a webinar plan, using `me` for | | **List zra conversations** `zoom_list_zra_conversations` | List all conversations in Zoom Revenue Accelerator | | **List zra CRM accounts** `zoom_list_zra_crm_accounts` | Lists CRM accounts from Zoom Revenue Accelerator by account IDs | | **List zra CRM contacts** `zoom_list_zra_crm_contacts` | Retrieve CRM contact information from Zoom IQ Revenue Accelerator (ZRA) | | **List zra CRM deals** `zoom_list_zra_crm_deals` | Retrieve CRM deal information from Zoom Revenue Accelerator (ZRA) | | **List zra CRM leads** `zoom_list_zra_crm_leads` | Retrieve CRM lead information from Zoom IQ Revenue Accelerator (ZRA) | ## Example prompts **Add A Meeting Registrant** > Use Zoom to add a meeting registrant and walk me through the result in plain English. **Create A Meeting** > Create it in Zoom for me, then confirm the important fields before you finish. **Get A Meeting** > Pull the relevant data from Zoom, summarize it in plain English, and point out anything that needs attention. **Get Meeting Recordings** > Pull the relevant data from Zoom, summarize it in plain English, and point out anything that needs attention. ## ClawLink vs. building it yourself The alternative to ClawLink is usually manual OAuth app setup plus your own token handling, permission troubleshooting, and tool plumbing for Grok Bot. That is fine if you want to build and maintain the integration yourself. Most teams just want Zoom working from chat. | | Manual | ClawLink | |---|---|---| | **Connection flow** | Register a Zoom app, configure redirect URLs, manage consent details, and reconnect users when auth settings drift. | Users connect Zoom through the hosted browser flow and ClawLink keeps the token lifecycle out of your app code. | | **Ongoing maintenance** | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Zoom. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. | | **Agent usability** | You still need to expose the right Zoom actions to the runtime in a format your agent can reliably use. | 51 tools for Zoom are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Zoom to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for Grok Bot users instead. You install the plugin once, connect Zoom in the browser, and the 51 tools above work from chat. There is no SDK, no config file, and no API key handling. Choosing between them? Read the full [Composio alternatives](https://claw-link.dev/hub/composio-alternatives) comparison. ### Grok Bot says it cannot add ClawLink as an MCP server Grok Bot only attaches MCP servers that are reachable over the public internet, so a local stdio server is refused. You do not need one. Ask Grok Bot to run `npx -y @useclawlink/cli login` in its terminal instead. The CLI is a shell command, not an MCP server. If you would rather have native tools, add `https://claw-link.dev/api/mcp` as a custom connector at grok.com/connectors and approve the ClawLink sign-in. ### Connection succeeds but no tools appear Reconnect Zoom from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded. ### "Tool schema not loaded yet" error when calling Zoom tools 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. ### Zoom returns 403 or "permission denied" on one action while others work 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. ### OAuth finished in the browser but the account is still missing 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. ### Is there a Grok Bot Zoom integration? Yes. ClawLink is the fastest way to connect Grok Bot to Zoom: link your Zoom account once in the browser and Grok Bot can call the Zoom API through 51 ready-made tools — no custom code or token handling. ### How do I connect Zoom to Grok Bot with ClawLink? Ask Grok Bot to run `npx -y @useclawlink/cli login` in its terminal and approve the link it prints, then `npx -y @useclawlink/cli connect zoom` to authorize Zoom. Grok Bot calls the tools from the next message, and the pairing persists in its sandbox, so this is a one-time step: no config files or API keys to manage. ### How long does it take to connect Zoom to Grok Bot? About two minutes. Sign in, click Connect next to Zoom in the dashboard, authenticate, and Grok Bot can use it from the next chat message. ### Why use ClawLink instead of wiring Zoom up myself? The alternative to ClawLink is usually manual OAuth app setup plus your own token handling, permission troubleshooting, and tool plumbing for Grok Bot. That is fine if you want to build and maintain the integration yourself. Most teams just want Zoom working from chat. ### Grok Bot says it cannot add ClawLink as an MCP server Grok Bot only attaches MCP servers that are reachable over the public internet, so a local stdio server is refused. You do not need one. Ask Grok Bot to run `npx -y @useclawlink/cli login` in its terminal instead. The CLI is a shell command, not an MCP server. If you would rather have native tools, add `https://claw-link.dev/api/mcp` as a custom connector at grok.com/connectors and approve the ClawLink sign-in. ## Related - [SendGrid](https://claw-link.dev/grokbot/sendgrid) — Deliver transactional and marketing emails - [Dialpad tools](https://claw-link.dev/grokbot/dialpad) — Business phone, messaging, and video conferencing - [Discord Bot](https://claw-link.dev/grokbot/discord-bot) — Automate Discord server actions with bot-specific permissions