# How to connect Retently to Hermes Agent (paste one key, 15 tools)

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

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

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

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

Verify the connection by asking Hermes:

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

## Retently MCP for Hermes

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

## What the Hermes Agent Retently integration can do

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

### 14 of 15 Retently tools for Hermes

| Tool | What it does |
|---|---|
| **Get campaigns** `retently_get_campaigns` | Retrieve a list of campaigns associated with the account |
| **Get customer by ID** `retently_get_customer_by_id` | Retrieve detailed information about a specific customer by their unique ID |
| **Get customers** `retently_get_customers` | Retrieve a list of customers with optional parameters for pagination, sorting, and filtering by |
| **Get feedback** `retently_get_feedback` | Retrieve feedback received from customers |
| **Get feedback by ID** `retently_get_feedback_by_id` | Retrieve detailed information about specific feedback by its unique ID |
| **Get latest score** `retently_get_latest_score` | Retrieve the latest NPS score for the account |
| **Get outbox** `retently_get_outbox` | Retrieve the outbox of surveys that are scheduled to be sent |
| **Get reports** `retently_get_reports` | Retrieve reports related to NPS surveys, including scores and trends |
| **Get templates** `retently_get_templates` | Retrieve a list of survey templates available in the account |
| **Add feedback tags** `retently_add_feedback_tags` | Add tags to feedback items by providing feedback IDs and corresponding tags |
| **Add feedback topics** `retently_add_feedback_topics` | Add topics to feedback items by providing feedback IDs and corresponding topics |
| **Create or update customers** `retently_create_or_update_customers` | Create new customers or update existing ones by providing their details, including email, name |
| **Send transactional survey** `retently_send_transactional_survey` | Send a transactional survey to customers |
| **Unsubscribe customers** `retently_unsubscribe_customers` | Unsubscribe customers from receiving surveys by providing their email addresses |

## Example prompts

**Get Campaigns**

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

**Get Customer By Id**

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

**Get Customers**

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

**Get Feedback**

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

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

## ClawLink vs. Composio

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

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

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

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

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

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

- [Zendesk tools](https://claw-link.dev/hermes/zendesk) — Manage support tickets, macros, users, and organizations
- [Gleap tools](https://claw-link.dev/hermes/gleap) — Gleap is an all-in-one customer feedback tool for apps and websites, enabling direct communication with users to build better software by discovering their everyday pain points.
- [Freshdesk](https://claw-link.dev/hermes/freshdesk) — Handle support tickets, contacts, and helpdesk operations
