How to connect Kapso to OpenClaw
Connect Kapso to OpenClaw with ClawLink: paste your Kapso key once and 10 tools work from chat. No MCP server to run, nothing stored on your machine.
KapsoAPI KEYMCPKapso provides APIs for WhatsApp messaging, customer and contact management, broadcasts, workflows, and serverless functions.. Once connected, OpenClaw can read and act on Kapso from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Kapso 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 Kapso setup: install one ClawHub skill, connect Kapso in the browser, and OpenClaw can call real Kapso 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 Kapso.
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 Kapso
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Kapso?"
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 Kapso in the ClawLink dashboard — paste your Kapso API key once.
Verify the connection by asking OpenClaw:
Pull the relevant data from Kapso, 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 Kapso is connected in the dashboard, that agent calls the same 10 Kapso tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Kapso MCP for OpenClaw
Looking for a Kapso MCP server for OpenClaw? ClawLink connects Kapso to OpenClaw and exposes 10 Kapso tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Kapso integration works the same way.
What the OpenClaw Kapso integration can do
10 Kapso tools are ready for OpenClaw once the account is connected.
All 10 Kapso tools for OpenClaw
| Tool | What it does |
|---|---|
Get function kapso_get_function | Retrieve one Kapso serverless function's code, runtime configuration, deployment status, and |
Get phone number kapso_get_phone_number | Retrieve one Kapso WhatsApp phone-number configuration by its Meta phone number ID |
Get phone number health kapso_get_phone_number_health | Run Kapso's live checks for one WhatsApp phone-number configuration and return its body-level |
Get workflow kapso_get_workflow | Retrieve one workflow's metadata, full graph definition, or available variables without |
List conversations kapso_list_conversations | List one page of WhatsApp conversations by recent activity, with filters for phone number |
List customers kapso_list_customers | List Kapso project customers and filter them by name, external customer ID, or creation time |
List functions kapso_list_functions | List serverless functions configured in the Kapso project, including runtime and deployment |
List messages kapso_list_messages | List one page of WhatsApp message history project-wide through Kapso Platform or for one phone |
List phone numbers kapso_list_phone_numbers | List WhatsApp phone-number configurations in the Kapso project, with filters for account |
List workflows kapso_list_workflows | List project workflows and filter them by lifecycle status, name, or creation time |
Try it: find the Kapso tool you need
Browse the 10 Kapso 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 Kapso, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Kapso, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Kapso, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Kapso, 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 Kapso working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Kapso API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Kapso 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 Kapso. | 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 Kapso actions to the runtime in a format your agent can reliably use. | 10 tools for Kapso are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Kapso 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 Kapso in the browser, and the 10 tools above work from chat. There is no SDK and no config file, and the Kapso 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 Kapso skill but can't call the tools
The ClawHub skill teaches OpenClaw about Kapso, but the calls run through the ClawLink plugin and your connected account. Make sure Kapso 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 Kapso 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 Kapso tools
Kapso 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 Kapso 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.
Kapso 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 Kapso 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 Kapso integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Kapso: link your Kapso account once in the browser and OpenClaw can call the Kapso API through 10 ready-made tools — no custom code or token handling.
How do I add Kapso to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Kapso skill from ClawHub, then you click Connect in the dashboard to authorize Kapso. OpenClaw calls the tools from the next message — no config files, and the Kapso key you paste is stored server-side instead of in your environment.
How long does it take to connect Kapso to OpenClaw?
About two minutes. Sign in, click Connect next to Kapso in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring Kapso 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 Kapso working from chat.
OpenClaw installed the Kapso skill but can't call the tools
The ClawHub skill teaches OpenClaw about Kapso, but the calls run through the ClawLink plugin and your connected account. Make sure Kapso 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.
