How to connect Pumble to OpenClaw
Connect Pumble to OpenClaw with ClawLink: paste your Pumble key once and 9 tools work from chat. No MCP server to run, nothing stored on your machine.
PumbleAPI KEYMCPPumble is a team communication platform for channels, direct messages, scheduled messages, and workspace collaboration.. Once connected, OpenClaw can read and act on Pumble from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Pumble 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 Pumble setup: install one ClawHub skill, connect Pumble in the browser, and OpenClaw can call real Pumble 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 Pumble.
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 Pumble
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Pumble?"
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 Pumble in the ClawLink dashboard — paste your Pumble API key once.
Verify the connection by asking OpenClaw:
Pull the relevant data from Pumble, 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 Pumble is connected in the dashboard, that agent calls the same 9 Pumble tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Pumble MCP for OpenClaw
Looking for a Pumble MCP server for OpenClaw? ClawLink connects Pumble to OpenClaw and exposes 9 Pumble tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Pumble integration works the same way.
What the OpenClaw Pumble integration can do
9 Pumble tools are ready for OpenClaw once the account is connected. The 8 below are the ones people reach for most; your agent can call all 9.
8 of 9 Pumble tools for OpenClaw
| Tool | What it does |
|---|---|
Get current user pumble_get_current_user | Return the Pumble user and workspace associated with the connected API key |
Get message pumble_get_message | Fetch one Pumble message by its message ID and channel ID |
List channel messages pumble_list_channel_messages | Return one page of recent messages from a channel, continuing backward through history with a |
List channels pumble_list_channels | List channels visible to the connected Pumble user, including channel IDs needed by message |
List users pumble_list_users | List users in the current Pumble workspace with stable IDs and profile details |
Search messages pumble_search_messages | Search Pumble messages and return one bounded page |
Edit message pumble_edit_message | Replace the text of an existing Pumble message in a channel |
Send message pumble_send_message | Immediately post a text message to a Pumble channel identified by its channel ID |
Try it: find the Pumble tool you need
Browse the 8 Pumble 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 Pumble, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Pumble, summarize it in plain English, and point out anything that needs attention.
List the relevant items in Pumble, group them by priority, and recommend what OpenClaw should do next.
List the relevant items in Pumble, group them by priority, and recommend what OpenClaw should do next.
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 Pumble working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Pumble API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Pumble 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 Pumble. | 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 Pumble actions to the runtime in a format your agent can reliably use. | 9 tools for Pumble are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Pumble 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 Pumble in the browser, and the 9 tools above work from chat. There is no SDK and no config file, and the Pumble 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 Pumble skill but can't call the tools
The ClawHub skill teaches OpenClaw about Pumble, but the calls run through the ClawLink plugin and your connected account. Make sure Pumble 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 Pumble 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 Pumble tools
Pumble 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 Pumble 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.
Pumble 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 Pumble 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 Pumble integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Pumble: link your Pumble account once in the browser and OpenClaw can call the Pumble API through 9 ready-made tools — no custom code or token handling.
How do I add Pumble to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Pumble skill from ClawHub, then you click Connect in the dashboard to authorize Pumble. OpenClaw calls the tools from the next message — no config files, and the Pumble key you paste is stored server-side instead of in your environment.
How long does it take to connect Pumble to OpenClaw?
About two minutes. Sign in, click Connect next to Pumble in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring Pumble 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 Pumble working from chat.
OpenClaw installed the Pumble skill but can't call the tools
The ClawHub skill teaches OpenClaw about Pumble, but the calls run through the ClawLink plugin and your connected account. Make sure Pumble 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.
