# How to connect Reply.io to Hermes Agent (paste one key, 33 tools) > Connect Reply.io to Hermes with ClawLink: paste your Reply.io key once and 33 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/hermes/reply-io Most guides for giving Hermes Agent Reply.io 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 Reply.io setup: pair once in the browser and your always-on Hermes agent can act on Reply.io 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 Reply.io. 1. **Install ClawLink** — add the plugin to Hermes Agent once. 2. **Connect Reply.io** — 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 reply-io # connect Reply.io (browser OAuth) npx -y @useclawlink/cli actions reply-io # list available actions npx -y @useclawlink/cli run reply-io --input '' # 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 Reply.io in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Reply.io API key once. Verify the connection by asking Hermes: > Use Reply.io to connect exchange account and walk me through the result in plain English. ### 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 Reply.io is connected in the dashboard, that agent calls the same 33 Reply.io 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). ## Reply.io MCP for Hermes Looking for a Reply.io MCP server for Hermes Agent? ClawLink connects Reply.io to Hermes Agent and exposes 33 Reply.io 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 Reply.io integration](https://claw-link.dev/openclaw/reply-io) works the same way. ## What the Hermes Agent Reply.io integration can do 33 Reply.io tools are ready for Hermes Agent once the account is connected. The 28 below are the ones people reach for most; your agent can call all 33. ### 28 of 33 Reply.io tools for Hermes | Tool | What it does | |---|---| | **Connect exchange account** `reply_io_connect_exchange_account` | Initiate OAuth connection for an Exchange email account | | **Connect gmail account** `reply_io_connect_gmail_account` | Initiate Gmail account connection via OAuth | | **Generate ulid** `reply_io_generate_ulid` | Generate ULID | | **Get contact by ID** `reply_io_get_contact_by_id` | Retrieve a contact by ID | | **Get contact status** `reply_io_get_contact_status` | Get contact status | | **Get current user** `reply_io_get_current_user` | Get the current authenticated user's ID | | **Get disconnected email accounts** `reply_io_get_disconnected_email_accounts` | List email accounts that are currently disconnected due to authentication or connection errors | | **Get sequence by ID** `reply_io_get_sequence_by_id` | Retrieve detailed information about a sequence by its ID | | **Get sequence contacts extended** `reply_io_get_sequence_contacts_extended` | Retrieve all contacts enrolled in a sequence with additional details | | **Get sequence step by ID** `reply_io_get_sequence_step_by_id` | Retrieve details of a specific sequence step | | **List contacts basic** `reply_io_list_contacts_basic` | List contacts | | **List email accounts** `reply_io_list_email_accounts` | List all email accounts | | **List lists** `reply_io_list_lists` | List all contact lists | | **List sequence steps** `reply_io_list_sequence_steps` | Retrieve all steps in a sequence | | **List sequences** `reply_io_list_sequences` | Retrieve a paginated list of sequences | | **Search contacts** `reply_io_search_contacts` | Search contacts by email | | **Add contact to sequence** `reply_io_add_contact_to_sequence` | Move an existing contact to a sequence in Reply.io | | **Archive sequence** `reply_io_archive_sequence` | Archive a sequence | | **Create contact** `reply_io_create_contact` | Create a new contact in Reply.io | | **Create sequence step** `reply_io_create_sequence_step` | Add a new step to an existing sequence | | **Pause sequence** `reply_io_pause_sequence` | Pause a running sequence | | **Set contact status** `reply_io_set_contact_status` | Set the status of one or more contacts | | **Start sequence** `reply_io_start_sequence` | Start a sequence | | **Update contact** `reply_io_update_contact` | Update an existing contact's information | | **Update email account** `reply_io_update_email_account` | Update an existing email account with custom SMTP/IMAP settings | | **Clear contact status** `reply_io_clear_contact_status` | Clear statuses from contacts | | **Remove contact from sequence** `reply_io_remove_contact_from_sequence` | Remove a contact from a sequence | | **Remove contacts from sequence** `reply_io_remove_contacts_from_sequence` | Bulk remove multiple contacts from a sequence at once | ## Example prompts **Connect Exchange Account** > Use Reply.io to connect exchange account and walk me through the result in plain English. **Connect Gmail Account** > Use Reply.io to connect gmail account and walk me through the result in plain English. **Generate Ulid** > Use Reply.io to generate ulid and walk me through the result in plain English. **Get Contact By Id** > Pull the relevant data from Reply.io, 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 Reply.io working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Reply.io API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Reply.io 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 Reply.io. | 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 Reply.io actions to the runtime in a format your agent can reliably use. | 33 tools for Reply.io are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Reply.io 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 Reply.io in the browser, and the 33 tools above work from chat. There is no SDK and no config file, and the Reply.io 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 Reply.io 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 Reply.io 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 Reply.io tools Reply.io 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 Reply.io 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. ### Reply.io 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 Reply.io 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 Reply.io integration? Yes. ClawLink is the fastest way to connect Hermes to Reply.io: link your Reply.io account once in the browser and Hermes Agent can call the Reply.io API through 33 ready-made tools — no custom code or token handling. ### How do I connect Reply.io 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 Reply.io in the dashboard and Hermes can use it from the next message — no config files, and the Reply.io key you paste is stored server-side instead of in your environment. ### How long does it take to connect Reply.io to Hermes Agent? About two minutes. Sign in, click Connect next to Reply.io in the dashboard, authenticate, and Hermes Agent can use it from the next chat message. ### Why use ClawLink instead of wiring Reply.io 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 Reply.io working from chat. ### Hermes paired but still can't use Reply.io 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 - [ActiveCampaign tools](https://claw-link.dev/hermes/activecampaign) — Marketing automation, CRM, and email marketing - [Connect 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. - [Mailchimp tools](https://claw-link.dev/hermes/mailchimp) — Create email campaigns and manage audiences