# How to connect Heyreach to Hermes Agent (paste one key, 19 tools) > Connect Heyreach to Hermes with ClawLink: paste your Heyreach key once and 19 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/hermes/heyreach Most guides for giving Hermes Agent Heyreach 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 Heyreach setup: pair once in the browser and your always-on Hermes agent can act on Heyreach 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 Heyreach. 1. **Install ClawLink** — add the plugin to Hermes Agent once. 2. **Connect Heyreach** — 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 heyreach # connect Heyreach (browser OAuth) npx -y @useclawlink/cli actions heyreach # list available actions npx -y @useclawlink/cli run heyreach --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 Heyreach in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Heyreach API key once. Verify the connection by asking Hermes: > Use Heyreach to check api key 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 Heyreach is connected in the dashboard, that agent calls the same 19 Heyreach 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). ## Heyreach MCP for Hermes Looking for a Heyreach MCP server for Hermes Agent? ClawLink connects Heyreach to Hermes Agent and exposes 19 Heyreach 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 Heyreach integration](https://claw-link.dev/openclaw/heyreach) works the same way. ## What the Hermes Agent Heyreach integration can do 19 Heyreach tools are ready for Hermes Agent once the account is connected. The 18 below are the ones people reach for most; your agent can call all 19. ### 18 of 19 Heyreach tools for Hermes | Tool | What it does | |---|---| | **Check API key** `heyreach_check_api_key` | Check if the API key is valid | | **Get all campaigns** `heyreach_get_all_campaigns` | Retrieve all campaigns | | **Get all leads** `heyreach_get_all_leads` | Retrieve all leads in a HeyReach list | | **Get all linkedin accounts** `heyreach_get_all_linkedin_accounts` | Retrieve all LinkedIn accounts | | **Get all lists** `heyreach_get_all_lists` | Retrieve all lists | | **Get all webhooks** `heyreach_get_all_webhooks` | Retrieve all webhooks | | **Get companies from list** `heyreach_get_companies_from_list` | Get companies from a company list | | **Get conversations v2** `heyreach_get_conversations_v2` | Retrieve paginated LinkedIn conversations with advanced filters | | **Get lead** `heyreach_get_lead` | Retrieve detailed information for a lead by profile URL | | **Get lists for lead** `heyreach_get_lists_for_lead` | Retrieve all lists that contain a specific lead by profile URL | | **Get my network for sender** `heyreach_get_my_network_for_sender` | Get the LinkedIn network for a specified sender account | | **Get overall stats** `heyreach_get_overall_stats` | Get overall statistics for LinkedIn accounts and campaigns | | **Get webhook by ID** `heyreach_get_webhook_by_id` | Retrieve a webhook by its ID | | **Add leads to list v2** `heyreach_add_leads_to_list_v2` | Add leads to a lead list in HeyReach for LinkedIn campaigns | | **Create empty list** `heyreach_create_empty_list` | Create an empty list | | **Create tags** `heyreach_create_tags` | Create one or multiple tags for your workspace | | **Create webhook** `heyreach_create_webhook` | Create a new webhook | | **Update webhook** `heyreach_update_webhook` | Update an existing webhook’s configuration | ## Example prompts **Check Api Key** > Use Heyreach to check api key and walk me through the result in plain English. **Get All Campaigns** > Pull the relevant data from Heyreach, summarize it in plain English, and point out anything that needs attention. **Get All Leads** > Pull the relevant data from Heyreach, summarize it in plain English, and point out anything that needs attention. **Get All Linkedin Accounts** > Pull the relevant data from Heyreach, 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 Heyreach working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Heyreach API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Heyreach 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 Heyreach. | 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 Heyreach actions to the runtime in a format your agent can reliably use. | 19 tools for Heyreach are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Heyreach 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 Heyreach in the browser, and the 19 tools above work from chat. There is no SDK and no config file, and the Heyreach 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 Heyreach 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 Heyreach 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 Heyreach tools Heyreach 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 Heyreach 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. ### Heyreach 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 Heyreach 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 Heyreach integration? Yes. ClawLink is the fastest way to connect Hermes to Heyreach: link your Heyreach account once in the browser and Hermes Agent can call the Heyreach API through 19 ready-made tools — no custom code or token handling. ### How do I connect Heyreach 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 Heyreach in the dashboard and Hermes can use it from the next message — no config files, and the Heyreach key you paste is stored server-side instead of in your environment. ### How long does it take to connect Heyreach to Hermes Agent? About two minutes. Sign in, click Connect next to Heyreach in the dashboard, authenticate, and Hermes Agent can use it from the next chat message. ### Why use ClawLink instead of wiring Heyreach 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 Heyreach working from chat. ### Hermes paired but still can't use Heyreach 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 - [Hermes Benchmark Email integration](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](https://claw-link.dev/hermes/mailchimp) — Create email campaigns and manage audiences