# How to connect Telnyx to Hermes Agent (paste one key, 30 tools) > Connect Telnyx to Hermes with ClawLink: paste your Telnyx key once and 30 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/hermes/telnyx Most guides for giving Hermes Agent Telnyx 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 Telnyx setup: pair once in the browser and your always-on Hermes agent can act on Telnyx 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 Telnyx. 1. **Install ClawLink** — add the plugin to Hermes Agent once. 2. **Connect Telnyx** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask Hermes Agent in plain English. **Paste this into Hermes to set up ClawLink:** > Set up ClawLink for Hermes and tell me when it's ready. > 1. Install the plugin: `hermes plugins install ClawLink-HQ/hermes-plugin --enable` > 2. Start pairing with `hermes clawlink begin`. It prints an approval link, so show me the link and stop, don't wait. > 3. I'll approve it in my browser, then reply "approved". > 4. When I say approved, finish setup: `hermes clawlink finish` > 5. Then run `hermes clawlink test` and tell me whether ClawLink is ready. **Alternative for any agent (no plugin needed):** if the Hermes Agent 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 telnyx # connect Telnyx (browser OAuth) npx -y @useclawlink/cli actions telnyx # list available actions npx -y @useclawlink/cli run telnyx --input '' # execute (add --confirm for writes) ``` ### Install by command The prompt above walks Hermes through this. By hand, it is four commands and a browser approval: ```bash 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 test ``` Then connect Telnyx in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Telnyx API key once. Verify the connection by asking Hermes: > Pull the relevant data from Telnyx, 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: ```bash npx -y @useclawlink/cli login ``` `login` opens the same browser approval and stores a credential locally. Once Telnyx is connected in the dashboard, that agent calls the same 30 Telnyx 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). ## Telnyx MCP for Hermes Looking for a Telnyx MCP server for Hermes Agent? ClawLink connects Telnyx to Hermes Agent and exposes 30 Telnyx 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 OpenClaw instead? The [OpenClaw Telnyx integration](https://claw-link.dev/openclaw/telnyx) works the same way. ## What the Hermes Agent Telnyx integration can do 30 Telnyx tools are ready for Hermes Agent once the account is connected. The 26 below are the ones people reach for most; your agent can call all 30. ### 26 of 30 Telnyx tools for Hermes | Tool | What it does | |---|---| | **Get black box test results** `telnyx_get_black_box_test_results` | Retrieve black box test results from Telnyx SETI Observability | | **Get user balance** `telnyx_get_user_balance` | Retrieve the current user account balance and credit details | | **List audit logs** `telnyx_list_audit_logs` | Retrieve a list of audit log entries for your account | | **List connections** `telnyx_list_connections` | Retrieve all connections in your account | | **List dynamic emergency endpoints** `telnyx_list_dynamic_emergency_endpoints` | List dynamic emergency endpoints | | **List global ip health check types** `telnyx_list_global_ip_health_check_types` | List all available global IP health check types | | **List messaging profiles** `telnyx_list_messaging_profiles` | List messaging profiles | | **List messaging URL domains** `telnyx_list_messaging_url_domains` | List configured messaging URL domains | | **List mobile network operators** `telnyx_list_mobile_network_operators` | List available mobile network operators | | **List network interfaces** `telnyx_list_network_interfaces` | List all network interfaces for a specified network | | **List networks** `telnyx_list_networks` | List all networks in your account | | **List notification channels** `telnyx_list_notification_channels` | List all notification channels | | **List notification event conditions** `telnyx_list_notification_event_conditions` | List all notification event conditions | | **List notification events** `telnyx_list_notification_events` | List all notification events with their IDs | | **List notification profiles** `telnyx_list_notification_profiles` | List all notification profiles | | **List phone numbers** `telnyx_list_phone_numbers` | List phone numbers associated with your account | | **List sso authentication providers** `telnyx_list_sso_authentication_providers` | Retrieve all configured SSO authentication providers | | **Retrieve network** `telnyx_retrieve_network` | Retrieve details of a specific network by ID | | **Retrieve notification channel** `telnyx_retrieve_notification_channel` | Retrieve a notification channel by ID | | **Retrieve notification profile** `telnyx_retrieve_notification_profile` | Retrieve a notification profile by ID | | **Retrieve notification setting** `telnyx_retrieve_notification_setting` | Retrieve a notification setting by ID | | **Create network** `telnyx_create_network` | Create a new network | | **Create notification channel** `telnyx_create_notification_channel` | Create a notification channel | | **Create notification profile** `telnyx_create_notification_profile` | Create a notification profile | | **Create notification setting** `telnyx_create_notification_setting` | Add a notification setting | | **Update network** `telnyx_update_network` | Update details of an existing network | ## Example prompts **Get Black Box Test Results** > Pull the relevant data from Telnyx, summarize it in plain English, and point out anything that needs attention. **Get User Balance** > Pull the relevant data from Telnyx, summarize it in plain English, and point out anything that needs attention. **List Audit Logs** > List the relevant items in Telnyx, group them by priority, and recommend what Hermes should do next. **List Connections** > List the relevant items in Telnyx, group them by priority, and recommend what Hermes should do next. ## 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 Telnyx working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Telnyx API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Telnyx 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 Telnyx. | 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 Telnyx actions to the runtime in a format your agent can reliably use. | 30 tools for Telnyx are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Telnyx 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 Telnyx in the browser, and the 30 tools above work from chat. There is no SDK and no config file, and the Telnyx 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. ### Hermes paired but still can't use Telnyx 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 Telnyx 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 Telnyx tools Telnyx 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 Telnyx 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. ### Telnyx 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 Telnyx has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a Hermes Agent Telnyx integration? Yes. ClawLink is the fastest way to connect Hermes to Telnyx: link your Telnyx account once in the browser and Hermes Agent can call the Telnyx API through 30 ready-made tools — no custom code or token handling. ### How do I connect Telnyx 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 Telnyx in the dashboard and Hermes can use it from the next message — no config files, and the Telnyx key you paste is stored server-side instead of in your environment. ### How long does it take to connect Telnyx to Hermes Agent? About two minutes. Sign in, click Connect next to Telnyx in the dashboard, authenticate, and Hermes Agent can use it from the next chat message. ### Why use ClawLink instead of wiring Telnyx 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 Telnyx working from chat. ### Hermes paired but still can't use Telnyx 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`. ## Related - [SendGrid](https://claw-link.dev/hermes/sendgrid) — Deliver transactional and marketing emails - [Hermes Dialpad integration](https://claw-link.dev/hermes/dialpad) — Business phone, messaging, and video conferencing - [Discord Bot](https://claw-link.dev/hermes/discord-bot) — Automate Discord server actions with bot-specific permissions