# How to connect Botpress to OpenClaw (paste one key, 53 tools) > Connect Botpress to OpenClaw with ClawLink: paste your Botpress key once and 53 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/botpress The usual route to Botpress 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 Botpress setup: install one ClawHub skill, connect Botpress in the browser, and OpenClaw can call real Botpress 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 Botpress. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Botpress** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask OpenClaw in plain English. **Paste this into OpenClaw to set up ClawLink:** > I want to connect my apps to OpenClaw through ClawLink. > Please install the ClawLink plugin from ClawHub and enable it: `openclaw plugins install clawhub:clawlink-plugin` > When it is installed, tell me and stop. After I reply, give me the ClawLink pairing link. Setup notes, if you need them: https://claw-link.dev/skill.md **Alternative for any agent (no plugin needed):** if the OpenClaw plugin route isn't available or doesn't work, any AI agent with shell access can use the ClawLink CLI instead: ```bash npx -y @useclawlink/cli login # sign in via browser — no API key to paste npx -y @useclawlink/cli connect botpress # connect Botpress (browser OAuth) npx -y @useclawlink/cli actions botpress # list available actions npx -y @useclawlink/cli run botpress --input '' # execute (add --confirm for writes) ``` ### 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: ```bash openclaw plugins install clawhub:clawlink-plugin ``` Then 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 Botpress in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Botpress API key once. Verify the connection by asking OpenClaw: > Use Botpress to break down workspace usage by bot and walk me through the result in plain English. ### 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: ```bash npx -y @useclawlink/cli login ``` `login` opens the same browser approval and stores a credential locally. Once Botpress is connected in the dashboard, that agent calls the same 53 Botpress tools over MCP. Full setup for MCP clients and shell agents: [connect apps to any AI agent](https://claw-link.dev/learn/connect-apps-to-any-ai-agent). ## Botpress MCP for OpenClaw Looking for a Botpress MCP server for OpenClaw? ClawLink connects Botpress to OpenClaw and exposes 53 Botpress tools your agent can call over [MCP](https://claw-link.dev/learn/what-is-an-mcp-server), with [hosted auth](https://claw-link.dev/learn/oauth-for-ai-agents) and nothing to run or maintain yourself. Using Hermes instead? The [Hermes Botpress integration](https://claw-link.dev/hermes/botpress) works the same way. ## What the OpenClaw Botpress integration can do 53 Botpress tools are ready for OpenClaw once the account is connected. The 30 below are the ones people reach for most; your agent can call all 53. ### 30 of 53 Botpress tools for OpenClaw | Tool | What it does | |---|---| | **Break down workspace usage by bot** `botpress_break_down_workspace_usage_by_bot` | Break down workspace usage by bot | | **Check handle availability** `botpress_check_handle_availability` | Check if a workspace handle is available in Botpress | | **Get account** `botpress_get_account` | Get details of the authenticated account | | **Get account preference** `botpress_get_account_preference` | Get a preference of the account | | **Get all workspace quota completion** `botpress_get_all_workspace_quota_completion` | Get a map of workspace IDs to their highest quota completion rate | | **Get dereferenced public plugin by ID** `botpress_get_dereferenced_public_plugin_by_id` | Get a public plugin by ID with all interface entity references resolved to the corresponding | | **Get integration** `botpress_get_integration` | Get a specific Botpress integration by name and version | | **Get public integration** `botpress_get_public_integration` | Retrieve a public integration by name and version from the Botpress hub | | **Get public integration by ID** `botpress_get_public_integration_by_id` | Retrieve detailed information about a public Botpress integration by its ID | | **Get public interface** `botpress_get_public_interface` | Get a public interface by name and version from the Botpress Hub | | **Get public interface by ID** `botpress_get_public_interface_by_id` | Retrieve a public interface by its ID from the Botpress Hub | | **Get public plugin** `botpress_get_public_plugin` | Retrieve detailed information about a public plugin from Botpress Hub by name and version | | **Get public plugin by ID** `botpress_get_public_plugin_by_id` | Retrieve details of a public plugin by its unique ID | | **Get public plugin code** `botpress_get_public_plugin_code` | Retrieve public plugin code from Botpress Hub | | **Get table row** `botpress_get_table_row` | Fetch a specific row from a table using the row's unique identifier | | **Get upcoming invoice** `botpress_get_upcoming_invoice` | Get the upcoming invoice for a workspace | | **Get workspace** `botpress_get_workspace` | Get detailed information about a specific Botpress workspace by ID | | **Get workspace quota** `botpress_get_workspace_quota` | Get workspace quota information for a specific usage type | | **List action runs** `botpress_list_action_runs` | List action runs for a specific integration of a bot | | **List bot issues** `botpress_list_bot_issues` | List issues associated with a specific bot | | **List conversations** `botpress_list_conversations` | List all Conversations | | **List file tag values** `botpress_list_file_tag_values` | List all values for a given file tag across all files | | **List file tags** `botpress_list_file_tags` | List all tags used across all bot files | | **List hub integrations** `botpress_list_hub_integrations` | List public integrations from the Botpress hub | | **List integration API keys** `botpress_list_integration_api_keys` | List Integration API Keys (IAKs) for a specific integration | | **List integrations** `botpress_list_integrations` | List integrations with filtering and sorting capabilities | | **List knowledge bases** `botpress_list_knowledge_bases` | List knowledge bases for a bot | | **List plugins** `botpress_list_plugins` | List Botpress plugins | | **List public interfaces** `botpress_list_public_interfaces` | Retrieve a list of public interfaces available in the Botpress Hub | | **List public plugins** `botpress_list_public_plugins` | Retrieve a list of public plugins available in the Botpress hub | ## Example prompts **Break Down Workspace Usage By Bot** > Use Botpress to break down workspace usage by bot and walk me through the result in plain English. **Check Handle Availability** > Use Botpress to check handle availability and walk me through the result in plain English. **Get Account** > Pull the relevant data from Botpress, summarize it in plain English, and point out anything that needs attention. **Get Account Preference** > Pull the relevant data from Botpress, 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 Botpress working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Botpress API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Botpress 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 Botpress. | 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 Botpress actions to the runtime in a format your agent can reliably use. | 53 tools for Botpress are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Botpress 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 Botpress in the browser, and the 53 tools above work from chat. There is no SDK and no config file, and the Botpress key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full [Composio alternatives](https://claw-link.dev/hub/composio-alternatives) comparison. ### OpenClaw installed the Botpress skill but can't call the tools The ClawHub skill teaches OpenClaw about Botpress, but the calls run through the ClawLink plugin and your connected account. Make sure Botpress 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 Botpress 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 Botpress tools Botpress 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 Botpress 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. ### Botpress 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 Botpress has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Botpress integration? Yes. ClawLink is the fastest way to connect OpenClaw to Botpress: link your Botpress account once in the browser and OpenClaw can call the Botpress API through 53 ready-made tools — no custom code or token handling. ### How do I add Botpress to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Botpress skill from ClawHub, then you click Connect in the dashboard to authorize Botpress. OpenClaw calls the tools from the next message — no config files, and the Botpress key you paste is stored server-side instead of in your environment. ### How long does it take to connect Botpress to OpenClaw? About two minutes. Sign in, click Connect next to Botpress in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Botpress 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 Botpress working from chat. ### OpenClaw installed the Botpress skill but can't call the tools The ClawHub skill teaches OpenClaw about Botpress, but the calls run through the ClawLink plugin and your connected account. Make sure Botpress 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. ## Related - [Connect DataRobot](https://claw-link.dev/openclaw/datarobot) — DataRobot is a machine learning platform that automates model building, deployment, and monitoring, enabling organizations to derive predictive insights from large datasets. - [Chatbotkit tools](https://claw-link.dev/openclaw/chatbotkit) — ChatBotKit is a platform that enables developers to build and manage AI-powered chatbots, offering comprehensive APIs and SDKs for seamless integration into applications. - [Just One API tools](https://claw-link.dev/openclaw/just-one-api) — Just One API provides unified access to public social media, creator, entertainment, and ecommerce data across hundreds of metered endpoints.