How to connect Dialmycalls to Hermes Agent
Connect Dialmycalls to Hermes with ClawLink: paste your Dialmycalls key once and 25 tools work from chat. No MCP server to run, nothing stored on your machine.
DialmycallsAPI KEYMCPDialMyCalls provides a mass notification system enabling users to send voice and text messages to contacts.. Once connected, Hermes Agent can read and act on Dialmycalls from chat — pairing, token refresh, and tool wiring handled for you.
Most guides for giving Hermes Agent Dialmycalls access start with registering your own OAuth app or pasting API keys into env files, then leave the token refresh and tool wiring to you. ClawLink gives Hermes a more practical Dialmycalls setup: pair once in the browser and your always-on Hermes agent can act on Dialmycalls for you, reading and doing real work on your behalf with no auth, token refresh, or tool wiring to build yourself.
Setup
It takes three steps to connect Hermes to Dialmycalls.
1Install and pair
Install the ClawLink plugin, then pair Hermes with a one-time browser approval:
hermes plugins install ClawLink-HQ/hermes-plugin --enable- 2
Connect Dialmycalls
Paste your API key in the dashboard.
- 3
Use it from chat
Ask Hermes Agent: "What can you do with Dialmycalls?"
Install by command
The prompt above walks Hermes through this. By hand, it is four commands and a browser approval:
hermes plugins install ClawLink-HQ/hermes-plugin --enable
hermes clawlink begin # prints an approval link — open it and approve
hermes clawlink finish # after approving in the browser
hermes clawlink testThen connect Dialmycalls in the ClawLink dashboard — paste your Dialmycalls API key once.
Verify the connection by asking Hermes:
Pull the relevant data from Dialmycalls, summarize it in plain English, and point out anything that needs attention.
Using a different agent?
The Hermes 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:
npx -y @useclawlink/cli loginlogin 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.
Dialmycalls MCP for Hermes
Looking for a Dialmycalls MCP server for Hermes Agent? ClawLink connects Dialmycalls to Hermes Agent and exposes 25 Dialmycalls tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using OpenClaw instead? The OpenClaw Dialmycalls integration works the same way.
What the Hermes Agent Dialmycalls integration can do
25 Dialmycalls tools are ready for Hermes Agent 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 Hermes
| 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 |
Try it: find the Dialmycalls tool you need
Browse the 20 Dialmycalls tools
Click any tool to see exactly what Hermes can do and copy a ready-to-use prompt.
Example prompts
Pull the relevant data from Dialmycalls, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Dialmycalls, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Dialmycalls, summarize it in plain English, and point out anything that needs attention.
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 Hermes Agent. 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 Hermes Agent 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 comparison.
Troubleshooting
Hermes paired but still can't use Dialmycalls
Pairing is a two-step handshake: run hermes clawlink begin, approve the link in your browser, then run hermes clawlink finish. If you ran finish before approving, or the approval link expired, run hermes clawlink begin again to get a fresh link. Confirm the plugin was installed with --enable, then verify with hermes clawlink test.
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.
FAQ
Is there a Hermes Agent Dialmycalls integration?
Yes. ClawLink is the fastest way to connect Hermes to Dialmycalls: link your Dialmycalls account once in the browser and Hermes Agent can call the Dialmycalls API through 25 ready-made tools — no custom code or token handling.
How do I connect Dialmycalls to Hermes with ClawLink?
Install the plugin with hermes plugins install ClawLink-HQ/hermes-plugin --enable, then pair once: run hermes clawlink begin, approve the link in your browser, and run hermes clawlink finish. Connect Dialmycalls in the dashboard and Hermes can use it 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 Hermes Agent?
About two minutes. Sign in, click Connect next to Dialmycalls in the dashboard, authenticate, and Hermes Agent 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 Hermes Agent. That is fine if you want to build and maintain the integration yourself. Most teams just want Dialmycalls working from chat.
Hermes paired but still can't use Dialmycalls
Pairing is a two-step handshake: run hermes clawlink begin, approve the link in your browser, then run hermes clawlink finish. If you ran finish before approving, or the approval link expired, run hermes clawlink begin again to get a fresh link. Confirm the plugin was installed with --enable, then verify with hermes clawlink test.
