How to connect Dynosend to Hermes Agent
Connect Dynosend to Hermes with ClawLink: paste your Dynosend key once and 18 tools work from chat. No MCP server to run, nothing stored on your machine.
DynosendAPI KEYMCPDynosend is an email marketing platform for managing audiences and contacts, operating campaigns, sending transactional messages, and tracking customer events.. Once connected, Hermes Agent can read and act on Dynosend from chat — pairing, token refresh, and tool wiring handled for you.
Most guides for giving Hermes Agent Dynosend 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 Dynosend setup: pair once in the browser and your always-on Hermes agent can act on Dynosend 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 Dynosend.
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 Dynosend
Paste your API key in the dashboard.
- 3
Use it from chat
Ask Hermes Agent: "What can you do with Dynosend?"
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 Dynosend in the ClawLink dashboard — paste your Dynosend API key once.
Verify the connection by asking Hermes:
Use Dynosend to check blacklist 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 Dynosend is connected in the dashboard, that agent calls the same 18 Dynosend tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Dynosend MCP for Hermes
Looking for a Dynosend MCP server for Hermes Agent? ClawLink connects Dynosend to Hermes Agent and exposes 18 Dynosend tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using OpenClaw instead? The OpenClaw Dynosend integration works the same way.
What the Hermes Agent Dynosend integration can do
18 Dynosend tools are ready for Hermes Agent once the account is connected. The 17 below are the ones people reach for most; your agent can call all 18.
17 of 18 Dynosend tools for Hermes
| Tool | What it does |
|---|---|
Check blacklist dynosend_check_blacklist | Check whether an email address is on the connected Dynosend account's blacklist and return its |
Find duplicate contacts dynosend_find_duplicate_contacts | Find contacts that use the same email address across all audiences in the connected Dynosend |
Get audience dynosend_get_audience | Get one audience's configuration, custom-field definitions, contact information, and |
Get campaign dynosend_get_campaign | Get one campaign's configuration and delivery, open, click, spam, bounce, and unsubscribe |
Get contact dynosend_get_contact | Get one contact in an audience by contact UID or email address |
List audiences dynosend_list_audiences | List audiences available to the connected Dynosend account, including the UID needed by |
List campaigns dynosend_list_campaigns | List campaigns in the connected Dynosend account, including status and the campaign UID used by |
List contacts dynosend_list_contacts | Return one page of contacts in a Dynosend audience, including contact UIDs, subscription |
Add tags to contact dynosend_add_tags_to_contact | Append one or more tags to a contact without replacing its existing tags |
Create contact dynosend_create_contact | Create a contact in an audience, optionally assigning tags and audience-defined custom fields |
Record contact event dynosend_record_contact_event | Record an application event for a contact in an audience |
Set contact subscription status dynosend_set_contact_subscription_status | Set a contact's subscription status to subscribed or unsubscribed in an audience |
Update contact dynosend_update_contact | Update a contact's email, replace its complete tag set, or set audience-defined custom fields |
Add email to blacklist dynosend_add_email_to_blacklist | Permanently add an email address to the Dynosend blacklist |
Send transactional message dynosend_send_transactional_message | Send a configured Dynosend transactional message |
Set campaign delivery state dynosend_set_campaign_delivery_state | Pause a sending campaign or resume a paused campaign by setting its delivery state to paused or |
Start campaign dynosend_start_campaign | Start a ready broadcast campaign |
Try it: find the Dynosend tool you need
Browse the 17 Dynosend tools
Click any tool to see exactly what Hermes can do and copy a ready-to-use prompt.
Example prompts
Use Dynosend to check blacklist and walk me through the result in plain English.
Use Dynosend to find duplicate contacts and walk me through the result in plain English.
Pull the relevant data from Dynosend, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Dynosend, 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 Dynosend working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Dynosend API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Dynosend 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 Dynosend. | 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 Dynosend actions to the runtime in a format your agent can reliably use. | 18 tools for Dynosend are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Dynosend 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 Dynosend in the browser, and the 18 tools above work from chat. There is no SDK and no config file, and the Dynosend 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 Dynosend
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 Dynosend 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 Dynosend tools
Dynosend 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 Dynosend 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.
Dynosend 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 Dynosend 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 Dynosend integration?
Yes. ClawLink is the fastest way to connect Hermes to Dynosend: link your Dynosend account once in the browser and Hermes Agent can call the Dynosend API through 18 ready-made tools — no custom code or token handling.
How do I connect Dynosend 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 Dynosend in the dashboard and Hermes can use it from the next message — no config files, and the Dynosend key you paste is stored server-side instead of in your environment.
How long does it take to connect Dynosend to Hermes Agent?
About two minutes. Sign in, click Connect next to Dynosend in the dashboard, authenticate, and Hermes Agent can use it from the next chat message.
Why use ClawLink instead of wiring Dynosend 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 Dynosend working from chat.
Hermes paired but still can't use Dynosend
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.
