# How to connect Bolna to OpenClaw (paste one key, 33 tools) > Connect Bolna to OpenClaw with ClawLink: paste your Bolna key once and 33 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/bolna The usual route to Bolna 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 Bolna setup: install one ClawHub skill, connect Bolna in the browser, and OpenClaw can call real Bolna 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 Bolna. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Bolna** — 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 bolna # connect Bolna (browser OAuth) npx -y @useclawlink/cli actions bolna # list available actions npx -y @useclawlink/cli run bolna --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 Bolna in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Bolna API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from Bolna, 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 Bolna is connected in the dashboard, that agent calls the same 33 Bolna 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). ## Bolna MCP for OpenClaw Looking for a Bolna MCP server for OpenClaw? ClawLink connects Bolna to OpenClaw and exposes 33 Bolna 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 Bolna integration](https://claw-link.dev/hermes/bolna) works the same way. ## What the OpenClaw Bolna integration can do 33 Bolna 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 33. ### 30 of 33 Bolna tools for OpenClaw | Tool | What it does | |---|---| | **Fetch all batches by agent ID** `bolna_fetch_all_batches_by_agent_id` | Retrieve all batches associated with a specific Bolna Voice AI agent | | **Get all agents** `bolna_get_all_agents` | Retrieve all agents configured in your Bolna account Returns a comprehensive list of all voice | | **Get execution by ID** `bolna_get_execution_by_id` | Retrieve detailed information about a specific phone call execution by its ID | | **Get knowledgebase** `bolna_get_knowledgebase` | Retrieve details of a specific knowledgebase by its ID | | **Get user info** `bolna_get_user_info` | Retrieve information about the authenticated user | | **List agents paginated** `bolna_list_agents_paginated` | Retrieve a paginated list of all agents in your Bolna account | | **List knowledgebases** `bolna_list_knowledgebases` | Retrieve all knowledgebases from your Bolna account | | **List phone numbers** `bolna_list_phone_numbers` | List all phone numbers associated with your Bolna account | | **List providers** `bolna_list_providers` | Retrieve all providers associated with your Bolna account Returns a list of all configured | | **List voices** `bolna_list_voices` | List all available voices that can be utilized for Voice AI agents | | **Retrieve agent by ID** `bolna_retrieve_agent_by_id` | Retrieve complete configuration and details for a specific Bolna voice AI agent by its ID | | **Retrieve agent execution details** `bolna_retrieve_agent_execution_details` | Retrieve detailed information about a specific execution (call/conversation) by an agent | | **Retrieve agent execution status** `bolna_retrieve_agent_execution_status` | Retrieve all executions for a specific agent with pagination and filtering support | | **Retrieve batch details by ID** `bolna_retrieve_batch_details_by_id` | Retrieve comprehensive details about a specific Bolna batch by its ID | | **Retrieve batch execution list** `bolna_retrieve_batch_execution_list` | Retrieve all executions from a specific batch with pagination support | | **Search phone numbers** `bolna_search_phone_numbers` | Search for available phone numbers that can be purchased for Bolna Voice agents | | **Add provider** `bolna_add_provider` | Add a new telephony or voice service provider to your Bolna account | | **Copy agent** `bolna_copy_agent` | Create a duplicate copy of an existing Bolna voice AI agent | | **Create agent** `bolna_create_agent` | Create a new Bolna Voice AI agent using the v2 API | | **Create batch** `bolna_create_batch` | Create a new outbound calling batch by uploading a CSV of contacts to obtain a batch_id | | **Create knowledgebase** `bolna_create_knowledgebase` | Create a new knowledgebase for Voice AI agents to reference during conversations | | **Create template agent** `bolna_create_template_agent` | Create a new Bolna Voice AI agent from a template | | **Import agent** `bolna_import_agent` | Import an existing Bolna voice AI agent by its ID | | **Make a phone call from agent** `bolna_make_a_phone_call_from_agent` | Initiate an outbound phone call using a configured Bolna Voice AI agent | | **Schedule batch by ID** `bolna_schedule_batch_by_id` | Schedule a batch to execute at a specific time | | **Setup inbound call for agent** `bolna_setup_inbound_call_for_agent` | Add agent for inbound calls | | **Update agent** `bolna_update_agent` | Update all settings and configuration of an existing Bolna Voice AI agent using the v2 API | | **Remove provider** `bolna_remove_provider` | Remove a provider from your Bolna account by its key name | | **Stop agent calls** `bolna_stop_agent_calls` | Stop all queued or scheduled calls for a specific Voice AI agent | | **Stop batch by ID** `bolna_stop_batch_by_id` | Stop a running batch by its ID | ## Example prompts **Fetch All Batches By Agent Id** > Pull the relevant data from Bolna, summarize it in plain English, and point out anything that needs attention. **Get All Agents** > Pull the relevant data from Bolna, summarize it in plain English, and point out anything that needs attention. **Get Execution By Id** > Pull the relevant data from Bolna, summarize it in plain English, and point out anything that needs attention. **Get Knowledgebase** > Pull the relevant data from Bolna, 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 Bolna working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Bolna API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Bolna 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 Bolna. | 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 Bolna actions to the runtime in a format your agent can reliably use. | 33 tools for Bolna are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Bolna 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 Bolna in the browser, and the 33 tools above work from chat. There is no SDK and no config file, and the Bolna 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 Bolna skill but can't call the tools The ClawHub skill teaches OpenClaw about Bolna, but the calls run through the ClawLink plugin and your connected account. Make sure Bolna 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 Bolna 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 Bolna tools Bolna 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 Bolna 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. ### Bolna 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 Bolna has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Bolna integration? Yes. ClawLink is the fastest way to connect OpenClaw to Bolna: link your Bolna account once in the browser and OpenClaw can call the Bolna API through 33 ready-made tools — no custom code or token handling. ### How do I add Bolna to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Bolna skill from ClawHub, then you click Connect in the dashboard to authorize Bolna. OpenClaw calls the tools from the next message — no config files, and the Bolna key you paste is stored server-side instead of in your environment. ### How long does it take to connect Bolna to OpenClaw? About two minutes. Sign in, click Connect next to Bolna in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Bolna 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 Bolna working from chat. ### OpenClaw installed the Bolna skill but can't call the tools The ClawHub skill teaches OpenClaw about Bolna, but the calls run through the ClawLink plugin and your connected account. Make sure Bolna 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. - [Connect 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. - [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.