How to connect Resend to OpenClaw
Connect Resend to OpenClaw with ClawLink: paste your Resend key once and 62 tools work from chat. No MCP server to run, nothing stored on your machine.
ResendAPI KEYMCPSend transactional and marketing emails. Once connected, OpenClaw can read and act on Resend from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Resend 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 Resend setup: install one ClawHub skill, connect Resend in the browser, and OpenClaw can call real Resend actions from any chat surface with no auth, token refresh, or tool wiring to build yourself.
Copy this prompt into OpenClaw, or open the Resend skill on ClawHub.
Before installing anything, inspect the ClawHub skill metadata and setup requirements.
If the skill asks you to install a third-party package or CLI, verify its source, maintainer, and package contents before running the install command.
Install the skill "Resend" (hith3sh/resend-mail) from ClawHub only after those checks pass.
Skill page: https://clawhub.ai/hith3sh/resend-mail
Keep the work scoped to this skill only.
After install, help me finish setup from verified skill metadata.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.Setup
It takes three steps to connect OpenClaw to Resend.
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 Resend
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Resend?"
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 Resend in the ClawLink dashboard — paste your Resend API key once.
Verify the connection by asking OpenClaw:
Create it in Resend for me, then confirm the important fields before you finish.
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 Resend is connected in the dashboard, that agent calls the same 62 Resend tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Resend MCP for OpenClaw
Looking for a Resend MCP server for OpenClaw? ClawLink connects Resend to OpenClaw and exposes 62 Resend tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Resend integration works the same way.
What the OpenClaw Resend integration can do
62 Resend tools are ready for OpenClaw once the account is connected. The 30 below are the ones people reach for most; your agent can call all 62.
30 of 62 Resend tools for OpenClaw
| Tool | What it does |
|---|---|
Create audience resend_create_audience | Create a Resend audience |
Create contact resend_create_contact | Create a Resend contact |
Create domain resend_create_domain | Create a Resend domain |
Create template resend_create_template | Create a Resend email template |
Get contact resend_get_contact | Get a Resend contact by ID |
Get template resend_get_template | Get a Resend email template |
List audiences resend_list_audiences | List Resend audiences |
List contacts resend_list_contacts | List Resend contacts in an audience |
List domains resend_list_domains | List Resend domains |
List templates resend_list_templates | List Resend email templates |
Send email resend_send_email | Send an email through Resend |
Get contact property resend_get_contact_property | Retrieve a single contact property from Resend |
Get email attachment resend_get_email_attachment | Retrieve a single attachment from a sent email |
Get segment resend_get_segment | Retrieve a single segment by its ID |
Get topic resend_get_topic | Retrieve a single topic by its ID in Resend |
Get webhook resend_get_webhook | Retrieve a single webhook for the authenticated user |
List all contacts resend_list_all_contacts | Retrieve a list of all contacts from Resend |
List API keys resend_list_api_keys | Retrieve a list of API keys for the authenticated user |
List broadcasts resend_list_broadcasts | Retrieve a list of broadcasts |
List contact properties resend_list_contact_properties | Retrieve a list of contact properties from Resend |
List contact segments resend_list_contact_segments | Retrieve a list of segments that a contact is part of |
List contact topics resend_list_contact_topics | Retrieve a list of topic subscriptions for a contact in Resend |
List email attachments resend_list_email_attachments | Retrieve a list of attachments from a sent email |
List emails resend_list_emails | Retrieve a list of emails sent by your team |
List received emails resend_list_received_emails | Retrieve a list of received emails for the authenticated user |
List segments resend_list_segments | Retrieve a list of segments from Resend |
List topics resend_list_topics | Retrieve a list of topics for the authenticated user |
List webhooks resend_list_webhooks | Retrieve a list of webhooks for the authenticated user |
Retrieve audience resend_retrieve_audience | Retrieve a single audience |
Retrieve contact resend_retrieve_contact | Retrieve a contact in Resend |
Try it: find the Resend tool you need
Browse the 30 Resend tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Create it in Resend for me, then confirm the important fields before you finish.
Create it in Resend for me, then confirm the important fields before you finish.
Create it in Resend for me, then confirm the important fields before you finish.
Create it in Resend for me, then confirm the important fields before you finish.
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 Resend working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Resend API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Resend 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 Resend. | 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 Resend actions to the runtime in a format your agent can reliably use. | 62 tools for Resend are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Resend 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 Resend in the browser, and the 62 tools above work from chat. There is no SDK and no config file, and the Resend 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 Resend skill but can't call the tools
The ClawHub skill teaches OpenClaw about Resend, but the calls run through the ClawLink plugin and your connected account. Make sure Resend 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 Resend 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 Resend tools
Resend 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 Resend 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.
Resend 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 Resend 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 Resend integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Resend: link your Resend account once in the browser and OpenClaw can call the Resend API through 62 ready-made tools — no custom code or token handling.
How do I add Resend to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Resend skill from ClawHub, then you click Connect in the dashboard to authorize Resend. OpenClaw calls the tools from the next message — no config files, and the Resend key you paste is stored server-side instead of in your environment.
How long does it take to connect Resend to OpenClaw?
About two minutes. Sign in, click Connect next to Resend in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring Resend 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 Resend working from chat.
OpenClaw installed the Resend skill but can't call the tools
The ClawHub skill teaches OpenClaw about Resend, but the calls run through the ClawLink plugin and your connected account. Make sure Resend 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.
