# How to connect Iterate to Hermes Agent (paste one key, 13 tools)

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

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

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

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

Verify the connection by asking Hermes:

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

## Iterate MCP for Hermes

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

## What the Hermes Agent Iterate integration can do

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

### 11 of 13 Iterate tools for Hermes

| Tool | What it does |
|---|---|
| **Get survey** `iterate_get_survey` | Return one survey's configuration and questions by survey ID |
| **Get survey stats** `iterate_get_survey_stats` | Return delivery, display, response-count, and response-rate statistics for one survey |
| **List survey response groups** `iterate_list_survey_response_groups` | Return one reverse-chronological page of completed survey submissions grouped by user, plus a |
| **List survey responses** `iterate_list_survey_responses` | Return one reverse-chronological page of individual answers for a survey, with an optional date |
| **List surveys** `iterate_list_surveys` | Return all surveys available to the connected Iterate API key, including the survey and company |
| **Search company users** `iterate_search_company_users` | Find one user in the connected Iterate company by email, external ID, or one typed user |
| **Add survey recipient** `iterate_add_survey_recipient` | Add one email recipient to a survey for a later send without sending the survey now |
| **Import survey recipients** `iterate_import_survey_recipients` | Add a non-empty batch of email recipients to a survey without sending it, and return duplicate |
| **Anonymize company user** `iterate_anonymize_company_user` | Irreversibly remove one Iterate user's email and attributes while retaining survey responses |
| **Bulk anonymize company users** `iterate_bulk_anonymize_company_users` | Irreversibly remove identifying data from every Iterate company user matching at least one |
| **Send survey** `iterate_send_survey` | Irreversibly send or schedule an email survey to one specified recipient or every previously |

## Example prompts

**Get Survey**

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

**Get Survey Stats**

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

**List Survey Response Groups**

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

**List Survey Responses**

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

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

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

## ClawLink vs. Composio

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

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

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

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

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

### Hermes paired but still can't use Iterate
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 GitHub](https://claw-link.dev/hermes/github) — Manage repositories, issues, pull requests, and workflows
- [PagerDuty tools](https://claw-link.dev/hermes/pagerduty) — Manage incidents, on-call schedules, and services
- [Connect SafetyCulture](https://claw-link.dev/hermes/safetyculture) — SafetyCulture (formerly iAuditor) is a workplace operations platform that enables teams to conduct digital inspections, manage audits, track issues, schedule tasks, and maintain compliance through mobile and web applications.
