# How to connect Clickmeeting to OpenClaw (paste one key, 39 tools) > Connect Clickmeeting to OpenClaw with ClawLink: paste your Clickmeeting key once and 39 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/clickmeeting The usual route to Clickmeeting access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical Clickmeeting setup: install one ClawHub skill, connect Clickmeeting in the browser, and OpenClaw can call real Clickmeeting actions from any chat surface with no auth, token refresh, or tool wiring to build yourself. ## Setup It takes three steps to connect OpenClaw to Clickmeeting. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Clickmeeting** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask OpenClaw in plain English. **Paste this into OpenClaw to set up ClawLink:** > I want to connect my apps to OpenClaw through ClawLink. > Please install the ClawLink plugin from ClawHub and enable it: `openclaw plugins install clawhub:clawlink-plugin` > When it is installed, tell me and stop. After I reply, give me the ClawLink pairing link. Setup notes, if you need them: https://claw-link.dev/skill.md **Alternative for any agent (no plugin needed):** if the OpenClaw plugin route isn't available or doesn't work, any AI agent with shell access can use the ClawLink CLI instead: ```bash npx -y @useclawlink/cli login # sign in via browser — no API key to paste npx -y @useclawlink/cli connect clickmeeting # connect Clickmeeting (browser OAuth) npx -y @useclawlink/cli actions clickmeeting # list available actions npx -y @useclawlink/cli run clickmeeting --input '' # execute (add --confirm for writes) ``` ### Install by command The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval: ```bash openclaw plugins install clawhub:clawlink-plugin ``` Then ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say `done`. Finally, connect Clickmeeting in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Clickmeeting API key once. Verify the connection by asking OpenClaw: > Use Clickmeeting to download file and walk me through the result in plain English. ### Using a different agent? The OpenClaw plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI: ```bash npx -y @useclawlink/cli login ``` `login` opens the same browser approval and stores a credential locally. Once Clickmeeting is connected in the dashboard, that agent calls the same 39 Clickmeeting 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). ## Clickmeeting MCP for OpenClaw Looking for a Clickmeeting MCP server for OpenClaw? ClawLink connects Clickmeeting to OpenClaw and exposes 39 Clickmeeting 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 Hermes instead? The [Hermes Clickmeeting integration](https://claw-link.dev/hermes/clickmeeting) works the same way. ## What the OpenClaw Clickmeeting integration can do 39 Clickmeeting tools are ready for OpenClaw once the account is connected. The 30 below are the ones people reach for most; your agent can call all 39. ### 30 of 39 Clickmeeting tools for OpenClaw | Tool | What it does | |---|---| | **Download file** `clickmeeting_download_file` | Download the content of a specific file from the ClickMeeting file library | | **Generate autologin URL** `clickmeeting_generate_autologin_url` | Generate an autologin hash for a conference participant | | **Generate session PDF report** `clickmeeting_generate_session_pdf_report` | Generates a PDF report containing analytics and details for a specific conference session | | **Get chat details** `clickmeeting_get_chat_details` | Retrieve details of a specific chat session | | **Get chats** `clickmeeting_get_chats` | Retrieve a list of all chat sessions | | **Get conference details** `clickmeeting_get_conference_details` | Retrieve detailed information about a specific ClickMeeting conference room | | **Get conference files** `clickmeeting_get_conference_files` | Retrieves the list of files uploaded to a specific conference room's file library | | **Get conference sessions** `clickmeeting_get_conference_sessions` | Retrieves past sessions for a conference room | | **Get conference skins** `clickmeeting_get_conference_skins` | Retrieves a list of available conference room skins that can be used to customize the | | **Get conferences** `clickmeeting_get_conferences` | Retrieve a list of conference rooms from your ClickMeeting account filtered by status | | **Get file details** `clickmeeting_get_file_details` | Retrieve detailed information about a specific file from the ClickMeeting file library | | **Get file library** `clickmeeting_get_file_library` | Retrieve a list of files from the ClickMeeting file library | | **Get phone gateways** `clickmeeting_get_phone_gateways` | Retrieve available phone dial-in numbers for ClickMeeting webinars | | **Get ping** `clickmeeting_get_ping` | Check API service status | | **Get registrations** `clickmeeting_get_registrations` | Retrieve registrations for a conference room by status | | **Get session attendees** `clickmeeting_get_session_attendees` | Retrieves the list of attendees who participated in a specific session of a conference room | | **Get session details** `clickmeeting_get_session_details` | Retrieve detailed statistics for a specific past conference session | | **Get session poll details** `clickmeeting_get_session_poll_details` | Retrieve details of a specific poll conducted during a session | | **Get session qa history** `clickmeeting_get_session_qa_history` | Retrieve the Q&A history for a specific session | | **Get session recordings** `clickmeeting_get_session_recordings` | Retrieve all recordings for a conference room | | **Get session registrations** `clickmeeting_get_session_registrations` | Retrieve registrations for a specific session within a conference room | | **Get session survey details** `clickmeeting_get_session_survey_details` | Retrieve details of a specific survey/poll conducted during a session | | **Get session surveys** `clickmeeting_get_session_surveys` | Retrieves the list of surveys conducted during a specific conference session | | **Get time zone list** `clickmeeting_get_time_zone_list` | Retrieves all available time zones supported by ClickMeeting | | **Get time zone list by country** `clickmeeting_get_time_zone_list_by_country` | Retrieve available time zones for a specific country by ISO 3166-1 alpha-2 country code | | **Get token by email** `clickmeeting_get_token_by_email` | Retrieve access tokens assigned to a specific email address for a token-protected conference | | **List access tokens** `clickmeeting_list_access_tokens` | Retrieve all generated access tokens for a token-protected conference room | | **List registrations by status** `clickmeeting_list_registrations_by_status` | Retrieve registered participants of a conference room filtered by registration status | | **Create access tokens** `clickmeeting_create_access_tokens` | Generate access tokens for conference participants | | **Create conference** `clickmeeting_create_conference` | Create a new conference | ## Example prompts **Download File** > Use Clickmeeting to download file and walk me through the result in plain English. **Generate Autologin Url** > Use Clickmeeting to generate autologin url and walk me through the result in plain English. **Generate Session Pdf Report** > Use Clickmeeting to generate session pdf report and walk me through the result in plain English. **Get Chat Details** > Pull the relevant data from Clickmeeting, summarize it in plain English, and point out anything that needs attention. ## ClawLink vs. building it yourself The alternative to ClawLink is usually manual API key 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 Clickmeeting working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Clickmeeting API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Clickmeeting account becomes available to the agent without you building credential management. | | **Ongoing maintenance** | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Clickmeeting. | 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 Clickmeeting actions to the runtime in a format your agent can reliably use. | 39 tools for Clickmeeting are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Clickmeeting 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 OpenClaw users instead. You install the plugin once, connect Clickmeeting in the browser, and the 39 tools above work from chat. There is no SDK and no config file, and the Clickmeeting key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full [Composio alternatives](https://claw-link.dev/hub/composio-alternatives) comparison. ### OpenClaw installed the Clickmeeting skill but can't call the tools The ClawHub skill teaches OpenClaw about Clickmeeting, but the calls run through the ClawLink plugin and your connected account. Make sure Clickmeeting 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. ### Connection succeeds but no tools appear Reconnect Clickmeeting 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 Clickmeeting tools Clickmeeting 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 Clickmeeting 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. ### Clickmeeting 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. ### API key setup works but results look incomplete Double-check that the API key for Clickmeeting has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Clickmeeting integration? Yes. ClawLink is the fastest way to connect OpenClaw to Clickmeeting: link your Clickmeeting account once in the browser and OpenClaw can call the Clickmeeting API through 39 ready-made tools — no custom code or token handling. ### How do I add Clickmeeting to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Clickmeeting skill from ClawHub, then you click Connect in the dashboard to authorize Clickmeeting. OpenClaw calls the tools from the next message — no config files, and the Clickmeeting key you paste is stored server-side instead of in your environment. ### How long does it take to connect Clickmeeting to OpenClaw? About two minutes. Sign in, click Connect next to Clickmeeting in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Clickmeeting up myself? The alternative to ClawLink is usually manual API key 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 Clickmeeting working from chat. ### OpenClaw installed the Clickmeeting skill but can't call the tools The ClawHub skill teaches OpenClaw about Clickmeeting, but the calls run through the ClawLink plugin and your connected account. Make sure Clickmeeting 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. ## Related - [Cloudinary](https://claw-link.dev/openclaw/cloudinary) — Cloudinary is a cloud-based media management platform for uploading, storing, transforming, and delivering images and videos via CDN. - [Penpot](https://claw-link.dev/openclaw/penpot) — Open-source design and prototyping platform for collaborative design workflows. - [OpenClaw Canva integration](https://claw-link.dev/openclaw/canva) — Create designs, upload assets, export content, and manage brand templates