# How to connect The Org to Hermes Agent (paste one key, 8 tools) > Connect The Org to Hermes with ClawLink: paste your The Org key once and 8 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/hermes/the-org Most guides for giving Hermes Agent The Org 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 The Org setup: pair once in the browser and your always-on Hermes agent can act on The Org 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 The Org. 1. **Install ClawLink** — add the plugin to Hermes Agent once. 2. **Connect The Org** — 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 the-org # connect The Org (browser OAuth) npx -y @useclawlink/cli actions the-org # list available actions npx -y @useclawlink/cli run the-org --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 The Org in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your The Org API key once. Verify the connection by asking Hermes: > Search The Org for what I need, summarize the results, and tell me the next best action. ### 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 The Org is connected in the dashboard, that agent calls the same 8 The Org 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). ## The Org MCP for Hermes Looking for a The Org MCP server for Hermes Agent? ClawLink connects The Org to Hermes Agent and exposes 8 The Org 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 The Org integration](https://claw-link.dev/openclaw/the-org) works the same way. ## What the Hermes Agent The Org integration can do 8 The Org tools are ready for Hermes Agent once the account is connected. ### All 8 The Org tools for Hermes | Tool | What it does | |---|---| | **Estimate position search cost** `the_org_estimate_position_search_cost` | Estimate the credits required for one page of a position search without consuming credits | | **Get current usage** `the_org_get_current_usage` | Return the connected account's current credit allowance, billing interval, reset date | | **Get manager** `the_org_get_manager` | WARNING: Each successful lookup costs 1 credit | | **Get org chart** `the_org_get_org_chart` | Return a company's current v1.2 org chart or board as a flat node list | | **Get usage history** `the_org_get_usage_history` | Return daily or monthly historical usage for one API product over an inclusive date range | | **List people lists** `the_org_list_people_lists` | Return people and lead lists owned by or shared with the connected account, one page at a time | | **Search companies** `the_org_search_companies` | Find companies by name, domain, or email without consuming credits | | **Search positions** `the_org_search_positions` | Search people and positions using company, role, hierarchy, location, funding, and contact | ## Example prompts **Estimate Position Search Cost** > Search The Org for what I need, summarize the results, and tell me the next best action. **Get Current Usage** > Pull the relevant data from The Org, summarize it in plain English, and point out anything that needs attention. **Get Manager** > Pull the relevant data from The Org, summarize it in plain English, and point out anything that needs attention. **Get Org Chart** > Pull the relevant data from The Org, 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 The Org working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the The Org API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected The Org 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 The Org. | 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 The Org actions to the runtime in a format your agent can reliably use. | 8 tools for The Org are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes The Org 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 The Org in the browser, and the 8 tools above work from chat. There is no SDK and no config file, and the The Org 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 The Org 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 The Org 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 The Org tools The Org 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 The Org 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. ### The Org 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 The Org 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 The Org integration? Yes. ClawLink is the fastest way to connect Hermes to The Org: link your The Org account once in the browser and Hermes Agent can call the The Org API through 8 ready-made tools — no custom code or token handling. ### How do I connect The Org 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 The Org in the dashboard and Hermes can use it from the next message — no config files, and the The Org key you paste is stored server-side instead of in your environment. ### How long does it take to connect The Org to Hermes Agent? About two minutes. Sign in, click Connect next to The Org in the dashboard, authenticate, and Hermes Agent can use it from the next chat message. ### Why use ClawLink instead of wiring The Org 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 The Org working from chat. ### Hermes paired but still can't use The Org 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 HubSpot integration](https://claw-link.dev/hermes/hubspot) — Manage contacts, deals, and pipelines - [CentralStationCRM](https://claw-link.dev/hermes/centralstationcrm) — CentralStationCRM is an easy-to-use CRM software focusing on collaboration and long-term customer relationships. - [Hermes Salesforce integration](https://claw-link.dev/hermes/salesforce) — Manage CRM data and workflows