# How to connect Productlane to Hermes Agent (paste one key, 39 tools) > Connect Productlane to Hermes with ClawLink: paste your Productlane key once and 39 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/hermes/productlane Most guides for giving Hermes Agent Productlane 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 Productlane setup: pair once in the browser and your always-on Hermes agent can act on Productlane 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 Productlane. 1. **Install ClawLink** — add the plugin to Hermes Agent once. 2. **Connect Productlane** — 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 productlane # connect Productlane (browser OAuth) npx -y @useclawlink/cli actions productlane # list available actions npx -y @useclawlink/cli run productlane --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 Productlane in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Productlane API key once. Verify the connection by asking Hermes: > Use Productlane to enable widget 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 Productlane is connected in the dashboard, that agent calls the same 39 Productlane 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). ## Productlane MCP for Hermes Looking for a Productlane MCP server for Hermes Agent? ClawLink connects Productlane to Hermes Agent and exposes 39 Productlane 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 Productlane integration](https://claw-link.dev/openclaw/productlane) works the same way. ## What the Hermes Agent Productlane integration can do 39 Productlane 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 39. ### 30 of 39 Productlane tools for Hermes | Tool | What it does | |---|---| | **Enable widget** `productlane_enable_widget` | Enable the Productlane widget | | **Get changelog** `productlane_get_changelog` | Retrieve a published changelog by ID from Productlane | | **Get company** `productlane_get_company` | Retrieve a company by its unique ID | | **Get contact** `productlane_get_contact` | Retrieve a contact by ID or email from Productlane | | **Get help center article** `productlane_get_help_center_article` | Retrieve a help center article by its ID | | **Get insight** `productlane_get_insight` | Retrieve an insight/thread by its ID | | **Get issue** `productlane_get_issue` | Retrieve a specific issue by its ID from a workspace | | **Get linear options** `productlane_get_linear_options` | Retrieve available Linear customer statuses and tiers for your workspace | | **Get project** `productlane_get_project` | Retrieve a project by its ID from a workspace | | **Get workspace** `productlane_get_workspace` | Fetch workspace details by ID | | **List changelogs** `productlane_list_changelogs` | List all published changelogs for a workspace by ID | | **List companies** `productlane_list_companies` | List all companies in Productlane | | **List contacts** `productlane_list_contacts` | Retrieve all contacts for your workspace | | **List help center articles** `productlane_list_help_center_articles` | List all help center articles for a specific workspace | | **List insights** `productlane_list_insights` | List all threads/insights for your workspace with optional filtering | | **List issues** `productlane_list_issues` | Retrieve all issues from a Productlane workspace | | **List members** `productlane_list_members` | Retrieve all members of your workspace with their roles and user information | | **List projects** `productlane_list_projects` | Retrieve all projects within a workspace | | **Widget close** `productlane_widget_close` | Close the Productlane widget | | **Widget disable** `productlane_widget_disable` | Disable the Productlane widget across the entire page | | **Widget off event** `productlane_widget_off_event` | Remove a previously registered widget event listener | | **Widget on event** `productlane_widget_on_event` | Register a listener for Productlane widget events | | **Widget open** `productlane_widget_open` | Generate a JavaScript snippet that opens the Productlane widget | | **Widget open docs** `productlane_widget_open_docs` | Open a specific docs article in the Productlane widget | | **Widget toggle** `productlane_widget_toggle` | Toggle the Productlane widget between open and closed states | | **Create changelog** `productlane_create_changelog` | Create a new changelog entry in Productlane | | **Create company** `productlane_create_company` | Create a new company in Productlane | | **Create contact** `productlane_create_contact` | Create a new contact in your Productlane workspace with optional company linking | | **Create feedback** `productlane_create_feedback` | Create new feedback in Productlane | | **Create insight** `productlane_create_insight` | Create a new insight/thread in Productlane workspace | ## Example prompts **Enable Widget** > Use Productlane to enable widget and walk me through the result in plain English. **Get Changelog** > Pull the relevant data from Productlane, summarize it in plain English, and point out anything that needs attention. **Get Company** > Pull the relevant data from Productlane, summarize it in plain English, and point out anything that needs attention. **Get Contact** > Pull the relevant data from Productlane, 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 Productlane working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Productlane API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Productlane 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 Productlane. | 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 Productlane actions to the runtime in a format your agent can reliably use. | 39 tools for Productlane are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Productlane 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 Productlane in the browser, and the 39 tools above work from chat. There is no SDK and no config file, and the Productlane 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 Productlane 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 Productlane 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 Productlane tools Productlane 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 Productlane 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. ### Productlane 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 Productlane 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 Productlane integration? Yes. ClawLink is the fastest way to connect Hermes to Productlane: link your Productlane account once in the browser and Hermes Agent can call the Productlane API through 39 ready-made tools — no custom code or token handling. ### How do I connect Productlane 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 Productlane in the dashboard and Hermes can use it from the next message — no config files, and the Productlane key you paste is stored server-side instead of in your environment. ### How long does it take to connect Productlane to Hermes Agent? About two minutes. Sign in, click Connect next to Productlane in the dashboard, authenticate, and Hermes Agent can use it from the next chat message. ### Why use ClawLink instead of wiring Productlane 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 Productlane working from chat. ### Hermes paired but still can't use Productlane 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 - [Zendesk](https://claw-link.dev/hermes/zendesk) — Manage support tickets, macros, users, and organizations - [Gleap tools](https://claw-link.dev/hermes/gleap) — Gleap is an all-in-one customer feedback tool for apps and websites, enabling direct communication with users to build better software by discovering their everyday pain points. - [Connect Freshdesk](https://claw-link.dev/hermes/freshdesk) — Handle support tickets, contacts, and helpdesk operations