# How to connect Loops.so to Hermes Agent (paste one key, 11 tools) > Connect Loops.so to Hermes with ClawLink: paste your Loops.so key once and 11 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/hermes/loops-so Most guides for giving Hermes Agent Loops.so 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 Loops.so setup: pair once in the browser and your always-on Hermes agent can act on Loops.so 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 Loops.so. 1. **Install ClawLink** — add the plugin to Hermes Agent once. 2. **Connect Loops.so** — 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 loops-so # connect Loops.so (browser OAuth) npx -y @useclawlink/cli actions loops-so # list available actions npx -y @useclawlink/cli run loops-so --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 Loops.so in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Loops.so API key once. Verify the connection by asking Hermes: > Use Loops.so to find contact 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 Loops.so is connected in the dashboard, that agent calls the same 11 Loops.so 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). ## Loops.so MCP for Hermes Looking for a Loops.so MCP server for Hermes Agent? ClawLink connects Loops.so to Hermes Agent and exposes 11 Loops.so 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 Loops.so integration](https://claw-link.dev/openclaw/loops-so) works the same way. ## What the Hermes Agent Loops.so integration can do 11 Loops.so tools are ready for Hermes Agent once the account is connected. The 10 below are the ones people reach for most; your agent can call all 11. ### 10 of 11 Loops.so tools for Hermes | Tool | What it does | |---|---| | **Find contact** `loops_so_find_contact` | Search for a contact by email or userId | | **Get contact properties** `loops_so_get_contact_properties` | Retrieve a list of your account's contact properties from Loops.so | | **Get dedicated sending ips** `loops_so_get_dedicated_sending_ips` | Retrieve a list of Loops' dedicated sending IP addresses | | **Get mailing lists** `loops_so_get_mailing_lists` | Retrieve all mailing lists associated with your Loops account | | **List transactional emails** `loops_so_list_transactional_emails` | Retrieve a list of published transactional emails | | **Test API key** `loops_so_test_api_key` | Test API key validity and retrieve team information | | **Create contact** `loops_so_create_contact` | Add a new contact to your Loops audience | | **Create contact property** `loops_so_create_contact_property` | Add a custom contact property to your Loops team | | **Send event** `loops_so_send_event` | Send events to trigger emails in Loops | | **Update contact** `loops_so_update_contact` | Update an existing contact by email or userId | ## Example prompts **Find Contact** > Use Loops.so to find contact and walk me through the result in plain English. **Get Contact Properties** > Pull the relevant data from Loops.so, summarize it in plain English, and point out anything that needs attention. **Get Dedicated Sending Ips** > Pull the relevant data from Loops.so, summarize it in plain English, and point out anything that needs attention. **Get Mailing Lists** > Pull the relevant data from Loops.so, 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 Loops.so working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Loops.so API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Loops.so 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 Loops.so. | 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 Loops.so actions to the runtime in a format your agent can reliably use. | 11 tools for Loops.so are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Loops.so 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 Loops.so in the browser, and the 11 tools above work from chat. There is no SDK and no config file, and the Loops.so 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 Loops.so 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 Loops.so 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 Loops.so tools Loops.so 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 Loops.so 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. ### Loops.so 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 Loops.so 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 Loops.so integration? Yes. ClawLink is the fastest way to connect Hermes to Loops.so: link your Loops.so account once in the browser and Hermes Agent can call the Loops.so API through 11 ready-made tools — no custom code or token handling. ### How do I connect Loops.so 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 Loops.so in the dashboard and Hermes can use it from the next message — no config files, and the Loops.so key you paste is stored server-side instead of in your environment. ### How long does it take to connect Loops.so to Hermes Agent? About two minutes. Sign in, click Connect next to Loops.so in the dashboard, authenticate, and Hermes Agent can use it from the next chat message. ### Why use ClawLink instead of wiring Loops.so 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 Loops.so working from chat. ### Hermes paired but still can't use Loops.so 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 - [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