# How to connect Engage to Hermes Agent (paste one key, 22 tools)

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

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

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

1. **Install ClawLink** — add the plugin to Hermes Agent once.
2. **Connect Engage** — 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 engage  # connect Engage (browser OAuth)
npx -y @useclawlink/cli actions engage  # list available actions
npx -y @useclawlink/cli run engage <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 Engage in the [ClawLink dashboard](https://claw-link.dev/dashboard) — enter your Engage account details once.

Verify the connection by asking Hermes:

> Pull the relevant data from Engage, summarize it in plain English, and point out anything that needs attention.

### 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 Engage is connected in the dashboard, that agent calls the same 22 Engage 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).

## Engage MCP for Hermes

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

## What the Hermes Agent Engage integration can do

22 Engage tools are ready for Hermes Agent once the account is connected. The 20 below are the ones people reach for most; your agent can call all 22.

### 20 of 22 Engage tools for Hermes

| Tool | What it does |
|---|---|
| **Get account members** `engage_get_account_members` | Retrieve all members (Customers) of an Account in Engage |
| **Get list** `engage_get_list` | Retrieve a single List by its ID |
| **Get user** `engage_get_user` | Retrieve a single user by their user ID |
| **List lists** `engage_list_lists` | Retrieve a paginated list of all Lists in Engage |
| **List users** `engage_list_users` | Retrieve a paginated list of all users in Engage |
| **Add customer to accounts** `engage_add_customer_to_accounts` | Add a customer to one or more account entities |
| **Add user to lists** `engage_add_user_to_lists` | Add a Customer or Account to one or more Lists in Engage.so |
| **Convert user type** `engage_convert_user_type` | Convert a user between Customer and Account entity types |
| **Create list** `engage_create_list` | Create a new List in Engage for organizing subscribers |
| **Create user** `engage_create_user` | Create a new user (Customer or Account) in Engage |
| **Send batch request** `engage_send_batch_request` | Batch multiple create user, update user, and add user events operations into a single API call |
| **Subscribe user to list** `engage_subscribe_user_to_list` | Create a user and subscribe them to an Engage.so List |
| **Track user event** `engage_track_user_event` | Add user events to Engage |
| **Update account role** `engage_update_account_role` | Update the role of a Customer in an Account or set a new one if none exists |
| **Update subscriber status** `engage_update_subscriber_status` | Update a subscriber's status on a List |
| **Update user** `engage_update_user` | Update user data and attributes on Engage |
| **Archive list** `engage_archive_list` | Archive a List in Engage |
| **Archive user** `engage_archive_user` | Archive a user in Engage |
| **Merge users** `engage_merge_users` | Merge two user profiles in Engage |
| **Remove customer from account** `engage_remove_customer_from_account` | Remove a Customer from an Account in Engage |

## Example prompts

**Get Account Members**

> Pull the relevant data from Engage, summarize it in plain English, and point out anything that needs attention.

**Get List**

> Pull the relevant data from Engage, summarize it in plain English, and point out anything that needs attention.

**Get User**

> Pull the relevant data from Engage, summarize it in plain English, and point out anything that needs attention.

**List Lists**

> List the relevant items in Engage, group them by priority, and recommend what Hermes should do next.

## ClawLink vs. building it yourself

The alternative to ClawLink is usually manual credential 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 Engage working from chat.

| | Manual | ClawLink |
|---|---|---|
| **Setup flow** | Collect and store the right Engage credentials yourself, then keep the account mapping and request format correct. | ClawLink keeps the setup in one hosted flow so non-technical users can link Engage without custom integration screens. |
| **Ongoing maintenance** | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Engage. | 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 Engage actions to the runtime in a format your agent can reliably use. | 22 tools for Engage are already exposed through ClawLink, so the agent can read and act from chat immediately. |

## ClawLink vs. Composio

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

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

### The setup form accepts credentials but calls still fail
Re-enter the credentials carefully and verify the account-level permissions for Engage. Basic and token-based integrations tend to fail on formatting mistakes or limited account roles.

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

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

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

### Why use ClawLink instead of wiring Engage up myself?
The alternative to ClawLink is usually manual credential 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 Engage working from chat.

### Hermes paired but still can't use Engage
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 ActiveCampaign integration](https://claw-link.dev/hermes/activecampaign) — Marketing automation, CRM, and email marketing
- [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.
- [Hermes Mailchimp integration](https://claw-link.dev/hermes/mailchimp) — Create email campaigns and manage audiences