How to connect Botstar to OpenClaw
Connect Botstar to OpenClaw with ClawLink: paste your Botstar key once and 31 tools work from chat. No MCP server to run, nothing stored on your machine.
BotstarAPI KEYMCPBotStar is a comprehensive chatbot platform that enables businesses to design, develop, and train chatbots visually for Messenger and websites.. Once connected, OpenClaw can read and act on Botstar from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Botstar 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 Botstar setup: install one ClawHub skill, connect Botstar in the browser, and OpenClaw can call real Botstar 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 Botstar.
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 Botstar
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Botstar?"
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 Botstar in the ClawLink dashboard — paste your Botstar API key once.
Verify the connection by asking OpenClaw:
Pull the relevant data from Botstar, 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 Botstar is connected in the dashboard, that agent calls the same 31 Botstar tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Botstar MCP for OpenClaw
Looking for a Botstar MCP server for OpenClaw? ClawLink connects Botstar to OpenClaw and exposes 31 Botstar tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Botstar integration works the same way.
What the OpenClaw Botstar integration can do
31 Botstar tools are ready for OpenClaw once the account is connected. The 27 below are the ones people reach for most; your agent can call all 31.
27 of 31 Botstar tools for OpenClaw
| Tool | What it does |
|---|---|
Get bot botstar_get_bot | Get your bot by bot ID |
Get bot app ID botstar_get_bot_app_id | Retrieve the BotStar application ID (appId) |
Get cms entity botstar_get_cms_entity | Get a specific CMS entity by ID |
Get entity item botstar_get_entity_item | Retrieve a specific item from a CMS entity with all field values |
List bot attributes botstar_list_bot_attributes | Get all bot attributes from BotStar |
List bots botstar_list_bots | Get your list of bots |
List cms entities botstar_list_cms_entities | Retrieve all CMS entities for a bot |
List entity items botstar_list_entity_items | Retrieve all entity items with pagination support |
Livechat boot botstar_livechat_boot | Reinitialize the live chat widget with provided data |
Livechat close botstar_livechat_close | Hide the live chat window |
Livechat on close botstar_livechat_on_close | Register a callback when the chat window is closed |
Livechat on open botstar_livechat_on_open | Register a callback when the chat window is opened |
Livechat open botstar_livechat_open | Show the live chat window |
Livechat update botstar_livechat_update | Update user details on the current live chat session |
Webview get parameter botstar_webview_get_parameter | Retrieve a parameter value passed from the BotStar chatbot to the webview |
Webview send response botstar_webview_send_response | Send data from the webview back to the BotStar chatbot |
Create bot botstar_create_bot | Create a new bot in BotStar |
Create bot attribute botstar_create_bot_attribute | Create a new bot attribute in BotStar |
Create cms entity botstar_create_cms_entity | Create a CMS entity in BotStar with a name and optional fields |
Create entity fields botstar_create_entity_fields | Create entity field(s) in BotStar CMS |
Create entity item botstar_create_entity_item | Create a new entity item in BotStar CMS |
Create user attributes botstar_create_user_attributes | Create custom user attributes in BotStar |
Publish bot botstar_publish_bot | Publish a bot to live |
Update bot attribute botstar_update_bot_attribute | Update a bot attribute in BotStar |
Update cms entity botstar_update_cms_entity | Update a CMS entity in BotStar |
Update entity fields botstar_update_entity_fields | Update entity field(s) in BotStar CMS |
Update entity item botstar_update_entity_item | Update a CMS entity item in BotStar |
Try it: find the Botstar tool you need
Browse the 27 Botstar 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 Botstar, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Botstar, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Botstar, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Botstar, 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 Botstar working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Botstar API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Botstar 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 Botstar. | 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 Botstar actions to the runtime in a format your agent can reliably use. | 31 tools for Botstar are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Botstar 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 Botstar in the browser, and the 31 tools above work from chat. There is no SDK and no config file, and the Botstar 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 Botstar skill but can't call the tools
The ClawHub skill teaches OpenClaw about Botstar, but the calls run through the ClawLink plugin and your connected account. Make sure Botstar 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 Botstar 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 Botstar tools
Botstar 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 Botstar 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.
Botstar 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 Botstar 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 Botstar integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Botstar: link your Botstar account once in the browser and OpenClaw can call the Botstar API through 31 ready-made tools — no custom code or token handling.
How do I add Botstar to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Botstar skill from ClawHub, then you click Connect in the dashboard to authorize Botstar. OpenClaw calls the tools from the next message — no config files, and the Botstar key you paste is stored server-side instead of in your environment.
How long does it take to connect Botstar to OpenClaw?
About two minutes. Sign in, click Connect next to Botstar in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring Botstar 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 Botstar working from chat.
OpenClaw installed the Botstar skill but can't call the tools
The ClawHub skill teaches OpenClaw about Botstar, but the calls run through the ClawLink plugin and your connected account. Make sure Botstar 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
DataRobot is a machine learning platform that automates model building, deployment, and monitoring, enabling organizations to derive predictive insights from large datasets.
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
Just One API provides unified access to public social media, creator, entertainment, and ecommerce data across hundreds of metered endpoints.