How to connect 2chat to Hermes Agent
Connect 2chat to Hermes with ClawLink: paste your 2chat key once and 5 tools work from chat. No MCP server to run, nothing stored on your machine.
2chatAPI KEYMCP2Chat provides a programmable API for integrating WhatsApp and other text channels, enabling developers to send and receive messages, manage groups, and automate workflows.. Once connected, Hermes Agent can read and act on 2chat from chat — pairing, token refresh, and tool wiring handled for you.
Most guides for giving Hermes Agent 2chat 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 2chat setup: pair once in the browser and your always-on Hermes agent can act on 2chat 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 2chat.
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 2chat
Paste your API key in the dashboard.
- 3
Use it from chat
Ask Hermes Agent: "What can you do with 2chat?"
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 2chat in the ClawLink dashboard — paste your 2chat API key once.
Verify the connection by asking Hermes:
Use 2chat to 2chat get api usage info and walk me through the result in plain English.
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 2chat is connected in the dashboard, that agent calls the same 5 2chat tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
2chat MCP for Hermes
Looking for a 2chat MCP server for Hermes Agent? ClawLink connects 2chat to Hermes Agent and exposes 5 2chat tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using OpenClaw instead? The OpenClaw 2chat integration works the same way.
What the Hermes Agent 2chat integration can do
5 2chat tools are ready for Hermes Agent once the account is connected.
All 5 2chat tools for Hermes
| Tool | What it does |
|---|---|
2chat get API usage info _2chat_get_api_usage_info | Retrieve current API usage and account information |
2chat list contacts _2chat_list_contacts | List all contacts in your 2Chat account |
2chat list webhooks _2chat_list_webhooks | List all configured webhook subscriptions for WhatsApp and phone call events |
2chat create contact _2chat_create_contact | Create a new contact in your 2Chat account |
2chat test API key _2chat_test_api_key | Validate your API key and retrieve account info |
Try it: find the 2chat tool you need
Browse the 5 2chat tools
Click any tool to see exactly what Hermes can do and copy a ready-to-use prompt.
Example prompts
Use 2chat to 2chat get api usage info and walk me through the result in plain English.
Use 2chat to 2chat list contacts and walk me through the result in plain English.
Use 2chat to 2chat list webhooks and walk me through the result in plain English.
Use 2chat to 2chat create contact and walk me through the result in plain English.
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 2chat working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the 2chat API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected 2chat 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 2chat. | 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 2chat actions to the runtime in a format your agent can reliably use. | 5 tools for 2chat are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes 2chat 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 2chat in the browser, and the 5 tools above work from chat. There is no SDK and no config file, and the 2chat 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 2chat
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 2chat 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 2chat tools
2chat 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 2chat 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.
2chat 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 2chat 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 2chat integration?
Yes. ClawLink is the fastest way to connect Hermes to 2chat: link your 2chat account once in the browser and Hermes Agent can call the 2chat API through 5 ready-made tools — no custom code or token handling.
How do I connect 2chat 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 2chat in the dashboard and Hermes can use it from the next message — no config files, and the 2chat key you paste is stored server-side instead of in your environment.
How long does it take to connect 2chat to Hermes Agent?
About two minutes. Sign in, click Connect next to 2chat in the dashboard, authenticate, and Hermes Agent can use it from the next chat message.
Why use ClawLink instead of wiring 2chat 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 2chat working from chat.
Hermes paired but still can't use 2chat
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.
