# How to connect Esputnik to Hermes Agent (paste one key, 89 tools)

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

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

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

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

Verify the connection by asking Hermes:

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

## Esputnik MCP for Hermes

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

## What the Hermes Agent Esputnik integration can do

89 Esputnik 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 89.

### 30 of 89 Esputnik tools for Hermes

| Tool | What it does |
|---|---|
| **Get account info** `esputnik_get_account_info` | Retrieve basic eSputnik account information |
| **Get app inbox message** `esputnik_get_app_inbox_message` | Retrieves an App Inbox message by its unique identifier from eSputnik |
| **Get broadcasts** `esputnik_get_broadcasts` | Retrieve a paginated list of broadcast campaigns from eSputnik |
| **Get contact** `esputnik_get_contact` | Retrieve complete information about a contact by their ID |
| **Get contact emails** `esputnik_get_contact_emails` | Retrieve email addresses of contacts by their contact IDs |
| **Get contact import status** `esputnik_get_contact_import_status` | Retrieve the status of a contact import session in eSputnik |
| **Get contact message history** `esputnik_get_contact_message_history` | Retrieve a contact's message history across multiple channels from eSputnik |
| **Get contact subscriptions** `esputnik_get_contact_subscriptions` | Retrieve all subscription categories a contact is enrolled in |
| **Get contacts** `esputnik_get_contacts` | Search for contacts in eSputnik using various filter criteria |
| **Get email interfaces** `esputnik_get_email_interfaces` | Retrieve all configured email interfaces (sender names) from eSputnik |
| **Get email message** `esputnik_get_email_message` | Retrieves an email message by its unique identifier from eSputnik |
| **Get email view link** `esputnik_get_email_view_link` | Get a link to view an email message in browser from eSputnik |
| **Get message status** `esputnik_get_message_status` | Retrieve delivery status for sent messages across all channels (email, SMS, Viber, push) |
| **Get mobile push message** `esputnik_get_mobile_push_message` | Retrieves a mobile push message by its unique identifier from eSputnik |
| **Get organization balance** `esputnik_get_organization_balance` | Retrieve the current eSputnik organization balance |
| **Get organization billing history** `esputnik_get_organization_billing_history` | Retrieve the organization's billing history from eSputnik, broken down by day and media channel |
| **Get preprocessor file status** `esputnik_get_preprocessor_file_status` | Retrieve the status of a preprocessor file upload session |
| **Get product feeds** `esputnik_get_product_feeds` | Retrieve product feeds configuration from eSputnik |
| **Get promocodes count** `esputnik_get_promocodes_count` | Get the number of available promotional codes in eSputnik |
| **Get site domain** `esputnik_get_site_domain` | Retrieve the organization's domain configuration from eSputnik |
| **Get site script** `esputnik_get_site_script` | Retrieve the site tracking script for your eSputnik account |
| **Get sms interfaces** `esputnik_get_sms_interfaces` | Retrieve all SMS interfaces (alpha names) configured for the organization |
| **Get subscription categories** `esputnik_get_subscription_categories` | Retrieve all subscription categories for the organization |
| **Get telegram message** `esputnik_get_telegram_message` | Retrieve a Telegram bot message by its unique identifier from eSputnik |
| **List promocodes** `esputnik_list_promocodes` | Retrieve a list of promotional codes from eSputnik |
| **List webpush domains** `esputnik_list_webpush_domains` | Retrieve the list of domains registered for web push notifications |
| **Search app inbox messages** `esputnik_search_app_inbox_messages` | Search for mobile App Inbox messages using a part of the name or a tag |
| **Search contacts** `esputnik_search_contacts` | Search for all contacts in a segment (group) |
| **Search email messages** `esputnik_search_email_messages` | Search for email messages using a part of their name or a tag |
| **Search mobilepush messages** `esputnik_search_mobilepush_messages` | Search for mobile push messages using part of the name or a tag |

## Example prompts

**Get Account Info**

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

**Get App Inbox Message**

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

**Get Broadcasts**

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

**Get Contact**

> Pull the relevant data from Esputnik, 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 Esputnik working from chat.

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

## ClawLink vs. Composio

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

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

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

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

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

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