# How to connect Raisely to Hermes Agent (paste one key, 61 tools) > Connect Raisely to Hermes with ClawLink: paste your Raisely key once and 61 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/hermes/raisely Most guides for giving Hermes Agent Raisely 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 Raisely setup: pair once in the browser and your always-on Hermes agent can act on Raisely 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 Raisely. 1. **Install ClawLink** — add the plugin to Hermes Agent once. 2. **Connect Raisely** — 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 raisely # connect Raisely (browser OAuth) npx -y @useclawlink/cli actions raisely # list available actions npx -y @useclawlink/cli run raisely --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 Raisely in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Raisely API key once. Verify the connection by asking Hermes: > Use Raisely to check profile url 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 Raisely is connected in the dashboard, that agent calls the same 61 Raisely 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). ## Raisely MCP for Hermes Looking for a Raisely MCP server for Hermes Agent? ClawLink connects Raisely to Hermes Agent and exposes 61 Raisely 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 Raisely integration](https://claw-link.dev/openclaw/raisely) works the same way. ## What the Hermes Agent Raisely integration can do 61 Raisely tools are ready for Hermes Agent once the account is connected. The 30 below are the ones people reach for most; your agent can call all 61. ### 30 of 61 Raisely tools for Hermes | Tool | What it does | |---|---| | **Check profile URL** `raisely_check_profile_url` | Verify if a profile URL is available for a given campaign and get suggestions if unavailable | | **Check user** `raisely_check_user` | Check if a user is already registered to a campaign with a specific email address | | **Get API docs** `raisely_get_api_docs` | Retrieve a summary of the Raisely API documentation including metadata and sample endpoints | | **Get authenticate** `raisely_get_authenticate` | Authenticate a token to confirm it's valid and check the logged-in user | | **Get available events** `raisely_get_available_events` | Retrieve a list of available Raisely webhook events | | **Get campaign** `raisely_get_campaign` | Retrieve a specific campaign from Raisely | | **Get campaign profile** `raisely_get_campaign_profile` | Retrieve the campaign profile for a Raisely campaign | | **Get campaigns** `raisely_get_campaigns` | Retrieve a paginated list of campaigns from Raisely | | **Get campaigns profiles** `raisely_get_campaigns_profiles` | List all fundraising profiles in a Raisely campaign | | **Get exercise log** `raisely_get_exercise_log` | Retrieve a specific exercise log by UUID from the Raisely platform | | **Get interaction** `raisely_get_interaction` | Retrieve a specific interaction from Raisely by its UUID | | **Get post** `raisely_get_post` | Retrieve a specific post from the Raisely fundraising platform | | **Get profile** `raisely_get_profile` | Retrieves a specific fundraising profile from Raisely by UUID or path | | **Get profiles** `raisely_get_profiles` | Retrieves a paginated list of fundraising profiles for a Raisely campaign | | **Get user** `raisely_get_user` | Retrieve a specific user from Raisely by UUID | | **Get user profiles** `raisely_get_user_profiles` | Retrieve all profiles associated with a specific user | | **Get users** `raisely_get_users` | Retrieve a paginated list of users from the Raisely platform | | **List campaign donations** `raisely_list_campaign_donations` | Retrieve donations from a specific campaign in Raisely | | **List campaign products** `raisely_list_campaign_products` | Retrieves all products available in a Raisely campaign | | **List campaign subscriptions** `raisely_list_campaign_subscriptions` | List all subscriptions for a specific Raisely campaign | | **List donations** `raisely_list_donations` | Retrieve donations from Raisely | | **List exercise logs** `raisely_list_exercise_logs` | Retrieve exercise logs from Raisely | | **List interaction categories** `raisely_list_interaction_categories` | Retrieve all interaction categories in the organisation from Raisely | | **List interactions** `raisely_list_interactions` | Retrieve all interactions from Raisely | | **List orders** `raisely_list_orders` | Retrieve all orders in a campaign from Raisely | | **List posts** `raisely_list_posts` | Retrieve a list of posts you've previously created on Raisely | | **List profile donations** `raisely_list_profile_donations` | Retrieves a paginated list of donations for a specific fundraising profile from Raisely | | **List profile members** `raisely_list_profile_members` | Retrieves a paginated list of all members belonging to a team profile in Raisely | | **List profile posts** `raisely_list_profile_posts` | List all posts created by a specific profile in Raisely | | **List promo codes** `raisely_list_promo_codes` | Retrieve all promo codes in a campaign from Raisely | ## Example prompts **Check Profile Url** > Use Raisely to check profile url and walk me through the result in plain English. **Check User** > Use Raisely to check user and walk me through the result in plain English. **Get Api Docs** > Pull the relevant data from Raisely, summarize it in plain English, and point out anything that needs attention. **Get Authenticate** > Pull the relevant data from Raisely, 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 Raisely working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Raisely API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Raisely 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 Raisely. | 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 Raisely actions to the runtime in a format your agent can reliably use. | 61 tools for Raisely are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Raisely 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 Raisely in the browser, and the 61 tools above work from chat. There is no SDK and no config file, and the Raisely 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 Raisely 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 Raisely 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 Raisely tools Raisely 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 Raisely 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. ### Raisely 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 Raisely 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 Raisely integration? Yes. ClawLink is the fastest way to connect Hermes to Raisely: link your Raisely account once in the browser and Hermes Agent can call the Raisely API through 61 ready-made tools — no custom code or token handling. ### How do I connect Raisely 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 Raisely in the dashboard and Hermes can use it from the next message — no config files, and the Raisely key you paste is stored server-side instead of in your environment. ### How long does it take to connect Raisely to Hermes Agent? About two minutes. Sign in, click Connect next to Raisely in the dashboard, authenticate, and Hermes Agent can use it from the next chat message. ### Why use ClawLink instead of wiring Raisely 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 Raisely working from chat. ### Hermes paired but still can't use Raisely 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 - [Hermes GitHub integration](https://claw-link.dev/hermes/github) — Manage repositories, issues, pull requests, and workflows - [Connect PagerDuty](https://claw-link.dev/hermes/pagerduty) — Manage incidents, on-call schedules, and services - [SafetyCulture tools](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.