How to connect Wati to OpenClaw
Connect Wati to OpenClaw with ClawLink: paste your Wati key once and 5 tools work from chat. No MCP server to run, nothing stored on your machine.
WatiAPI KEYMCPWati is a WhatsApp Business API platform that automates marketing, sales, service, and support.. Once connected, OpenClaw can read and act on Wati from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Wati 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 Wati setup: install one ClawHub skill, connect Wati in the browser, and OpenClaw can call real Wati 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 Wati.
1Install the plugin
Paste the setup prompt into OpenClaw, or install from the terminal and ask OpenClaw to pair:
openclaw plugins install clawhub:clawlink-plugin- 2
Connect Wati
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Wati?"
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:
openclaw plugins install clawhub:clawlink-pluginThen 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 Wati in the ClawLink dashboard — paste your Wati API key once.
Verify the connection by asking OpenClaw:
Pull the relevant data from Wati, 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:
npx -y @useclawlink/cli loginlogin opens the same browser approval and stores a credential locally. Once Wati is connected in the dashboard, that agent calls the same 5 Wati tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Wati MCP for OpenClaw
Looking for a Wati MCP server for OpenClaw? ClawLink connects Wati to OpenClaw and exposes 5 Wati tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Wati integration works the same way.
What the OpenClaw Wati integration can do
5 Wati tools are ready for OpenClaw once the account is connected.
All 5 Wati tools for OpenClaw
| Tool | What it does |
|---|---|
Get teams wati_get_teams | Retrieve a list of teams from WATI |
Add contact wati_add_contact | Add a new contact in WATI |
Send session message wati_send_session_message | Send a session message to a specified WhatsApp number |
Update chat status wati_update_chat_status | Update the status of a chat/conversation in WATI Team Inbox |
Update contact attributes wati_update_contact_attributes | Update attributes of an existing contact |
Try it: find the Wati tool you need
Browse the 5 Wati tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Pull the relevant data from Wati, summarize it in plain English, and point out anything that needs attention.
Use Wati to add contact and walk me through the result in plain English.
Use Wati to send session message for me and draft the message before sending.
Update it in Wati, then show me exactly what changed.
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 Wati working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Wati API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Wati 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 Wati. | 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 Wati actions to the runtime in a format your agent can reliably use. | 5 tools for Wati are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Wati 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 Wati in the browser, and the 5 tools above work from chat. There is no SDK and no config file, and the Wati key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full Composio alternatives comparison.
Troubleshooting
OpenClaw installed the Wati skill but can't call the tools
The ClawHub skill teaches OpenClaw about Wati, but the calls run through the ClawLink plugin and your connected account. Make sure Wati 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 Wati 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 Wati tools
Wati 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 Wati 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.
Wati 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 Wati has the right scopes or account access. A valid key can still be too limited for some reads or writes.
FAQ
Is there a OpenClaw Wati integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Wati: link your Wati account once in the browser and OpenClaw can call the Wati API through 5 ready-made tools — no custom code or token handling.
How do I add Wati to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Wati skill from ClawHub, then you click Connect in the dashboard to authorize Wati. OpenClaw calls the tools from the next message — no config files, and the Wati key you paste is stored server-side instead of in your environment.
How long does it take to connect Wati to OpenClaw?
About two minutes. Sign in, click Connect next to Wati in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring Wati 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 Wati working from chat.
OpenClaw installed the Wati skill but can't call the tools
The ClawHub skill teaches OpenClaw about Wati, but the calls run through the ClawLink plugin and your connected account. Make sure Wati 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.
