# How to connect Resend to Hermes Agent (paste one key, 62 tools)

> Connect Resend to Hermes with ClawLink: paste your Resend key once and 62 tools work from chat. No MCP server to run, nothing stored on your machine.

Web version: https://claw-link.dev/hermes/resend

Most guides for giving Hermes Agent Resend 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 Resend setup: pair once in the browser and your always-on Hermes agent can act on Resend for you, reading and doing real work on your behalf with no auth, token refresh, or tool wiring to build yourself.

**Start here — 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.

## Setup

It takes three steps to connect Hermes to Resend.

1. **Install ClawLink** — add the plugin to Hermes Agent once.
2. **Connect Resend** — one-click OAuth in the ClawLink dashboard.
3. **Use it from chat** — ask Hermes Agent in plain English.

**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 resend  # connect Resend (browser OAuth)
npx -y @useclawlink/cli actions resend  # list available actions
npx -y @useclawlink/cli run resend <action> --input '<json>'  # 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 Resend in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Resend API key once.

Verify the connection by asking Hermes:

> Send an email to \<address> with subject \<subject> from \<from> using resend_send_email, and show me the exact body before sending. Do not send until I approve.

### 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 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](https://claw-link.dev/learn/connect-apps-to-any-ai-agent).

## Resend MCP for Hermes

