# How to connect Botbaba to OpenClaw (paste one key, 42 tools) > Connect Botbaba to OpenClaw with ClawLink: paste your Botbaba key once and 42 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/botbaba The usual route to Botbaba 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 Botbaba setup: install one ClawHub skill, connect Botbaba in the browser, and OpenClaw can call real Botbaba 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 Botbaba. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Botbaba** — 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 botbaba # connect Botbaba (browser OAuth) npx -y @useclawlink/cli actions botbaba # list available actions npx -y @useclawlink/cli run botbaba --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 Botbaba in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Botbaba API key once. Verify the connection by asking OpenClaw: > Use Botbaba to cart creation event simulator 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 Botbaba is connected in the dashboard, that agent calls the same 42 Botbaba 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). ## Botbaba MCP for OpenClaw Looking for a Botbaba MCP server for OpenClaw? ClawLink connects Botbaba to OpenClaw and exposes 42 Botbaba 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 Botbaba integration](https://claw-link.dev/hermes/botbaba) works the same way. ## What the OpenClaw Botbaba integration can do 42 Botbaba 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 42. ### 30 of 42 Botbaba tools for OpenClaw | Tool | What it does | |---|---| | **Cart creation event simulator** `botbaba_cart_creation_event_simulator` | Simulate a Shopify cart creation webhook payload | | **Get bot widget settings** `botbaba_get_bot_widget_settings` | Retrieve widget configuration settings for a bot | | **Get broadcast** `botbaba_get_broadcast` | Retrieve details of a specific broadcast | | **Get contact** `botbaba_get_contact` | Fetch a BotBaba contact by its ID | | **Get contact analytics** `botbaba_get_contact_analytics` | Retrieve analytics data for contacts | | **Get filename** `botbaba_get_filename` | Extract the filename from a file path | | **Get flow** `botbaba_get_flow` | Retrieve details of a specific flow | | **Get message** `botbaba_get_message` | Retrieve status of a specific message | | **Get message analytics** `botbaba_get_message_analytics` | Retrieve analytics data for a specific message | | **Get template** `botbaba_get_template` | Retrieve details of a specific template | | **Get webhook** `botbaba_get_webhook` | Retrieve details of a specific webhook | | **List broadcasts** `botbaba_list_broadcasts` | List all broadcast campaigns | | **List flows** `botbaba_list_flows` | List all conversation flows with their IDs and metadata | | **List tags** `botbaba_list_tags` | List all tags | | **List templates** `botbaba_list_templates` | Retrieve a paginated list of templates | | **List webhook event types** `botbaba_list_webhook_event_types` | List available webhook event types | | **List webhooks** `botbaba_list_webhooks` | List all registered webhooks | | **Order cancellation shopify webhook** `botbaba_order_cancellation_shopify_webhook` | Receive Shopify order cancellation webhooks | | **Order fulfillment event simulator** `botbaba_order_fulfillment_event_simulator` | Simulate a Shopify order fulfillment webhook payload | | **Order fulfillment shopify webhook** `botbaba_order_fulfillment_shopify_webhook` | Receive Shopify Order Fulfillment webhooks | | **Order payment shopify webhook** `botbaba_order_payment_shopify_webhook` | Receive Shopify Order Payment webhooks | | **Shopify checkout creation event simulator** `botbaba_shopify_checkout_creation_event_simulator` | Simulate a Shopify checkout creation webhook payload | | **Shopify checkout update event simulator** `botbaba_shopify_checkout_update_event_simulator` | Simulate a Shopify checkout update webhook payload | | **Wa gupshup event simulator** `botbaba_wa_gupshup_event_simulator` | Simulate Gupshup WhatsApp webhook events | | **Cart creation shopify webhook** `botbaba_cart_creation_shopify_webhook` | Receive Shopify Cart Creation webhooks | | **Cart update shopify webhook** `botbaba_cart_update_shopify_webhook` | Forward Shopify cart update events to BotBaba | | **Checkout creation shopify webhook** `botbaba_checkout_creation_shopify_webhook` | Receive Shopify checkout creation webhook events | | **Checkout update shopify webhook** `botbaba_checkout_update_shopify_webhook` | Forward Shopify checkout/update events to Botbaba | | **Execute bot action** `botbaba_execute_bot_action` | Execute a bot action or workflow | | **Execute bot action by user** `botbaba_execute_bot_action_by_user` | Execute a bot action for specific users | ## Example prompts **Cart Creation Event Simulator** > Use Botbaba to cart creation event simulator and walk me through the result in plain English. **Get Bot Widget Settings** > Pull the relevant data from Botbaba, summarize it in plain English, and point out anything that needs attention. **Get Broadcast** > Pull the relevant data from Botbaba, summarize it in plain English, and point out anything that needs attention. **Get Contact** > Pull the relevant data from Botbaba, 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 Botbaba working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Botbaba API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Botbaba 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 Botbaba. | 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 Botbaba actions to the runtime in a format your agent can reliably use. | 42 tools for Botbaba are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Botbaba 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 Botbaba in the browser, and the 42 tools above work from chat. There is no SDK and no config file, and the Botbaba 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 Botbaba skill but can't call the tools The ClawHub skill teaches OpenClaw about Botbaba, but the calls run through the ClawLink plugin and your connected account. Make sure Botbaba 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 Botbaba 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 Botbaba tools Botbaba 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 Botbaba 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. ### Botbaba 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 Botbaba has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Botbaba integration? Yes. ClawLink is the fastest way to connect OpenClaw to Botbaba: link your Botbaba account once in the browser and OpenClaw can call the Botbaba API through 42 ready-made tools — no custom code or token handling. ### How do I add Botbaba to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Botbaba skill from ClawHub, then you click Connect in the dashboard to authorize Botbaba. OpenClaw calls the tools from the next message — no config files, and the Botbaba key you paste is stored server-side instead of in your environment. ### How long does it take to connect Botbaba to OpenClaw? About two minutes. Sign in, click Connect next to Botbaba in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Botbaba 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 Botbaba working from chat. ### OpenClaw installed the Botbaba skill but can't call the tools The ClawHub skill teaches OpenClaw about Botbaba, but the calls run through the ClawLink plugin and your connected account. Make sure Botbaba 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. - [Chatbotkit](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. - [Connect Just One API](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.