# How to connect Callerapi to OpenClaw (paste one key, 7 tools) > Connect Callerapi to OpenClaw with ClawLink: paste your Callerapi key once and 7 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/callerapi The usual route to Callerapi 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 Callerapi setup: install one ClawHub skill, connect Callerapi in the browser, and OpenClaw can call real Callerapi 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 Callerapi. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Callerapi** — 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 callerapi # connect Callerapi (browser OAuth) npx -y @useclawlink/cli actions callerapi # list available actions npx -y @useclawlink/cli run callerapi --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 Callerapi in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Callerapi API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from Callerapi, 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 Callerapi is connected in the dashboard, that agent calls the same 7 Callerapi 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). ## Callerapi MCP for OpenClaw Looking for a Callerapi MCP server for OpenClaw? ClawLink connects Callerapi to OpenClaw and exposes 7 Callerapi 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 Callerapi integration](https://claw-link.dev/hermes/callerapi) works the same way. ## What the OpenClaw Callerapi integration can do 7 Callerapi tools are ready for OpenClaw once the account is connected. ### All 7 Callerapi tools for OpenClaw | Tool | What it does | |---|---| | **Get phone number information** `callerapi_get_phone_number_information` | Retrieve detailed information about a specific phone number, including reputation, business and | | **Get user information** `callerapi_get_user_information` | Retrieve information about the authenticated user, including email and credit usage details | | **List webhook subscriptions** `callerapi_list_webhook_subscriptions` | List all webhook subscriptions for daily spam reports | | **Test webhook** `callerapi_test_webhook` | Send a sample webhook payload to test your webhook endpoint integration | | **Dispatch reports manually** `callerapi_dispatch_reports_manually` | Manually trigger today's spam reports webhook delivery for enterprise clients | | **Subscribe daily reports** `callerapi_subscribe_daily_reports` | Subscribe to daily spam report webhooks for enterprise clients | | **Unsubscribe daily reports** `callerapi_unsubscribe_daily_reports` | Unsubscribe from daily spam report webhooks | ## Example prompts **Get Phone Number Information** > Pull the relevant data from Callerapi, summarize it in plain English, and point out anything that needs attention. **Get User Information** > Pull the relevant data from Callerapi, summarize it in plain English, and point out anything that needs attention. **List Webhook Subscriptions** > List the relevant items in Callerapi, group them by priority, and recommend what OpenClaw should do next. **Test Webhook** > Use Callerapi to test webhook and walk me through the result in plain English. ## 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 Callerapi working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Callerapi API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Callerapi 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 Callerapi. | 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 Callerapi actions to the runtime in a format your agent can reliably use. | 7 tools for Callerapi are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Callerapi 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 Callerapi in the browser, and the 7 tools above work from chat. There is no SDK and no config file, and the Callerapi 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 Callerapi skill but can't call the tools The ClawHub skill teaches OpenClaw about Callerapi, but the calls run through the ClawLink plugin and your connected account. Make sure Callerapi 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 Callerapi 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 Callerapi tools Callerapi 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 Callerapi 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. ### Callerapi 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 Callerapi has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Callerapi integration? Yes. ClawLink is the fastest way to connect OpenClaw to Callerapi: link your Callerapi account once in the browser and OpenClaw can call the Callerapi API through 7 ready-made tools — no custom code or token handling. ### How do I add Callerapi to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Callerapi skill from ClawHub, then you click Connect in the dashboard to authorize Callerapi. OpenClaw calls the tools from the next message — no config files, and the Callerapi key you paste is stored server-side instead of in your environment. ### How long does it take to connect Callerapi to OpenClaw? About two minutes. Sign in, click Connect next to Callerapi in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Callerapi 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 Callerapi working from chat. ### OpenClaw installed the Callerapi skill but can't call the tools The ClawHub skill teaches OpenClaw about Callerapi, but the calls run through the ClawLink plugin and your connected account. Make sure Callerapi 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 - [SendGrid](https://claw-link.dev/openclaw/sendgrid) — Deliver transactional and marketing emails - [Connect Dialpad](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