# How to connect Whautomate to OpenClaw (paste one key, 17 tools) > Connect Whautomate to OpenClaw with ClawLink: paste your Whautomate key once and 17 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/whautomate The usual route to Whautomate 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 Whautomate setup: install one ClawHub skill, connect Whautomate in the browser, and OpenClaw can call real Whautomate 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 Whautomate. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Whautomate** — 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 whautomate # connect Whautomate (browser OAuth) npx -y @useclawlink/cli actions whautomate # list available actions npx -y @useclawlink/cli run whautomate --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 Whautomate in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Whautomate API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from Whautomate, summarize it in plain English, and point out anything that needs attention. ### 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 Whautomate is connected in the dashboard, that agent calls the same 17 Whautomate 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). ## Whautomate MCP for OpenClaw Looking for a Whautomate MCP server for OpenClaw? ClawLink connects Whautomate to OpenClaw and exposes 17 Whautomate 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 Whautomate integration](https://claw-link.dev/hermes/whautomate) works the same way. ## What the OpenClaw Whautomate integration can do 17 Whautomate tools are ready for OpenClaw once the account is connected. The 15 below are the ones people reach for most; your agent can call all 17. ### 15 of 17 Whautomate tools for OpenClaw | Tool | What it does | |---|---| | **Get account info** `whautomate_get_account_info` | Retrieve account information for the authenticated user | | **Get all webhooks** `whautomate_get_all_webhooks` | Retrieve all registered webhooks | | **Get broadcast by ID** `whautomate_get_broadcast_by_id` | Retrieve a specific broadcast's details | | **Get broadcasts** `whautomate_get_broadcasts` | Retrieve a list of broadcasts | | **Get contacts** `whautomate_get_contacts` | Retrieve a list of contacts | | **Get messages of contact** `whautomate_get_messages_of_contact` | Retrieve chat messages for a specific contact | | **Get segments** `whautomate_get_segments` | Retrieve a list of segments | | **Get service by ID** `whautomate_get_service_by_id` | Retrieve details of a specific service by its unique ID | | **Get service categories** `whautomate_get_service_categories` | Retrieve a list of service categories | | **Get services** `whautomate_get_services` | Retrieve a list of services with optional filters | | **Get staff availability blocks** `whautomate_get_staff_availability_blocks` | Retrieve a staff member's blocked time schedule over a date range | | **Get staff by ID** `whautomate_get_staff_by_id` | Retrieve detailed information about a specific staff member | | **Get staffs** `whautomate_get_staffs` | Retrieve a list of staff members | | **Add contact** `whautomate_add_contact` | Add a new contact | | **Update service** `whautomate_update_service` | Update an existing Whautomate service | ## Example prompts **Get Account Info** > Pull the relevant data from Whautomate, summarize it in plain English, and point out anything that needs attention. **Get All Webhooks** > Pull the relevant data from Whautomate, summarize it in plain English, and point out anything that needs attention. **Get Broadcast By Id** > Pull the relevant data from Whautomate, summarize it in plain English, and point out anything that needs attention. **Get Broadcasts** > Pull the relevant data from Whautomate, 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 Whautomate working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Whautomate API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Whautomate 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 Whautomate. | 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 Whautomate actions to the runtime in a format your agent can reliably use. | 17 tools for Whautomate are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Whautomate 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 Whautomate in the browser, and the 17 tools above work from chat. There is no SDK and no config file, and the Whautomate 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 Whautomate skill but can't call the tools The ClawHub skill teaches OpenClaw about Whautomate, but the calls run through the ClawLink plugin and your connected account. Make sure Whautomate 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 Whautomate 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 Whautomate tools Whautomate 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 Whautomate 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. ### Whautomate 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 Whautomate has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Whautomate integration? Yes. ClawLink is the fastest way to connect OpenClaw to Whautomate: link your Whautomate account once in the browser and OpenClaw can call the Whautomate API through 17 ready-made tools — no custom code or token handling. ### How do I add Whautomate to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Whautomate skill from ClawHub, then you click Connect in the dashboard to authorize Whautomate. OpenClaw calls the tools from the next message — no config files, and the Whautomate key you paste is stored server-side instead of in your environment. ### How long does it take to connect Whautomate to OpenClaw? About two minutes. Sign in, click Connect next to Whautomate in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Whautomate 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 Whautomate working from chat. ### OpenClaw installed the Whautomate skill but can't call the tools The ClawHub skill teaches OpenClaw about Whautomate, but the calls run through the ClawLink plugin and your connected account. Make sure Whautomate 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 - [Connect DataRobot](https://claw-link.dev/openclaw/datarobot) — DataRobot is a machine learning platform that automates model building, deployment, and monitoring, enabling organizations to derive predictive insights from large datasets. - [Chatbotkit](https://claw-link.dev/openclaw/chatbotkit) — ChatBotKit is a platform that enables developers to build and manage AI-powered chatbots, offering comprehensive APIs and SDKs for seamless integration into applications. - [Just One API](https://claw-link.dev/openclaw/just-one-api) — Just One API provides unified access to public social media, creator, entertainment, and ecommerce data across hundreds of metered endpoints.