How to connect Dynosend to OpenClaw
Connect Dynosend to OpenClaw 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, OpenClaw can read and act on Dynosend from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Dynosend access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical Dynosend setup: install one ClawHub skill, connect Dynosend in the browser, and OpenClaw can call real Dynosend actions from any chat surface with no auth, token refresh, or tool wiring to build yourself.
Setup
It takes three steps to connect OpenClaw to Dynosend.
1Install the plugin
Paste the setup prompt into OpenClaw, or install from the terminal and ask OpenClaw to pair:
openclaw plugins install clawhub:clawlink-plugin- 2
Connect Dynosend
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Dynosend?"
Install by command
The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval:
openclaw plugins install clawhub:clawlink-pluginThen ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say done. Finally, connect Dynosend in the ClawLink dashboard — paste your Dynosend API key once.
Verify the connection by asking OpenClaw:
Use Dynosend to check blacklist and walk me through the result in plain English.
Using a different agent?
The OpenClaw 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 OpenClaw
Looking for a Dynosend MCP server for OpenClaw? ClawLink connects Dynosend to OpenClaw and exposes 18 Dynosend tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Dynosend integration works the same way.
What the OpenClaw Dynosend integration can do
18 Dynosend tools are ready for OpenClaw 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 OpenClaw
| 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 OpenClaw 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 OpenClaw. 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 OpenClaw 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
OpenClaw installed the Dynosend skill but can't call the tools
The ClawHub skill teaches OpenClaw about Dynosend, but the calls run through the ClawLink plugin and your connected account. Make sure Dynosend is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.
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 OpenClaw Dynosend integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Dynosend: link your Dynosend account once in the browser and OpenClaw can call the Dynosend API through 18 ready-made tools — no custom code or token handling.
How do I add Dynosend to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Dynosend skill from ClawHub, then you click Connect in the dashboard to authorize Dynosend. OpenClaw calls the tools 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 OpenClaw?
About two minutes. Sign in, click Connect next to Dynosend in the dashboard, authenticate, and OpenClaw 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 OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Dynosend working from chat.
OpenClaw installed the Dynosend skill but can't call the tools
The ClawHub skill teaches OpenClaw about Dynosend, but the calls run through the ClawLink plugin and your connected account. Make sure Dynosend is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.
