How to connect HubSpot to Hermes Agent

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.

Reconnect HubSpot from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded.

HubSpot 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 HubSpot 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.

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.

HubSpot's own community threads answer this with scope checking, and their failure modes are different from the generic causes: the connected user may lack a scope the tool needs, such as crm.objects.contacts.write, or the object type may be tier-gated so the portal's plan does not include it, or the request hits field-level permissions on the user's role. Some tools also require the user to be a Super Admin, for example for marketplace app access. Walk the checklist in that order, and keep the placeholder trap in mind: an id like YOUR_ID from documentation 403s on the write even when the scope is fine, so have the agent search or list first and retry with a real id. If the scope itself is the problem, the fix is a HubSpot-side permission or plan change, not a reconnect.

The fan-out queries for this page keep rewriting the question this way, so the checklist: start a fresh chat so the runtime reloads the tool catalog, because a stale catalog can surface as a tool-level failure. Then check the id the agent sent, because placeholder ids from documentation are the most common cause of a 403 on an otherwise healthy connection. Then check portal permissions for the scopes the failing tool needs, including whether the object type is included in the portal's plan. Reconnect last, and only after confirming the token side, because HubSpot can also force re-authorization when the app's scopes change.

The query space answers this with local developer setup: npm install -g @hubspot/cli, run hsmcp setup, and edit IDE config files. A hosted connection has no local MCP server, so none of those errors or fixes exist here: there is no CLI to install and no config file for a missing tool to come from. If a HubSpot tool is missing from your agent's catalog, reconnect HubSpot from the dashboard and start a fresh chat so the runtime reloads the tool list.

Try reconnecting HubSpot and complete the consent flow in the same browser session. Partial OAuth approvals or switching accounts mid-flow can leave the connection incomplete.

Yes. ClawLink is the fastest way to connect Hermes to HubSpot: link your HubSpot account once in the browser and Hermes Agent can call the HubSpot API through 224 ready-made tools — no custom code or token handling.

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 HubSpot in the dashboard and Hermes can use it from the next message — no config files or API keys to manage.

About two minutes. Sign in, click Connect next to HubSpot in the dashboard, authenticate, and Hermes Agent can use it from the next chat message.

The alternative to ClawLink is usually manual OAuth app 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 HubSpot working from chat.

No. HubSpot has deprecated legacy API keys, so the manual path is now a private app: Settings, then Integrations, then Private Apps, create an app, pick scopes, and copy the token it shows. ClawLink replaces all of that with hosted OAuth. You connect HubSpot in the browser, the scopes come from the OAuth consent rather than a hand-built scope list, and there is no token for you to create, rotate, or store anywhere.

Composio's own walkthrough is developer setup: pipe their install script into a shell, have Hermes authenticate, and add a Connect MCP block to ~/.hermes/config.yaml. ClawLink is the hosted version of that idea with the config file removed: you install the plugin once, connect HubSpot in the dashboard, and the 224 tools are callable from the next message. If you already run Composio and want its MCP config, that path works; if you want the same capability without a config file, this is the page.

HubSpot's own security pages and the governance writeups answer yes with caveats, and the caveats matter here. The connection uses OAuth consent, so the agent can only act with the permissions of the portal and user you authenticate with, and you can revoke it from the ClawLink dashboard at any time. HubSpot's published position is that its platform does not train on customer data; what the agent does with your CRM records is governed by the scopes and by your own instructions, so constrain what it may read and write just as you would any staff member with portal access.

HubSpot's built-in Breeze agents answer the no-API-key story inside HubSpot: they are native to the portal, plan-gated, and designed around HubSpot workflows. They do not give an external runtime like Hermes Agent an API surface, which is the gap this connection fills. If your agent needs to mix CRM data with your other connected tools in one conversation, it needs a HubSpot connection it can call directly.

224 tools, counted from the generated manifest on 2026-08-02. Some index snippets still show an older copy that says 15; the page and its tool list are current at 224, and the agent can call all of them. The 30 featured on the page are the most-used CRM operations.

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.