# How to connect Affinity to Hermes Agent (paste one key, 20 tools) > Connect Affinity to Hermes with ClawLink: paste your Affinity key once and 20 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/hermes/affinity Most guides for giving Hermes Agent Affinity 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 Affinity setup: pair once in the browser and your always-on Hermes agent can act on Affinity for you, reading and doing real work on your behalf with no auth, token refresh, or tool wiring to build yourself. **Start here — 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. ## Setup It takes three steps to connect Hermes to Affinity. 1. **Install ClawLink** — add the plugin to Hermes Agent once. 2. **Connect Affinity** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask Hermes Agent in plain English. **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 affinity # connect Affinity (browser OAuth) npx -y @useclawlink/cli actions affinity # list available actions npx -y @useclawlink/cli run affinity --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 Affinity in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Affinity API key once. Verify the connection by asking Hermes: > Pull the relevant data from Affinity, 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 Affinity is connected in the dashboard, that agent calls the same 20 Affinity 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). ## Affinity MCP for Hermes Looking for a Affinity MCP server for Hermes Agent? ClawLink connects Affinity to Hermes Agent and exposes 20 Affinity 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 Affinity integration](https://claw-link.dev/openclaw/affinity) works the same way. ## What the Hermes Agent Affinity integration can do 20 Affinity tools are ready for Hermes Agent once the account is connected. ### All 20 Affinity tools for Hermes | Tool | What it does | |---|---| | **Get a company s list entries** `affinity_get_a_company_s_list_entries` | Summarize company data across all lists, including list-specific fields and metadata like creation date and author. Access requires \'Export data from Lists\' permission. | | **Get a company s lists** `affinity_get_a_company_s_lists` | Returns metadata for all the Lists on which the given Company appears. | | **Get a person s list entries** `affinity_get_a_person_s_list_entries` | Summary: Browse rows for a Person in all Lists, showing field data and entry metadata like creation time and author. Requires \'Export data from Lists\' permission. | | **Get a person s lists** `affinity_get_a_person_s_lists` | Returns metadata for all the Lists on which the given Person appears. | | **Get a single company** `affinity_get_a_single_company` | Retrieve basic company info and specific field data by using `fieldIds` or `fieldTypes` parameters. Multiple fields can be queried. No field data if parameters aren't specified. | | **Get a single opportunity** `affinity_get_a_single_opportunity` | Get basic details about an Opportunity without field data via provided endpoints. Field data requires using specific list entry APIs and the \'Export data from Lists\' permission. | | **Get a single person** `affinity_get_a_single_person` | Use GET `/v2/persons/fields` with `fieldIds` or `fieldTypes` for detailed data; basic info by default. Request multiple fields at once. \'Export All People\' permission needed. | | **Get all companies** `affinity_get_all_companies` | Affinity API allows paginated access to company info and custom fields. Use `fieldIds` or `fieldTypes` to specify data in a request. Retrieve field IDs/Types via GET `/v2/companies/fields`. | | **Get all list entries on a list** `affinity_get_all_list_entries_on_a_list` | Access and export essential data and metadata for Companies, Persons, or Opportunities from a List, specifying data via `fieldIds` or `fieldTypes`. \'Export data from Lists\' permission is necessary. | | **Get all list entries on a saved view** `affinity_get_all_list_entries_on_a_saved_view` | Use the endpoint to access rows in a Saved View with specific filters and selected fields from a web app. | | **Get all opportunities** `affinity_get_all_opportunities` | Pagination through Opportunities in Affinity yields basic info but excludes field data. For field data, use specified GET endpoints. \'Export data from Lists\' permission needed. | | **Get all persons** `affinity_get_all_persons` | The Affinity API offers paginated access to Person data using `fieldIds` or `fieldTypes`. Bulk extraction needs special permissions and supports multiple parameters. | | **Get current user** `affinity_get_current_user` | Returns metadata about the current user | | **Get metadata on a single list** `affinity_get_metadata_on_a_single_list` | Returns metadata on a single List | | **Get metadata on a single list s fields** `affinity_get_metadata_on_a_single_list_s_fields` | Returns metadata on the Fields available on a single List | | **Get metadata on a single saved view** `affinity_get_metadata_on_a_single_saved_view` | Returns metadata on a single Saved View | | **Get metadata on all lists** `affinity_get_metadata_on_all_lists` | Returns metadata on Lists | | **Get metadata on company fields** `affinity_get_metadata_on_company_fields` | Returns metadata on non-list-specific Company Fields | | **Get metadata on person fields** `affinity_get_metadata_on_person_fields` | Returns metadata on non-list-specific Person Fields | | **Get metadata on saved views** `affinity_get_metadata_on_saved_views` | Returns metadata on the Saved Views on a List | ## Example prompts **Get A Company S List Entries** > Pull the relevant data from Affinity, summarize it in plain English, and point out anything that needs attention. **Get A Company S Lists** > Pull the relevant data from Affinity, summarize it in plain English, and point out anything that needs attention. **Get A Person S List Entries** > Pull the relevant data from Affinity, summarize it in plain English, and point out anything that needs attention. **Get A Person S Lists** > Pull the relevant data from Affinity, 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 Affinity working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Affinity API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Affinity 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 Affinity. | 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 Affinity actions to the runtime in a format your agent can reliably use. | 20 tools for Affinity are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Affinity 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 Affinity in the browser, and the 20 tools above work from chat. There is no SDK and no config file, and the Affinity 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 Affinity 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 Affinity 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 Affinity tools Affinity 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 Affinity 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. ### Affinity 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 Affinity 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 Affinity integration? Yes. ClawLink is the fastest way to connect Hermes to Affinity: link your Affinity account once in the browser and Hermes Agent can call the Affinity API through 20 ready-made tools — no custom code or token handling. ### How do I connect Affinity 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 Affinity in the dashboard and Hermes can use it from the next message — no config files, and the Affinity key you paste is stored server-side instead of in your environment. ### How long does it take to connect Affinity to Hermes Agent? About two minutes. Sign in, click Connect next to Affinity in the dashboard, authenticate, and Hermes Agent can use it from the next chat message. ### Why use ClawLink instead of wiring Affinity 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 Affinity working from chat. ### Hermes paired but still can't use Affinity 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 - [CentralStationCRM tools](https://claw-link.dev/hermes/centralstationcrm) — CentralStationCRM is an easy-to-use CRM software focusing on collaboration and long-term customer relationships. - [Salesforce](https://claw-link.dev/hermes/salesforce) — Manage CRM data and workflows - [Connect RepairShopr](https://claw-link.dev/hermes/repairshopr) — RepairShopr is a comprehensive repair shop management software designed to streamline operations, manage customer relationships, and enhance business efficiency.