How to connect Dialpad to Hermes Agent

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.

Reconnect Dialpad from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded.

Dialpad 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 Dialpad 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.

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.

The AI Overview's answer names the causes precisely, and the old card said them without the names: a missing scope for the endpoint (calls:list, recordings_export, message_content_export are the ones it lists), a user-level key where a Company Admin key is required, and a token that needs regenerating. On a hosted OAuth connection the token-regenerate advice translates to reauthorizing from the dashboard, which re-issues the grant with the current scope set, and the company-admin distinction means a connection approved by a user without admin rights fails company-level endpoints no matter how healthy it looks. The hosted-flow cause still applies on top: a placeholder id, a call id from documentation instead of from the call list tools, which Dialpad answers like a permission error because the object is not in the connection's scope.

Ask the agent to diagnose it:

Call dialpad_fetch_call_by_id for <id> and quote the exact error, including any scope name it mentions. Then tell me which Dialpad account and role approved this connection. Do not retry it yet.

Dialpad rate-limits per company, with endpoint-specific ceilings, and an agent walking many call ids in one loop is the traffic shape that meets it: each id is a separate call, and a few hundred of them back to back hit the company ceiling quickly. The response is not to retry immediately but to change the shape of the work: summarise the calls you already have before fetching more, and have the agent report its call count as it goes. If a bulk analysis is genuinely needed, running it in stages across a few turns is more reliable than one sweep.

Ask the agent to diagnose it:

Tell me how many Dialpad calls you have made in the last minute and which endpoints they hit. Quote any rate-limit headers from the last response. Do not call Dialpad again until I reply.

The fixes search results teach for this symptom are about a local MCP server that does not exist here: the hyphen-versus-underscore naming fix applies to a configured server's tool names, and the AIO's fallback, use a third-party bridge because the official MCP is sales-gated, is the problem this page already solves. Two hosted-flow causes cover it instead: schemas load on demand, so the opening Dialpad call in a fresh session can arrive before the catalog and needs one retry, and if Hermes shows no Dialpad tools at all the pairing is incomplete, so confirm the plugin was installed with --enable and that both hermes clawlink begin and hermes clawlink finish ran.

Ask the agent to diagnose it:

List the Dialpad tools you actually have access to. If there are none, retry once and tell me whether the second call worked, then confirm whether `hermes clawlink test` passes.

Try reconnecting Dialpad and complete the consent flow in the same browser session. Partial OAuth approvals or switching accounts mid-flow can leave the connection incomplete.

Yes. ClawLink is the fastest way to connect Hermes to Dialpad: link your Dialpad account once in the browser and Hermes Agent can call the Dialpad API through 192 ready-made tools — no custom code or token handling.

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 Dialpad in the dashboard and Hermes can use it from the next message — no config files or API keys to manage.

About two minutes. Sign in, click Connect next to Dialpad in the dashboard, authenticate, and Hermes Agent can use it from the next chat message.

The alternative to ClawLink is usually manual OAuth app 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 Dialpad working from chat.

Yes. dialpad.com/mcp is a marketing page whose only forward paths are "Talk to Sales" and "Request a demo", and Google's AI Overview states it on two different queries, telling searchers to use Composio or Zapier MCP instead because there is no self-serve official endpoint. That makes this page the self-serve alternative: hosted OAuth, 192 tools, no sales conversation and no public endpoint to configure. If Dialpad ships a public MCP endpoint later, this comparison changes, but as of this run the sales gate is the fact the engines repeat.

Because this connection is OAuth, not a key. The route the AI Overview teaches for "dialpad api token" is a six-step admin walkthrough: Admin Portal, My Company, Authentication, API Keys, then a Bearer token on every request, and that key carries whatever the admin portal granted it. Here you approve Dialpad's consent screen once and the grant lives server-side: there is no key to generate, no token to rotate by hand, and revoking the connection from the dashboard cuts the agent off immediately. "No API keys" is accurate on this page in a way it is not on most.

The call-data surface is the core: dialpad_fetch_call_by_id, dialpad_fetch_call_transcript_by_id, dialpad_fetch_transcript_url_by_call_id, and dialpad_get_recording_share_link_by_id. Around it sits the org surface: users, offices, departments, call centers, custom IVRs, channels, rooms, deskphones, phone numbers and caller id, labels, subscription contacts, webhooks, access control policies, and scheduled reports, plus dialpad_format_phone_numbers for list hygiene. Most of the 192 tools are reads, which matches how this integration is actually used, an agent answering questions about calls and the org that took them.

The engines' safety answers are "generally safe with guardrails": transcripts, recordings, and SMS are the sensitive surface, least privilege is the taught practice, and the connection should be scoped to the call data the work actually needs. Dialpad's own posture (SOC 2, HIPAA, GDPR, data not used for training) is what the AIO cites. On this connection the grant is revocable from the dashboard, so the practical rule is: connect with the account that should see the calls, and prompt the agent to summarise rather than dump full transcripts into chat.

Because the answer bodies for the Hermes head queries walk searchers through the Composio CLI: install the Dialpad MCP toolkit, authenticate, authorize, and the AIO lists this page second on that query while teaching the competitor's install script. The underlying Dialpad API is the same for both routes; the difference is setup and upkeep, a CLI and a connected MCP endpoint you own versus a pairing handshake and one hosted grant. The pages even cover the same error space, so choose on how much you want to run, not on features.

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.