# How to connect Callpage to OpenClaw (paste one key, 26 tools) > Connect Callpage to OpenClaw with ClawLink: paste your Callpage key once and 26 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/callpage The usual route to Callpage 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 Callpage setup: install one ClawHub skill, connect Callpage in the browser, and OpenClaw can call real Callpage 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 Callpage. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Callpage** — 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 callpage # connect Callpage (browser OAuth) npx -y @useclawlink/cli actions callpage # list available actions npx -y @useclawlink/cli run callpage --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 Callpage in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Callpage API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from Callpage, 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 Callpage is connected in the dashboard, that agent calls the same 26 Callpage 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). ## Callpage MCP for OpenClaw Looking for a Callpage MCP server for OpenClaw? ClawLink connects Callpage to OpenClaw and exposes 26 Callpage 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 Callpage integration](https://claw-link.dev/hermes/callpage) works the same way. ## What the OpenClaw Callpage integration can do 26 Callpage tools are ready for OpenClaw once the account is connected. The 23 below are the ones people reach for most; your agent can call all 26. ### 23 of 26 Callpage tools for OpenClaw | Tool | What it does | |---|---| | **Get all managers** `callpage_get_all_managers` | Retrieve a list of managers for a specific widget with pagination | | **Get all sms messages** `callpage_get_all_sms_messages` | Retrieve all SMS messages for a widget | | **Get all users** `callpage_get_all_users` | Retrieve a list of all users with pagination | | **Get all voice messages** `callpage_get_all_voice_messages` | Retrieve all voice messages for a widget | | **Get all widgets** `callpage_get_all_widgets` | Retrieve a list of widgets with pagination | | **Get API root** `callpage_get_api_root` | Get the root API greeting | | **Get calls history** `callpage_get_calls_history` | Retrieve calls history with filtering and pagination | | **Get manager** `callpage_get_manager` | Retrieve a specific manager by user_id and widget_id | | **Get manager status statistics** `callpage_get_manager_status_statistics` | Retrieve statistical data about manager statuses | | **Get widget** `callpage_get_widget` | Retrieve details of a specific widget by id | | **Add users to widget** `callpage_add_users_to_widget` | Add users to a widget as managers | | **Create sms message** `callpage_create_sms_message` | Create custom SMS messages for specific widget events | | **Create user** `callpage_create_user` | Create a new user with specified name, phone number, email and role | | **Post create manager** `callpage_post_create_manager` | Create a new manager for a widget | | **Post create voice message** `callpage_post_create_voice_message` | Create a custom voice message for a widget | | **Post create widget** `callpage_post_create_widget` | Create a new widget | | **Post reset sms** `callpage_post_reset_sms` | Reset SMS messages to default for a widget | | **Post reset voice message** `callpage_post_reset_voice_message` | Reset voice messages to default for a widget | | **Post update manager** `callpage_post_update_manager` | Update an existing manager | | **Post update sms** `callpage_post_update_sms` | Update a custom SMS message for a widget | | **Post update user** `callpage_post_update_user` | Update an existing user by ID | | **Post update widget** `callpage_post_update_widget` | Update an existing widget | | **Post widget call or schedule** `callpage_post_widget_call_or_schedule` | Initiate or schedule a call via widget | ## Example prompts **Get All Managers** > Pull the relevant data from Callpage, summarize it in plain English, and point out anything that needs attention. **Get All Sms Messages** > Pull the relevant data from Callpage, summarize it in plain English, and point out anything that needs attention. **Get All Users** > Pull the relevant data from Callpage, summarize it in plain English, and point out anything that needs attention. **Get All Voice Messages** > Pull the relevant data from Callpage, 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 Callpage working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Callpage API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Callpage 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 Callpage. | 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 Callpage actions to the runtime in a format your agent can reliably use. | 26 tools for Callpage are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Callpage 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 Callpage in the browser, and the 26 tools above work from chat. There is no SDK and no config file, and the Callpage 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 Callpage skill but can't call the tools The ClawHub skill teaches OpenClaw about Callpage, but the calls run through the ClawLink plugin and your connected account. Make sure Callpage 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 Callpage 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 Callpage tools Callpage 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 Callpage 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. ### Callpage 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 Callpage has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Callpage integration? Yes. ClawLink is the fastest way to connect OpenClaw to Callpage: link your Callpage account once in the browser and OpenClaw can call the Callpage API through 26 ready-made tools — no custom code or token handling. ### How do I add Callpage to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Callpage skill from ClawHub, then you click Connect in the dashboard to authorize Callpage. OpenClaw calls the tools from the next message — no config files, and the Callpage key you paste is stored server-side instead of in your environment. ### How long does it take to connect Callpage to OpenClaw? About two minutes. Sign in, click Connect next to Callpage in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Callpage 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 Callpage working from chat. ### OpenClaw installed the Callpage skill but can't call the tools The ClawHub skill teaches OpenClaw about Callpage, but the calls run through the ClawLink plugin and your connected account. Make sure Callpage 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 - [HubSpot tools](https://claw-link.dev/openclaw/hubspot) — Manage contacts, deals, and pipelines - [CentralStationCRM](https://claw-link.dev/openclaw/centralstationcrm) — CentralStationCRM is an easy-to-use CRM software focusing on collaboration and long-term customer relationships. - [Salesforce tools](https://claw-link.dev/openclaw/salesforce) — Manage CRM data and workflows