# How to connect Dialmycalls to OpenClaw (paste one key, 25 tools) > Connect Dialmycalls to OpenClaw with ClawLink: paste your Dialmycalls key once and 25 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/dialmycalls The usual route to Dialmycalls 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 Dialmycalls setup: install one ClawHub skill, connect Dialmycalls in the browser, and OpenClaw can call real Dialmycalls 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 Dialmycalls. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Dialmycalls** — 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 dialmycalls # connect Dialmycalls (browser OAuth) npx -y @useclawlink/cli actions dialmycalls # list available actions npx -y @useclawlink/cli run dialmycalls --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 Dialmycalls in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Dialmycalls API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from Dialmycalls, 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 Dialmycalls is connected in the dashboard, that agent calls the same 25 Dialmycalls 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). ## Dialmycalls MCP for OpenClaw Looking for a Dialmycalls MCP server for OpenClaw? ClawLink connects Dialmycalls to OpenClaw and exposes 25 Dialmycalls 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 Dialmycalls integration](https://claw-link.dev/hermes/dialmycalls) works the same way. ## What the OpenClaw Dialmycalls integration can do 25 Dialmycalls tools are ready for OpenClaw once the account is connected. The 20 below are the ones people reach for most; your agent can call all 25. ### 20 of 25 Dialmycalls tools for OpenClaw | Tool | What it does | |---|---| | **Get access account** `dialmycalls_get_access_account` | Retrieve an access (sub) account by ID | | **Get account** `dialmycalls_get_account` | Retrieve your main account details | | **Get caller ID** `dialmycalls_get_caller_id` | Retrieve a caller ID by ID | | **Get contact** `dialmycalls_get_contact` | Retrieve a contact by its unique ID | | **Get group** `dialmycalls_get_group` | Retrieve a contact group by ID | | **Get recording** `dialmycalls_get_recording` | Retrieve a recording by ID | | **List access accounts** `dialmycalls_list_access_accounts` | List all access (sub) accounts | | **List caller i ds** `dialmycalls_list_caller_i_ds` | List all caller IDs on the account | | **List calls** `dialmycalls_list_calls` | List all call broadcasts on the account | | **List contacts** `dialmycalls_list_contacts` | List all contacts in your contact list | | **List do not contacts** `dialmycalls_list_do_not_contacts` | List all Do Not Contact entries | | **List groups** `dialmycalls_list_groups` | List all contact groups | | **List recordings** `dialmycalls_list_recordings` | List all recordings | | **List texts** `dialmycalls_list_texts` | List all outgoing text broadcasts | | **List vanity numbers** `dialmycalls_list_vanity_numbers` | List all vanity numbers | | **Add access account** `dialmycalls_add_access_account` | Add a new access (sub) account | | **Add contact** `dialmycalls_add_contact` | Add a contact to your contact list | | **Add group** `dialmycalls_add_group` | Add a new contact group | | **Update access account** `dialmycalls_update_access_account` | Update an existing access (sub) account by ID | | **Update caller ID** `dialmycalls_update_caller_id` | Update an existing caller ID by ID | ## Example prompts **Get Access Account** > Pull the relevant data from Dialmycalls, summarize it in plain English, and point out anything that needs attention. **Get Account** > Pull the relevant data from Dialmycalls, summarize it in plain English, and point out anything that needs attention. **Get Caller Id** > Pull the relevant data from Dialmycalls, summarize it in plain English, and point out anything that needs attention. **Get Contact** > Pull the relevant data from Dialmycalls, 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 Dialmycalls working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Dialmycalls API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Dialmycalls 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 Dialmycalls. | 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 Dialmycalls actions to the runtime in a format your agent can reliably use. | 25 tools for Dialmycalls are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Dialmycalls 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 Dialmycalls in the browser, and the 25 tools above work from chat. There is no SDK and no config file, and the Dialmycalls 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 Dialmycalls skill but can't call the tools The ClawHub skill teaches OpenClaw about Dialmycalls, but the calls run through the ClawLink plugin and your connected account. Make sure Dialmycalls 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 Dialmycalls 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 Dialmycalls tools Dialmycalls 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 Dialmycalls 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. ### Dialmycalls 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 Dialmycalls has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Dialmycalls integration? Yes. ClawLink is the fastest way to connect OpenClaw to Dialmycalls: link your Dialmycalls account once in the browser and OpenClaw can call the Dialmycalls API through 25 ready-made tools — no custom code or token handling. ### How do I add Dialmycalls to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Dialmycalls skill from ClawHub, then you click Connect in the dashboard to authorize Dialmycalls. OpenClaw calls the tools from the next message — no config files, and the Dialmycalls key you paste is stored server-side instead of in your environment. ### How long does it take to connect Dialmycalls to OpenClaw? About two minutes. Sign in, click Connect next to Dialmycalls in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Dialmycalls 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 Dialmycalls working from chat. ### OpenClaw installed the Dialmycalls skill but can't call the tools The ClawHub skill teaches OpenClaw about Dialmycalls, but the calls run through the ClawLink plugin and your connected account. Make sure Dialmycalls 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 - [Dialpad](https://claw-link.dev/openclaw/dialpad) — Business phone, messaging, and video conferencing - [Connect Discord Bot](https://claw-link.dev/openclaw/discord-bot) — Automate Discord server actions with bot-specific permissions