# How to connect Callingly to OpenClaw (paste one key, 29 tools) > Connect Callingly to OpenClaw with ClawLink: paste your Callingly key once and 29 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/callingly The usual route to Callingly 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 Callingly setup: install one ClawHub skill, connect Callingly in the browser, and OpenClaw can call real Callingly 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 Callingly. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Callingly** — 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 callingly # connect Callingly (browser OAuth) npx -y @useclawlink/cli actions callingly # list available actions npx -y @useclawlink/cli run callingly --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 Callingly in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Callingly API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from Callingly, 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 Callingly is connected in the dashboard, that agent calls the same 29 Callingly 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). ## Callingly MCP for OpenClaw Looking for a Callingly MCP server for OpenClaw? ClawLink connects Callingly to OpenClaw and exposes 29 Callingly 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 Callingly integration](https://claw-link.dev/hermes/callingly) works the same way. ## What the OpenClaw Callingly integration can do 29 Callingly tools are ready for OpenClaw once the account is connected. The 25 below are the ones people reach for most; your agent can call all 29. ### 25 of 29 Callingly tools for OpenClaw | Tool | What it does | |---|---| | **Get agent schedule** `callingly_get_agent_schedule` | Retrieve the availability schedule for a specific agent | | **Get call** `callingly_get_call` | Retrieves detailed information about a specific call by its unique ID | | **Get lead** `callingly_get_lead` | Retrieve details of a specific lead by its ID | | **Get team** `callingly_get_team` | Retrieve details of a specific team | | **Get webhook** `callingly_get_webhook` | Retrieve details of a specific webhook by its ID | | **List calls** `callingly_list_calls` | List calls | | **List clients** `callingly_list_clients` | List clients | | **List leads** `callingly_list_leads` | List leads based on provided filters like date range or phone number | | **List team users** `callingly_list_team_users` | Retrieve all agents assigned to a specific team in Callingly | | **List teams** `callingly_list_teams` | List teams | | **List users** `callingly_list_users` | Retrieve a list of agents | | **List webhooks** `callingly_list_webhooks` | List configured webhooks | | **Activate deactivate client** `callingly_activate_deactivate_client` | Activate or deactivate a client account | | **Create agent** `callingly_create_agent` | Create a new agent | | **Create call** `callingly_create_call` | Creates a new outbound call record and initiates a real outbound call, which incurs cost — | | **Create client** `callingly_create_client` | Creates a new client account in Callingly | | **Create team** `callingly_create_team` | Create a new team | | **Create webhook** `callingly_create_webhook` | Create a new webhook for call or lead events | | **Update agent** `callingly_update_agent` | Update an existing agent's details | | **Update lead** `callingly_update_lead` | Update an existing lead's information | | **Update schedule** `callingly_update_schedule` | Update an agent's availability schedule | | **Update team agent settings** `callingly_update_team_agent_settings` | Update settings (priority, capacity) for a specific team agent | | **Update team users** `callingly_update_team_users` | Updates the list of agents assigned to a team | | **Update webhook** `callingly_update_webhook` | Updates an existing webhook's configuration by ID | | **Remove team agent** `callingly_remove_team_agent` | Remove a specific agent from a team | ## Example prompts **Get Agent Schedule** > Pull the relevant data from Callingly, summarize it in plain English, and point out anything that needs attention. **Get Call** > Pull the relevant data from Callingly, summarize it in plain English, and point out anything that needs attention. **Get Lead** > Pull the relevant data from Callingly, summarize it in plain English, and point out anything that needs attention. **Get Team** > Pull the relevant data from Callingly, 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 Callingly working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Callingly API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Callingly 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 Callingly. | 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 Callingly actions to the runtime in a format your agent can reliably use. | 29 tools for Callingly are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Callingly 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 Callingly in the browser, and the 29 tools above work from chat. There is no SDK and no config file, and the Callingly 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 Callingly skill but can't call the tools The ClawHub skill teaches OpenClaw about Callingly, but the calls run through the ClawLink plugin and your connected account. Make sure Callingly 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 Callingly 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 Callingly tools Callingly 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 Callingly 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. ### Callingly 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 Callingly has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Callingly integration? Yes. ClawLink is the fastest way to connect OpenClaw to Callingly: link your Callingly account once in the browser and OpenClaw can call the Callingly API through 29 ready-made tools — no custom code or token handling. ### How do I add Callingly to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Callingly skill from ClawHub, then you click Connect in the dashboard to authorize Callingly. OpenClaw calls the tools from the next message — no config files, and the Callingly key you paste is stored server-side instead of in your environment. ### How long does it take to connect Callingly to OpenClaw? About two minutes. Sign in, click Connect next to Callingly in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Callingly 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 Callingly working from chat. ### OpenClaw installed the Callingly skill but can't call the tools The ClawHub skill teaches OpenClaw about Callingly, but the calls run through the ClawLink plugin and your connected account. Make sure Callingly 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 - [ActiveCampaign](https://claw-link.dev/openclaw/activecampaign) — Marketing automation, CRM, and email marketing - [Benchmark Email tools](https://claw-link.dev/openclaw/benchmark-email) — Benchmark Email is a comprehensive email marketing platform offering tools for creating, sending, and analyzing email campaigns. - [OpenClaw Mailchimp integration](https://claw-link.dev/openclaw/mailchimp) — Create email campaigns and manage audiences