# How to connect BotMape to OpenClaw (paste one key, 8 tools) > Connect BotMape to OpenClaw with ClawLink: paste your BotMape key once and 8 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/botmape The usual route to BotMape 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 BotMape setup: install one ClawHub skill, connect BotMape in the browser, and OpenClaw can call real BotMape 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 BotMape. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect BotMape** — 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 botmape # connect BotMape (browser OAuth) npx -y @useclawlink/cli actions botmape # list available actions npx -y @useclawlink/cli run botmape --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 BotMape in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your BotMape API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from BotMape, 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: ```bash npx -y @useclawlink/cli login ``` `login` opens the same browser approval and stores a credential locally. Once BotMape is connected in the dashboard, that agent calls the same 8 BotMape 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). ## BotMape MCP for OpenClaw Looking for a BotMape MCP server for OpenClaw? ClawLink connects BotMape to OpenClaw and exposes 8 BotMape 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 BotMape integration](https://claw-link.dev/hermes/botmape) works the same way. ## What the OpenClaw BotMape integration can do 8 BotMape tools are ready for OpenClaw once the account is connected. The 7 below are the ones people reach for most; your agent can call all 8. ### 7 of 8 BotMape tools for OpenClaw | Tool | What it does | |---|---| | **Get AI agent** `botmape_get_ai_agent` | Return the detailed configuration, behavior prompt, appearance, and active state of one AI | | **Get platform analytics** `botmape_get_platform_analytics` | Return account-wide BotMape message and conversation totals, daily activity, averages, and | | **List AI agents** `botmape_list_ai_agents` | Return all AI agents owned by the connected BotMape account, including the IDs needed by | | **List knowledge entries** `botmape_list_knowledge_entries` | Return all knowledge-base entries currently attached to one AI agent, including entry IDs | | **Add knowledge** `botmape_add_knowledge` | Add and automatically embed training content in one AI agent's knowledge base, optionally with | | **Create AI agent** `botmape_create_ai_agent` | Permanently create a BotMape AI agent | | **Send message to AI agent** `botmape_send_message_to_ai_agent` | Immediately send a visitor message to an AI agent, creating a conversation or continuing the | ## Example prompts **Get Ai Agent** > Pull the relevant data from BotMape, summarize it in plain English, and point out anything that needs attention. **Get Platform Analytics** > Pull the relevant data from BotMape, summarize it in plain English, and point out anything that needs attention. **List Ai Agents** > List the relevant items in BotMape, group them by priority, and recommend what OpenClaw should do next. **List Knowledge Entries** > List the relevant items in BotMape, 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 BotMape working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the BotMape API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected BotMape 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 BotMape. | 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 BotMape actions to the runtime in a format your agent can reliably use. | 8 tools for BotMape are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes BotMape 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 BotMape in the browser, and the 8 tools above work from chat. There is no SDK and no config file, and the BotMape 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 BotMape skill but can't call the tools The ClawHub skill teaches OpenClaw about BotMape, but the calls run through the ClawLink plugin and your connected account. Make sure BotMape 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 BotMape 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 BotMape tools BotMape 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 BotMape 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. ### BotMape 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 BotMape has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw BotMape integration? Yes. ClawLink is the fastest way to connect OpenClaw to BotMape: link your BotMape account once in the browser and OpenClaw can call the BotMape API through 8 ready-made tools — no custom code or token handling. ### How do I add BotMape to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink BotMape skill from ClawHub, then you click Connect in the dashboard to authorize BotMape. OpenClaw calls the tools from the next message — no config files, and the BotMape key you paste is stored server-side instead of in your environment. ### How long does it take to connect BotMape to OpenClaw? About two minutes. Sign in, click Connect next to BotMape in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring BotMape 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 BotMape working from chat. ### OpenClaw installed the BotMape skill but can't call the tools The ClawHub skill teaches OpenClaw about BotMape, but the calls run through the ClawLink plugin and your connected account. Make sure BotMape 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 - [DataRobot tools](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. - [OpenClaw Chatbotkit integration](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. - [OpenClaw Just One API integration](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.