# How to connect Bland AI to OpenClaw (paste one key, 10 tools)

> Connect Bland AI to OpenClaw with ClawLink: paste your Bland AI key once and 10 tools work from chat. No MCP server to run, nothing stored on your machine.

Web version: https://claw-link.dev/openclaw/bland-ai

The usual route to Bland AI 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 Bland AI setup: install one ClawHub skill, connect Bland AI in the browser, and OpenClaw can call real Bland AI 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 Bland AI.

1. **Install ClawLink** — add the plugin to OpenClaw once.
2. **Connect Bland AI** — 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 bland-ai  # connect Bland AI (browser OAuth)
npx -y @useclawlink/cli actions bland-ai  # list available actions
npx -y @useclawlink/cli run bland-ai <action> --input '<json>'  # 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 Bland AI in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Bland AI API key once.

Verify the connection by asking OpenClaw:

> Pull the relevant data from Bland AI, 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 Bland AI is connected in the dashboard, that agent calls the same 10 Bland AI 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).

## Bland AI MCP for OpenClaw

Looking for a Bland AI MCP server for OpenClaw? ClawLink connects Bland AI to OpenClaw and exposes 10 Bland AI 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 Bland AI integration](https://claw-link.dev/hermes/bland-ai) works the same way.

## What the OpenClaw Bland AI integration can do

10 Bland AI tools are ready for OpenClaw once the account is connected. The 9 below are the ones people reach for most; your agent can call all 10.

### 9 of 10 Bland AI tools for OpenClaw

| Tool | What it does |
|---|---|
| **Get account details** `bland_ai_get_account_details` | Return the connected Bland AI account's status, call count, balance, and refill settings |
| **List calls** `bland_ai_list_calls` | Search the connected account's existing inbound and outbound call history without placing or |
| **List contacts** `bland_ai_list_contacts` | Return organization contacts and their identifiers and memory records one page at a time |
| **List knowledge bases** `bland_ai_list_knowledge_bases` | Return one page of the connected Bland AI organization's knowledge bases, including processing |
| **List pathway folders** `bland_ai_list_pathway_folders` | Return all pathway folders and their parent relationships from Bland's US regional pathway |
| **List pathways** `bland_ai_list_pathways` | Return all conversational pathways, including their names, descriptions, nodes, and edges |
| **List tools** `bland_ai_list_tools` | Search and page through the active or draft tools configured for Bland agents |
| **Create pathway folder** `bland_ai_create_pathway_folder` | Create an empty pathway folder, optionally nested under an existing folder, without running |
| **Rename pathway folder** `bland_ai_rename_pathway_folder` | Rename an existing pathway folder without moving or changing any pathways inside it |

## Example prompts

**Get Account Details**

> Pull the relevant data from Bland AI, summarize it in plain English, and point out anything that needs attention.

**List Calls**

> List the relevant items in Bland AI, group them by priority, and recommend what OpenClaw should do next.

**List Contacts**

> List the relevant items in Bland AI, group them by priority, and recommend what OpenClaw should do next.

**List Knowledge Bases**

> List the relevant items in Bland AI, 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 Bland AI working from chat.

| | Manual | ClawLink |
|---|---|---|
| **Credential handling** | Collect, validate, store, and rotate the Bland AI API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Bland AI 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 Bland AI. | 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 Bland AI actions to the runtime in a format your agent can reliably use. | 10 tools for Bland AI are already exposed through ClawLink, so the agent can read and act from chat immediately. |

## ClawLink vs. Composio

Composio also exposes Bland AI 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 Bland AI in the browser, and the 10 tools above work from chat. There is no SDK and no config file, and the Bland AI 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 Bland AI skill but can't call the tools
The ClawHub skill teaches OpenClaw about Bland AI, but the calls run through the ClawLink plugin and your connected account. Make sure Bland AI 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 Bland AI 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 Bland AI tools
Bland AI 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 Bland AI 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.

### Bland AI 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 Bland AI has the right scopes or account access. A valid key can still be too limited for some reads or writes.

### Is there a OpenClaw Bland AI integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Bland AI: link your Bland AI account once in the browser and OpenClaw can call the Bland AI API through 10 ready-made tools — no custom code or token handling.

### How do I add Bland AI to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Bland AI skill from ClawHub, then you click Connect in the dashboard to authorize Bland AI. OpenClaw calls the tools from the next message — no config files, and the Bland AI key you paste is stored server-side instead of in your environment.

### How long does it take to connect Bland AI to OpenClaw?
About two minutes. Sign in, click Connect next to Bland AI in the dashboard, authenticate, and OpenClaw can use it from the next chat message.

### Why use ClawLink instead of wiring Bland AI 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 Bland AI working from chat.

### OpenClaw installed the Bland AI skill but can't call the tools
The ClawHub skill teaches OpenClaw about Bland AI, but the calls run through the ClawLink plugin and your connected account. Make sure Bland AI 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.
