How to connect Wati to Hermes Agent
Connect Wati to Hermes 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, Hermes Agent can read and act on Wati from chat — pairing, token refresh, and tool wiring handled for you.
Most guides for giving Hermes Agent Wati access start with registering your own OAuth app or pasting API keys into env files, then leave the token refresh and tool wiring to you. ClawLink gives Hermes a more practical Wati setup: pair once in the browser and your always-on Hermes agent can act on Wati for you, reading and doing real work on your behalf with no auth, token refresh, or tool wiring to build yourself.
Setup
It takes three steps to connect Hermes to Wati.
1Install and pair
Install the ClawLink plugin, then pair Hermes with a one-time browser approval:
hermes plugins install ClawLink-HQ/hermes-plugin --enable- 2
Connect Wati
Paste your API key in the dashboard.
- 3
Use it from chat
Ask Hermes Agent: "What can you do with Wati?"
Install by command
The prompt above walks Hermes through this. By hand, it is four commands and a browser approval:
hermes plugins install ClawLink-HQ/hermes-plugin --enable
hermes clawlink begin # prints an approval link — open it and approve
hermes clawlink finish # after approving in the browser
hermes clawlink testThen connect Wati in the ClawLink dashboard — paste your Wati API key once.
Verify the connection by asking Hermes:
Pull the relevant data from Wati, summarize it in plain English, and point out anything that needs attention.
Using a different agent?
The Hermes 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 Hermes
Looking for a Wati MCP server for Hermes Agent? ClawLink connects Wati to Hermes Agent and exposes 5 Wati tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using OpenClaw instead? The OpenClaw Wati integration works the same way.
What the Hermes Agent Wati integration can do
5 Wati tools are ready for Hermes Agent once the account is connected.
All 5 Wati tools for Hermes
| 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 Hermes 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 Hermes Agent. 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 Hermes Agent 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
Hermes paired but still can't use Wati
Pairing is a two-step handshake: run hermes clawlink begin, approve the link in your browser, then run hermes clawlink finish. If you ran finish before approving, or the approval link expired, run hermes clawlink begin again to get a fresh link. Confirm the plugin was installed with --enable, then verify with hermes clawlink test.
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 Hermes Agent Wati integration?
Yes. ClawLink is the fastest way to connect Hermes to Wati: link your Wati account once in the browser and Hermes Agent can call the Wati API through 5 ready-made tools — no custom code or token handling.
How do I connect Wati to Hermes with ClawLink?
Install the plugin with hermes plugins install ClawLink-HQ/hermes-plugin --enable, then pair once: run hermes clawlink begin, approve the link in your browser, and run hermes clawlink finish. Connect Wati in the dashboard and Hermes can use it 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 Hermes Agent?
About two minutes. Sign in, click Connect next to Wati in the dashboard, authenticate, and Hermes Agent 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 Hermes Agent. That is fine if you want to build and maintain the integration yourself. Most teams just want Wati working from chat.
Hermes paired but still can't use Wati
Pairing is a two-step handshake: run hermes clawlink begin, approve the link in your browser, then run hermes clawlink finish. If you ran finish before approving, or the approval link expired, run hermes clawlink begin again to get a fresh link. Confirm the plugin was installed with --enable, then verify with hermes clawlink test.
