# How to connect Postalytics to Hermes Agent (paste one key, 24 tools)

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

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

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

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

Verify the connection by asking Hermes:

> Pull the relevant data from Postalytics, 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 Postalytics is connected in the dashboard, that agent calls the same 24 Postalytics 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).

## Postalytics MCP for Hermes

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

## What the Hermes Agent Postalytics integration can do

24 Postalytics 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 24.

### 20 of 24 Postalytics tools for Hermes

| Tool | What it does |
|---|---|
| **Get all contact lists** `postalytics_get_all_contact_lists` | Retrieve all contact lists for an account |
| **Get all contacts on a list** `postalytics_get_all_contacts_on_a_list` | Retrieve all contacts from a specified contact list with pagination support |
| **Get all drip campaigns** `postalytics_get_all_drip_campaigns` | Retrieve all triggered drip campaign names and endpoint IDs in the account |
| **Get all flows** `postalytics_get_all_flows` | Retrieve all flows for the requester's account |
| **Get all webhooks** `postalytics_get_all_webhooks` | Retrieve all webhooks configured for the authenticated account |
| **Get integrations** `postalytics_get_integrations` | Retrieve all Connect integrations configured for the authenticated user's account |
| **Get my account** `postalytics_get_my_account` | Retrieve basic account information for the authenticated user |
| **Get suppression list** `postalytics_get_suppression_list` | Get the details of a suppression list based on the id supplied |
| **Get suppression list contact** `postalytics_get_suppression_list_contact` | Retrieve a specific contact from a suppression list |
| **Get suppression list contacts** `postalytics_get_suppression_list_contacts` | Get all contacts on a specified suppression list |
| **Get suppression lists** `postalytics_get_suppression_lists` | Retrieve all suppression lists for the authenticated user |
| **Add account** `postalytics_add_account` | Create a new sub-account in the Postalytics system |
| **Add contact** `postalytics_add_contact` | Add a contact to a specified contact list with their information |
| **Create new campaign** `postalytics_create_new_campaign` | Create a new direct mail campaign in Postalytics |
| **Create suppression list** `postalytics_create_suppression_list` | Create a new suppression list that can be used in campaigns to suppress contacts from being |
| **Create suppression list contact** `postalytics_create_suppression_list_contact` | Create a new suppression contact on a specified suppression list |
| **Create template** `postalytics_create_template` | Create a new template with full HTML for postcard or letter |
| **Create webhook** `postalytics_create_webhook` | Create a new webhook to receive campaign event notifications from Postalytics |
| **Update account** `postalytics_update_account` | Update an existing account in the Postalytics system |
| **Update suppression list contact** `postalytics_update_suppression_list_contact` | Update a suppression contact on the specified suppression list |

## Example prompts

**Get All Contact Lists**

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

**Get All Contacts On A List**

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

**Get All Drip Campaigns**

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

**Get All Flows**

> Pull the relevant data from Postalytics, 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 Hermes Agent. That is fine if you want to build and maintain the integration yourself. Most teams just want Postalytics working from chat.

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

## ClawLink vs. Composio

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

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

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

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

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

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

- [Connect ActiveCampaign](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
