# How to connect Landbot to OpenClaw (paste one key, 13 tools) > Connect Landbot to OpenClaw with ClawLink: paste your Landbot key once and 13 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/landbot The usual route to Landbot 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 Landbot setup: install one ClawHub skill, connect Landbot in the browser, and OpenClaw can call real Landbot 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 Landbot. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Landbot** — 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 landbot # connect Landbot (browser OAuth) npx -y @useclawlink/cli actions landbot # list available actions npx -y @useclawlink/cli run landbot --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 Landbot in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Landbot API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from Landbot, 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 Landbot is connected in the dashboard, that agent calls the same 13 Landbot 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). ## Landbot MCP for OpenClaw Looking for a Landbot MCP server for OpenClaw? ClawLink connects Landbot to OpenClaw and exposes 13 Landbot 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 Landbot integration](https://claw-link.dev/hermes/landbot) works the same way. ## What the OpenClaw Landbot integration can do 13 Landbot tools are ready for OpenClaw once the account is connected. The 12 below are the ones people reach for most; your agent can call all 13. ### 12 of 13 Landbot tools for OpenClaw | Tool | What it does | |---|---| | **Get brand** `landbot_get_brand` | Retrieve your brand data including contact information and settings | | **List agents** `landbot_list_agents` | Retrieve a list of agents in your Landbot account | | **List bots** `landbot_list_bots` | List all bots in your Landbot account | | **List channels** `landbot_list_channels` | List all channels integrated with your account | | **List customers** `landbot_list_customers` | List customers who have interacted with your bot | | **List whatsapp templates** `landbot_list_whatsapp_templates` | List all WhatsApp message templates available for the account | | **Replace agent** `landbot_replace_agent` | Replace all data for a specific agent (full update) | | **Replace brand** `landbot_replace_brand` | Replace or update brand data with a full update (PUT operation) | | **Send message** `landbot_send_message` | Send a plain text outbound message to a Landbot customer | | **Set agent status** `landbot_set_agent_status` | Change your agent status to online, offline, or busy | | **Update agent** `landbot_update_agent` | Update an agent's information in your Landbot account | | **Update brand** `landbot_update_brand` | Partially update your brand data in Landbot | ## Example prompts **Get Brand** > Pull the relevant data from Landbot, summarize it in plain English, and point out anything that needs attention. **List Agents** > List the relevant items in Landbot, group them by priority, and recommend what OpenClaw should do next. **List Bots** > List the relevant items in Landbot, group them by priority, and recommend what OpenClaw should do next. **List Channels** > List the relevant items in Landbot, 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 Landbot working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Landbot API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Landbot 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 Landbot. | 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 Landbot actions to the runtime in a format your agent can reliably use. | 13 tools for Landbot are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Landbot 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 Landbot in the browser, and the 13 tools above work from chat. There is no SDK and no config file, and the Landbot 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 Landbot skill but can't call the tools The ClawHub skill teaches OpenClaw about Landbot, but the calls run through the ClawLink plugin and your connected account. Make sure Landbot 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 Landbot 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 Landbot tools Landbot 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 Landbot 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. ### Landbot 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 Landbot has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Landbot integration? Yes. ClawLink is the fastest way to connect OpenClaw to Landbot: link your Landbot account once in the browser and OpenClaw can call the Landbot API through 13 ready-made tools — no custom code or token handling. ### How do I add Landbot to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Landbot skill from ClawHub, then you click Connect in the dashboard to authorize Landbot. OpenClaw calls the tools from the next message — no config files, and the Landbot key you paste is stored server-side instead of in your environment. ### How long does it take to connect Landbot to OpenClaw? About two minutes. Sign in, click Connect next to Landbot in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Landbot 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 Landbot working from chat. ### OpenClaw installed the Landbot skill but can't call the tools The ClawHub skill teaches OpenClaw about Landbot, but the calls run through the ClawLink plugin and your connected account. Make sure Landbot 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 - [OpenClaw DataRobot integration](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.