How to connect Spondyr to Hermes Agent
Connect Spondyr to Hermes with ClawLink: paste your Spondyr key once and 21 tools work from chat. No MCP server to run, nothing stored on your machine.
SpondyrAPI KEYMCPSpondyr is a correspondence template management and distribution platform that enables developers to quickly integrate template-driven content delivery via API, supporting email, SMS, fax, and postal mail.. Once connected, Hermes Agent can read and act on Spondyr from chat — pairing, token refresh, and tool wiring handled for you.
Most guides for giving Hermes Agent Spondyr 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 Spondyr setup: pair once in the browser and your always-on Hermes agent can act on Spondyr 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 Spondyr.
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 Spondyr
Paste your API key in the dashboard.
- 3
Use it from chat
Ask Hermes Agent: "What can you do with Spondyr?"
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 Spondyr in the ClawLink dashboard — paste your Spondyr API key once.
Verify the connection by asking Hermes:
Use Spondyr to conditions list and walk me through the result in plain English.
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 Spondyr is connected in the dashboard, that agent calls the same 21 Spondyr tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Spondyr MCP for Hermes
Looking for a Spondyr MCP server for Hermes Agent? ClawLink connects Spondyr to Hermes Agent and exposes 21 Spondyr tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using OpenClaw instead? The OpenClaw Spondyr integration works the same way.
What the Hermes Agent Spondyr integration can do
21 Spondyr tools are ready for Hermes Agent once the account is connected. The 19 below are the ones people reach for most; your agent can call all 21.
19 of 21 Spondyr tools for Hermes
| Tool | What it does |
|---|---|
Conditions list spondyr_conditions_list | List all conditions for a transaction type |
Get event types spondyr_get_event_types | Retrieves all event types associated with a specific transaction type in Spondyr |
Get spondyr status spondyr_get_spondyr_status | Retrieve the status of a previously generated correspondence |
Get transaction types spondyr_get_transaction_types | Retrieve a list of available transaction types |
Recipient get spondyr_recipient_get | Retrieve details of a specific recipient |
Recipients list spondyr_recipients_list | List all recipients for a transaction type |
Search filter get spondyr_search_filter_get | Retrieves details of a specific search filter in Spondyr by name and transaction type |
Search filters list spondyr_search_filters_list | List all search filters for a transaction type |
Search spondyrs spondyr_search_spondyrs | Search for generated correspondence (spondyrs) by multiple criteria including batch ID, event |
Template get spondyr_template_get | Retrieve detailed configuration for a specific correspondence template |
Templates list spondyr_templates_list | List all templates configured for a transaction type |
Transaction type get spondyr_transaction_type_get | Retrieve details of a specific transaction type |
Create condition spondyr_create_condition | Create a condition rule for template selection in Spondyr |
Create transaction type spondyr_create_transaction_type | Create a new transaction type |
Deliver spondyr spondyr_deliver_spondyr | Trigger delivery of previously generated correspondence to recipients |
Event type update spondyr_event_type_update | Update an existing event type name within a transaction type |
Search filter create spondyr_search_filter_create | Create a new search filter for a transaction type in Spondyr |
Sso stub spondyr_sso_stub | Create a one-time SSO user stub in Spondyr |
Transaction type update spondyr_transaction_type_update | Updates an existing transaction type's name and/or JSON schema in Spondyr |
Try it: find the Spondyr tool you need
Browse the 19 Spondyr tools
Click any tool to see exactly what Hermes can do and copy a ready-to-use prompt.
Example prompts
Use Spondyr to conditions list and walk me through the result in plain English.
Pull the relevant data from Spondyr, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Spondyr, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Spondyr, 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 Spondyr working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Spondyr API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Spondyr 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 Spondyr. | 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 Spondyr actions to the runtime in a format your agent can reliably use. | 21 tools for Spondyr are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Spondyr 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 Spondyr in the browser, and the 21 tools above work from chat. There is no SDK and no config file, and the Spondyr 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 Spondyr
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 Spondyr 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 Spondyr tools
Spondyr 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 Spondyr 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.
Spondyr 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 Spondyr 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 Spondyr integration?
Yes. ClawLink is the fastest way to connect Hermes to Spondyr: link your Spondyr account once in the browser and Hermes Agent can call the Spondyr API through 21 ready-made tools — no custom code or token handling.
How do I connect Spondyr 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 Spondyr in the dashboard and Hermes can use it from the next message — no config files, and the Spondyr key you paste is stored server-side instead of in your environment.
How long does it take to connect Spondyr to Hermes Agent?
About two minutes. Sign in, click Connect next to Spondyr in the dashboard, authenticate, and Hermes Agent can use it from the next chat message.
Why use ClawLink instead of wiring Spondyr 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 Spondyr working from chat.
Hermes paired but still can't use Spondyr
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.
