# How to connect ReferralRock to Hermes Agent (paste one key, 32 tools) > Connect ReferralRock to Hermes with ClawLink: paste your ReferralRock key once and 32 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/hermes/referralrock Most guides for giving Hermes Agent ReferralRock 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 ReferralRock setup: pair once in the browser and your always-on Hermes agent can act on ReferralRock 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 ReferralRock. 1. **Install ClawLink** — add the plugin to Hermes Agent once. 2. **Connect ReferralRock** — 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 referralrock # connect ReferralRock (browser OAuth) npx -y @useclawlink/cli actions referralrock # list available actions npx -y @useclawlink/cli run referralrock --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 ReferralRock in the [ClawLink dashboard](https://claw-link.dev/dashboard) — enter your ReferralRock account details once. Verify the connection by asking Hermes: > Pull the relevant data from ReferralRock, 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 ReferralRock is connected in the dashboard, that agent calls the same 32 ReferralRock 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). ## ReferralRock MCP for Hermes Looking for a ReferralRock MCP server for Hermes Agent? ClawLink connects ReferralRock to Hermes Agent and exposes 32 ReferralRock 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 ReferralRock integration](https://claw-link.dev/openclaw/referralrock) works the same way. ## What the Hermes Agent ReferralRock integration can do 32 ReferralRock tools are ready for Hermes Agent once the account is connected. The 27 below are the ones people reach for most; your agent can call all 32. ### 27 of 32 ReferralRock tools for Hermes | Tool | What it does | |---|---| | **Get email getunsubscribed** `referralrock_get_email_getunsubscribed` | Check if an email address is unsubscribed from communications | | **Get hooks history eventname** `referralrock_get_hooks_history_eventname` | Retrieve webhook history for a specific event | | **Get member stats get single** `referralrock_get_member_stats_get_single` | Retrieve comprehensive statistics for a single member from ReferralRock | | **Get members** `referralrock_get_members` | List program members with filtering and pagination | | **Get payouts ID** `referralrock_get_payouts_id` | Get payout details by ID | | **Get payouts pending** `referralrock_get_payouts_pending` | Get pending payouts for a member or recipient | | **Get payouts transactions** `referralrock_get_payouts_transactions` | Get payout transaction history for referral program participants | | **Get program getsingle** `referralrock_get_program_getsingle` | Retrieve a single referral program by name | | **Get programs** `referralrock_get_programs` | List all referral programs in ReferralRock | | **Get referral single** `referralrock_get_referral_single` | Retrieve a single referral by email, ID, or external ID | | **Get referrals** `referralrock_get_referrals` | List referrals with filtering and pagination options | | **Get rewardrules** `referralrock_get_rewardrules` | Get reward rules for a program | | **Get rewards** `referralrock_get_rewards` | List rewards with optional filtering and pagination | | **Post member access URLS** `referralrock_post_member_access_urls` | Generate member access URLs for custom share experience or secure portal embedding | | **Post email removeunsubscribe** `referralrock_post_email_removeunsubscribe` | Remove an email address from the unsubscribe list | | **Post email unsubscribe** `referralrock_post_email_unsubscribe` | Unsubscribe an email address from the ReferralRock mailing list | | **Post hooks** `referralrock_post_hooks` | Create or update a webhook subscription for event notifications | | **Post invitefeed** `referralrock_post_invitefeed` | Create an invite feed entry for automatic invitations | | **Post invitefeeds** `referralrock_post_invitefeeds` | Create multiple invite feed entries for automatic invites in ReferralRock | | **Post members** `referralrock_post_members` | Create a new member and add them to a referral program | | **Post referral update** `referralrock_post_referral_update` | Update referral details in a referral program | | **Post referralaction** `referralrock_post_referralaction` | Create a referral action for processing recurring rewards | | **Post referrals** `referralrock_post_referrals` | Create a new referral in ReferralRock based on a member's referral code | | **Post rewards issue** `referralrock_post_rewards_issue` | Issue a reward to a member in the Referral Rock system | | **Post members remove** `referralrock_post_members_remove` | Remove members from a referral program | | **Post referral remove** `referralrock_post_referral_remove` | Remove referrals from a referral program | | **Post rewards remove** `referralrock_post_rewards_remove` | Remove rewards from members or referrals of a referral program | ## Example prompts **Get Email Getunsubscribed** > Pull the relevant data from ReferralRock, summarize it in plain English, and point out anything that needs attention. **Get Hooks History Eventname** > Pull the relevant data from ReferralRock, summarize it in plain English, and point out anything that needs attention. **Get Member Stats Get Single** > Pull the relevant data from ReferralRock, summarize it in plain English, and point out anything that needs attention. **Get Members** > Pull the relevant data from ReferralRock, summarize it in plain English, and point out anything that needs attention. ## ClawLink vs. building it yourself The alternative to ClawLink is usually manual credential 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 ReferralRock working from chat. | | Manual | ClawLink | |---|---|---| | **Setup flow** | Collect and store the right ReferralRock credentials yourself, then keep the account mapping and request format correct. | ClawLink keeps the setup in one hosted flow so non-technical users can link ReferralRock without custom integration screens. | | **Ongoing maintenance** | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for ReferralRock. | 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 ReferralRock actions to the runtime in a format your agent can reliably use. | 32 tools for ReferralRock are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes ReferralRock 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 ReferralRock in the browser, and the 32 tools above work from chat. There is no SDK and no config file, and the ReferralRock 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 ReferralRock 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 ReferralRock 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 ReferralRock tools ReferralRock 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 ReferralRock 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. ### ReferralRock 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. ### The setup form accepts credentials but calls still fail Re-enter the credentials carefully and verify the account-level permissions for ReferralRock. Basic and token-based integrations tend to fail on formatting mistakes or limited account roles. ### Is there a Hermes Agent ReferralRock integration? Yes. ClawLink is the fastest way to connect Hermes to ReferralRock: link your ReferralRock account once in the browser and Hermes Agent can call the ReferralRock API through 32 ready-made tools — no custom code or token handling. ### How do I connect ReferralRock 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 ReferralRock in the dashboard and Hermes can use it from the next message — no config files, and the ReferralRock key you paste is stored server-side instead of in your environment. ### How long does it take to connect ReferralRock to Hermes Agent? About two minutes. Sign in, click Connect next to ReferralRock in the dashboard, authenticate, and Hermes Agent can use it from the next chat message. ### Why use ClawLink instead of wiring ReferralRock up myself? The alternative to ClawLink is usually manual credential 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 ReferralRock working from chat. ### Hermes paired but still can't use ReferralRock 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](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. - [Connect Mailchimp](https://claw-link.dev/hermes/mailchimp) — Create email campaigns and manage audiences