Looking for a Resend MCP server for Hermes Agent? ClawLink connects Resend to Hermes Agent and exposes 62 Resend 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 Resend integration](https://claw-link.dev/openclaw/resend) works the same way.

This page is about Hermes Agent, the CLI agent from the OpenClaw family that pairs through `hermes plugins install`, not the email platform guides sometimes mean when they say Hermes. On this provider the manual setup search results teach is a Composio Connect MCP config: copy an MCP URL and a consumer API key, paste them into `~/.hermes/config.yaml`, restart the agent. This page's flow removes that file: a Resend API key pasted once into a hosted setup page, `hermes clawlink begin` and `hermes clawlink finish`, and 62 Resend tools callable from chat. The one thing to be honest about up front is that Resend itself now ships a hosted MCP with browser OAuth, so the comparison is no longer hosted versus manual, it is which hosted route: their MCP endpoint, or 62 named tools under one dashboard with every connection revocable in one place. Either way the key or the OAuth lives server-side, which is the architecture the engines themselves recommend when they suggest a backend proxy holding the credential.

## What the Hermes Agent Resend integration can do

62 Resend tools are ready for Hermes Agent 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 Hermes

| 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 |

## Example prompts

**Send with approval**

> Send an email to \<address> with subject \<subject> from \<from> using resend_send_email, and show me the exact body before sending. Do not send until I approve.

**Audit deliverability**

> Use resend_list_emails for the last 7 days and summarize sends by status: delivered, bounced, and failed, with the top error message. Do not resend anything.

**Domain health**

> Call resend_list_domains and tell me which domains are verified and which are pending DNS verification. For the pending one, explain what records are needed.

**Audience work**

> List my audiences and their contacts with resend_list_audiences and resend_list_contacts, and tell me which segment of \<audience> has the most contacts. Do not create anything.

## How the Resend tools behave

Details that decide whether a Resend prompt sends mail or produces a 403 the agent cannot explain.

- **A verified domain is the prerequisite for everything that sends.** `resend_list_domains` shows verification state, and a from address must sit on a verified domain; the onboarding@resend.dev test sender is the one exception and it is a test path, not a production one.
- **The key the agent uses is the key you pasted, scoped as it was created.** Read-only keys fail every send with a permissions error, and the fix is a full-access key in Resend, not a reconnect.
- **Sent and received are separate tool families.** `resend_list_emails` and `resend_list_received_emails` are different surfaces; `resend_get_email_attachment` retrieves attachments by id from either side, and an id from the wrong family fails like a typo.
- **Webhooks and API keys are readable.** `resend_list_webhooks` and `resend_list_api_keys` expose account configuration, which makes them useful for audits and prompts for caution: reading a list of keys is fine, an agent creating one is account state worth approving.
- **Audiences, contacts, and templates are objects, not messages.** `resend_create_audience`, `resend_create_contact`, and `resend_create_template` change shared account state, so they deserve a confirmation step in the prompt.
- **Everything is id-addressed.** Emails, domains, contacts, templates, and webhooks are referenced by id returned from the list tools; an id from documentation fails like a typo, and the list tools are where real ids come from.

## 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 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 Hermes Agent 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](https://claw-link.dev/hub/composio-alternatives) comparison.

### Hermes paired but still can't use Resend
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 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.

### Resend returns 403 or "insufficient permissions" although the account shows as connected
Resend's own knowledge base names the causes, and three of them are account state rather than connection state. The first is key scope: a key restricted to read-only or to a specific project fails sending calls, and the fix is a full-access key. The second is domain verification: sending from a domain that is not verified in the account fails, and the fix is the domain's DNS records in Resend. The third is a `from` mismatch: the sender address must sit on a verified domain, and a from address on an unverified or foreign domain is refused. The fourth is the test sender: onboarding@resend.dev only works for testing and is the cause engines teach for 403s on first sends. The page's own cause completes the list: a placeholder argument such as YOUR_DOMAIN reaching the API literally. Re-paste the current key, check the domain and from address, then re-run before touching the connection.

Ask the agent to diagnose it:

```text
Call resend_list_domains and tell me the verification status of each domain, then quote the exact error text from the failed call including the from address it used. Do not retry it yet.
```

### Resend calls start failing or the agent reports a rate limit
Resend rate-limits sending and API traffic, and an agent that retries a failed send in a tight loop is the shape that meets the limit fastest. The response is to stop and look at the send itself first: failed sends are usually the account causes above (domain, from address, scope) rather than rate, and retrying the same send produces the same error. If the error is a genuine rate limit, the agent should report the retry detail and pace the work, batching where the tools allow, rather than hammering the endpoint.

Ask the agent to diagnose it:

```text
Tell me exactly which Resend tools you called in the last few minutes and what the send or list pattern was. Quote the full error text from the last response. Do not call Resend again until I reply.
```

### Resend tools are missing, or one tool name is not found
Two failures share this symptom. If no Resend tools appear at all, the connection or pairing is incomplete: confirm the plugin was installed with --enable, that `hermes clawlink begin` and `hermes clawlink finish` both ran, and that Resend shows as connected in the dashboard. If most tools work and one name fails, the name is wrong rather than missing, and the error lists the closest real ones. There is also a first-call timing case: schemas load on demand, so the opening Resend call in a fresh session can arrive before the catalog and needs one retry. The fixes search results teach for this symptom, reloading the MCP client and setting RESEND_API_KEY in an environment, belong to a local setup and do not apply here.

Ask the agent to diagnose it:

```text
List the Resend tools you actually have access to. If there are none, say so plainly and tell me whether Resend shows as connected. Do not guess tool names.
```

### 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.

### Is there a Hermes Agent Resend integration?
Yes. ClawLink is the fastest way to connect Hermes to Resend: link your Resend account once in the browser and Hermes Agent can call the Resend API through 62 ready-made tools — no custom code or token handling.

### How do I connect Resend 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 Resend in the dashboard and Hermes can use it 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 Hermes Agent?
About two minutes. Sign in, click Connect next to Resend in the dashboard, authenticate, and Hermes Agent 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 Hermes Agent. That is fine if you want to build and maintain the integration yourself. Most teams just want Resend working from chat.

### Why paste a key when Resend has its own hosted MCP with browser OAuth?
Resend's hosted MCP is a real route: a streamable HTTP endpoint, browser OAuth, no raw key handled by the user. The difference is the surface and the management. Their MCP is one endpoint registered in a client config; this page's route exposes 62 named tools Hermes can reason about individually, and it puts Resend beside your other connected accounts with one dashboard to manage and revoke. If you run a plain MCP client and want Resend there verbatim, their hosted server is the direct choice. If Hermes is your agent and you want Resend alongside everything else, this is the shape that fits.

### Which key does this need, and where does it end up?
A Resend API key from the Resend dashboard, pasted once on the hosted setup page and held server-side. It is the same key the manual routes put in a config file or environment; the difference is that it never sits on a machine. Rotating it in Resend means updating one place, and disconnecting from the dashboard revokes the agent's use of it immediately.

### What can the agent do in Resend?
Send email, manage domains and their verification, create and manage audiences, contacts, and templates, read sent and received email lists and attachments, manage webhooks, and read API keys. The sending half needs two account prerequisites that are the usual 403 causes: a verified domain and a `from` address on that domain. The management half is where prompts deserve care, because creating domains, audiences, and templates is account state that other work depends on.

### Can the agent read inbound email through Resend?
The tool set includes `resend_list_received_emails` and `resend_get_email_attachment`, so received messages are readable when the account has inbound enabled. That is not the same as full inbox semantics with reply threading, which belongs to the agent's email reading side; for sending plus inbound visibility, this integration covers both ends of the loop.

### Hermes paired but still can't use Resend
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

- [Hermes SendGrid integration](https://claw-link.dev/hermes/sendgrid) — Deliver transactional and marketing emails
- [Dialpad tools](https://claw-link.dev/hermes/dialpad) — Business phone, messaging, and video conferencing
- [Discord Bot tools](https://claw-link.dev/hermes/discord-bot) — Automate Discord server actions with bot-specific permissions