# How to connect Enginemailer to Hermes Agent (paste one key, 38 tools)

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

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

Most guides for giving Hermes Agent Enginemailer 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 Enginemailer setup: pair once in the browser and your always-on Hermes agent can act on Enginemailer 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 Enginemailer.

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

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

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

Verify the connection by asking Hermes:

> Use Enginemailer to batch update status 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:

```bash
npx -y @useclawlink/cli login
```

`login` opens the same browser approval and stores a credential locally. Once Enginemailer is connected in the dashboard, that agent calls the same 38 Enginemailer 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).

## Enginemailer MCP for Hermes

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

## What the Hermes Agent Enginemailer integration can do

38 Enginemailer 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 38.

### 30 of 38 Enginemailer tools for Hermes

| Tool | What it does |
|---|---|
| **Batch update status** `enginemailer_batch_update_status` | Check the status of a batch subscriber update operation |
| **Check export status v2** `enginemailer_check_export_status_v2` | Check status of a previously requested CSV report export |
| **Connect** `enginemailer_connect` | Test API connection and verify authentication |
| **Export CSV report v2** `enginemailer_export_csv_report_v2` | Export a transactional email report as CSV |
| **Find subscriber** `enginemailer_find_subscriber` | Find a subscriber by email address via N8N integration |
| **Get getcustomfield** `enginemailer_get_getcustomfield` | Retrieve the list of custom fields configured for subscribers |
| **Get listcampaign** `enginemailer_get_listcampaign` | Get a list of undelivered campaigns |
| **Get new subscribers** `enginemailer_get_new_subscribers` | Retrieve new subscribers with optional filtering by source, form, page, or popup |
| **Get subcategory** `enginemailer_get_subcategory` | Retrieve subcategories for a given category |
| **Get subscriber** `enginemailer_get_subscriber` | Retrieve subscriber information by email address |
| **Get subscriber autoresponder completed** `enginemailer_get_subscriber_autoresponder_completed` | Retrieve subscribers who completed autoresponders with optional filtering by autoresponder ID |
| **Get subscriber autoresponder triggered** `enginemailer_get_subscriber_autoresponder_triggered` | Retrieve subscribers who triggered autoresponders with optional filtering by autoresponder ID |
| **Get subscribers deleted** `enginemailer_get_subscribers_deleted` | Retrieve deleted subscribers since last polling date |
| **Get subscribers modified** `enginemailer_get_subscribers_modified` | Retrieve modified subscribers since last polling date with optional limit |
| **Get subscribers tagged** `enginemailer_get_subscribers_tagged` | Retrieve subscribers who were tagged with optional filtering by subcategory |
| **Get subscribers untagged** `enginemailer_get_subscribers_untagged` | Retrieve subscribers who were untagged from subcategories |
| **Get unsubscribe** `enginemailer_get_unsubscribe` | Retrieve unsubscribe events with optional filtering by campaign or autoresponder |
| **List autoresponders** `enginemailer_list_autoresponders` | Retrieve a list of all autoresponders |
| **List campaigns** `enginemailer_list_campaigns` | Retrieve a list of all campaigns |
| **List forms** `enginemailer_list_forms` | Retrieve a list of available forms in Enginemailer |
| **List pages** `enginemailer_list_pages` | Retrieve a list of all pages |
| **List popups** `enginemailer_list_popups` | Retrieve a list of popups from Enginemailer |
| **List templates** `enginemailer_list_templates` | Retrieve a list of all email templates |
| **Activate subscriber** `enginemailer_activate_subscriber` | Activate an inactive subscriber in EngineMailer |
| **Add update subscriber** `enginemailer_add_update_subscriber` | Add or update a subscriber with custom fields via N8N integration |
| **Batch update subscribers** `enginemailer_batch_update_subscribers` | Add or update multiple subscribers with custom fields in a single batch operation |
| **Create campaign** `enginemailer_create_campaign` | Create a new email campaign |
| **Insert subscriber** `enginemailer_insert_subscriber` | Add a new subscriber with optional custom fields |
| **Pause campaign** `enginemailer_pause_campaign` | Pause a scheduled email campaign |
| **Post update subscriber** `enginemailer_post_update_subscriber` | Update data for an existing subscriber in EngineMailer |

## Example prompts

**Batch Update Status**

> Use Enginemailer to batch update status and walk me through the result in plain English.

**Check Export Status V2**

> Use Enginemailer to check export status v2 and walk me through the result in plain English.

**Connect**

> Use Enginemailer to connect and walk me through the result in plain English.

**Export Csv Report V2**

> Use Enginemailer to export csv report v2 and walk me through the result in plain English.

## 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 Enginemailer working from chat.

| | Manual | ClawLink |
|---|---|---|
| **Credential handling** | Collect, validate, store, and rotate the Enginemailer API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Enginemailer 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 Enginemailer. | 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 Enginemailer actions to the runtime in a format your agent can reliably use. | 38 tools for Enginemailer are already exposed through ClawLink, so the agent can read and act from chat immediately. |

## ClawLink vs. Composio

Composio also exposes Enginemailer 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 Enginemailer in the browser, and the 38 tools above work from chat. There is no SDK and no config file, and the Enginemailer 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 Enginemailer
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 Enginemailer 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 Enginemailer tools
Enginemailer 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 Enginemailer 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.

### Enginemailer 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 Enginemailer 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 Enginemailer integration?
Yes. ClawLink is the fastest way to connect Hermes to Enginemailer: link your Enginemailer account once in the browser and Hermes Agent can call the Enginemailer API through 38 ready-made tools — no custom code or token handling.

### How do I connect Enginemailer 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 Enginemailer in the dashboard and Hermes can use it from the next message — no config files, and the Enginemailer key you paste is stored server-side instead of in your environment.

### How long does it take to connect Enginemailer to Hermes Agent?
About two minutes. Sign in, click Connect next to Enginemailer in the dashboard, authenticate, and Hermes Agent can use it from the next chat message.

### Why use ClawLink instead of wiring Enginemailer 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 Enginemailer working from chat.

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

- [ActiveCampaign tools](https://claw-link.dev/hermes/activecampaign) — Marketing automation, CRM, and email marketing
- [Connect Benchmark Email](https://claw-link.dev/hermes/benchmark-email) — Benchmark Email is a comprehensive email marketing platform offering tools for creating, sending, and analyzing email campaigns.
- [Mailchimp](https://claw-link.dev/hermes/mailchimp) — Create email campaigns and manage audiences