# How to connect ActiveMerge to Hermes Agent (paste one key, 13 tools) > Connect ActiveMerge to Hermes with ClawLink: paste your ActiveMerge key once and 13 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/hermes/active-merge Most guides for giving Hermes Agent ActiveMerge 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 ActiveMerge setup: pair once in the browser and your always-on Hermes agent can act on ActiveMerge 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 ActiveMerge. 1. **Install ClawLink** — add the plugin to Hermes Agent once. 2. **Connect ActiveMerge** — 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 active-merge # connect ActiveMerge (browser OAuth) npx -y @useclawlink/cli actions active-merge # list available actions npx -y @useclawlink/cli run active-merge --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 ActiveMerge in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your ActiveMerge API key once. Verify the connection by asking Hermes: > Pull the relevant data from ActiveMerge, 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 ActiveMerge is connected in the dashboard, that agent calls the same 13 ActiveMerge 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). ## ActiveMerge MCP for Hermes Looking for a ActiveMerge MCP server for Hermes Agent? ClawLink connects ActiveMerge to Hermes Agent and exposes 13 ActiveMerge 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 ActiveMerge integration](https://claw-link.dev/openclaw/active-merge) works the same way. ## What the Hermes Agent ActiveMerge integration can do 13 ActiveMerge tools are ready for Hermes Agent once the account is connected. ### All 13 ActiveMerge tools for Hermes | Tool | What it does | |---|---| | **Get credits** `active_merge_get_credits` | Get total, used, remaining, plan, and prepaid ActiveMerge credits before running | | **Get document generations** `active_merge_get_document_generations` | Get one document-generation job by ID, or list and filter generation history when no job ID is | | **Get document template placeholders** `active_merge_get_document_template_placeholders` | Return the case-sensitive placeholder names required by one document template | | **Get file download URL** `active_merge_get_file_download_url` | Create a temporary download URL for a file in ActiveMerge cloud storage | | **Get image generation** `active_merge_get_image_generation` | Get an image-generation job's progress, credit usage, errors, and temporary ZIP download URL | | **Get image templates** `active_merge_get_image_templates` | List image templates and basic placeholders, or get complete dimensions, positions, defaults | | **Get workflows** `active_merge_get_workflows` | List available ActiveMerge workflows, or return the case-sensitive placeholders for one | | **List document templates** `active_merge_list_document_templates` | List document templates available to the connected ActiveMerge account, including the unique | | **List files** `active_merge_list_files` | List the immediate files and folders at the ActiveMerge cloud-storage root, or directly inside | | **Generate document** `active_merge_generate_document` | Start asynchronous document generation from a template and case-sensitive placeholder data | | **Generate images** `active_merge_generate_images` | Start an asynchronous image-generation job from inline JSON records | | **Generate workflow documents** `active_merge_generate_workflow_documents` | Generate documents for every template in an ActiveMerge workflow using case-sensitive | | **Save generated files** `active_merge_save_generated_files` | Save non-expired output from a completed document-generation job to permanent ActiveMerge cloud | ## Example prompts **Get Credits** > Pull the relevant data from ActiveMerge, summarize it in plain English, and point out anything that needs attention. **Get Document Generations** > Pull the relevant data from ActiveMerge, summarize it in plain English, and point out anything that needs attention. **Get Document Template Placeholders** > Pull the relevant data from ActiveMerge, summarize it in plain English, and point out anything that needs attention. **Get File Download Url** > Pull the relevant data from ActiveMerge, 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 ActiveMerge working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the ActiveMerge API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected ActiveMerge 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 ActiveMerge. | 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 ActiveMerge actions to the runtime in a format your agent can reliably use. | 13 tools for ActiveMerge are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes ActiveMerge 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 ActiveMerge in the browser, and the 13 tools above work from chat. There is no SDK and no config file, and the ActiveMerge 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 ActiveMerge 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 ActiveMerge 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 ActiveMerge tools ActiveMerge 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 ActiveMerge 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. ### ActiveMerge 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 ActiveMerge 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 ActiveMerge integration? Yes. ClawLink is the fastest way to connect Hermes to ActiveMerge: link your ActiveMerge account once in the browser and Hermes Agent can call the ActiveMerge API through 13 ready-made tools — no custom code or token handling. ### How do I connect ActiveMerge 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 ActiveMerge in the dashboard and Hermes can use it from the next message — no config files, and the ActiveMerge key you paste is stored server-side instead of in your environment. ### How long does it take to connect ActiveMerge to Hermes Agent? About two minutes. Sign in, click Connect next to ActiveMerge in the dashboard, authenticate, and Hermes Agent can use it from the next chat message. ### Why use ClawLink instead of wiring ActiveMerge 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 ActiveMerge working from chat. ### Hermes paired but still can't use ActiveMerge 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 - [Trello](https://claw-link.dev/hermes/trello) — Manage boards, lists, and cards - [Moco](https://claw-link.dev/hermes/moco) — MOCO is a business management software offering project management, time tracking, and invoicing solutions. - [ClickUp](https://claw-link.dev/hermes/clickup) — Manage tasks, docs, goals, and sprints