# How to connect Plivo to OpenClaw (paste one key, 6 tools) > Connect Plivo to OpenClaw with ClawLink: paste your Plivo key once and 6 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/plivo The usual route to Plivo 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 Plivo setup: install one ClawHub skill, connect Plivo in the browser, and OpenClaw can call real Plivo 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 Plivo. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Plivo** — 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 plivo # connect Plivo (browser OAuth) npx -y @useclawlink/cli actions plivo # list available actions npx -y @useclawlink/cli run plivo --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 Plivo in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Plivo API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from Plivo, 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 Plivo is connected in the dashboard, that agent calls the same 6 Plivo 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). ## Plivo MCP for OpenClaw Looking for a Plivo MCP server for OpenClaw? ClawLink connects Plivo to OpenClaw and exposes 6 Plivo 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 Plivo integration](https://claw-link.dev/hermes/plivo) works the same way. ## What the OpenClaw Plivo integration can do 6 Plivo tools are ready for OpenClaw once the account is connected. ### All 6 Plivo tools for OpenClaw | Tool | What it does | |---|---| | **Get account details** `plivo_get_account_details` | Return billing, credit, timezone, and account-type details for the connected Plivo account | | **Get message** `plivo_get_message` | Retrieve one existing Plivo message by its message UUID, including delivery, routing, timing | | **Get usage summary** `plivo_get_usage_summary` | Return one page of Plivo spend and usage grouped by hour, day, month, or year for a required | | **List calls** `plivo_list_calls` | Return one page of Plivo call history, optionally filtered by time, direction, status | | **List messages** `plivo_list_messages` | Return one page of inbound and outbound Plivo message history, optionally filtered by time | | **List owned numbers** `plivo_list_owned_numbers` | Return one page of phone numbers currently owned by the connected Plivo account, optionally | ## Example prompts **Get Account Details** > Pull the relevant data from Plivo, summarize it in plain English, and point out anything that needs attention. **Get Message** > Pull the relevant data from Plivo, summarize it in plain English, and point out anything that needs attention. **Get Usage Summary** > Pull the relevant data from Plivo, summarize it in plain English, and point out anything that needs attention. **List Calls** > List the relevant items in Plivo, 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 Plivo working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Plivo API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Plivo 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 Plivo. | 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 Plivo actions to the runtime in a format your agent can reliably use. | 6 tools for Plivo are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Plivo 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 Plivo in the browser, and the 6 tools above work from chat. There is no SDK and no config file, and the Plivo 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 Plivo skill but can't call the tools The ClawHub skill teaches OpenClaw about Plivo, but the calls run through the ClawLink plugin and your connected account. Make sure Plivo 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 Plivo 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 Plivo tools Plivo 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 Plivo 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. ### Plivo 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 Plivo has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Plivo integration? Yes. ClawLink is the fastest way to connect OpenClaw to Plivo: link your Plivo account once in the browser and OpenClaw can call the Plivo API through 6 ready-made tools — no custom code or token handling. ### How do I add Plivo to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Plivo skill from ClawHub, then you click Connect in the dashboard to authorize Plivo. OpenClaw calls the tools from the next message — no config files, and the Plivo key you paste is stored server-side instead of in your environment. ### How long does it take to connect Plivo to OpenClaw? About two minutes. Sign in, click Connect next to Plivo in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Plivo 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 Plivo working from chat. ### OpenClaw installed the Plivo skill but can't call the tools The ClawHub skill teaches OpenClaw about Plivo, but the calls run through the ClawLink plugin and your connected account. Make sure Plivo 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 SendGrid integration](https://claw-link.dev/openclaw/sendgrid) — Deliver transactional and marketing emails - [OpenClaw Dialpad integration](https://claw-link.dev/openclaw/dialpad) — Business phone, messaging, and video conferencing - [Discord Bot](https://claw-link.dev/openclaw/discord-bot) — Automate Discord server actions with bot-specific permissions