How to connect HighLevel 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 HighLevel from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded.

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

The engines teach three causes, all token-shape: a valid token restricted to the wrong location, which shows up as mismatched location IDs; a company-level token used against location-level endpoints; and missing OAuth scopes. Their fix is "regenerate your PIT scopes", which has no equivalent in a hosted flow, because the permission comes from the OAuth grant, not from a token you maintain. The hosted equivalents: confirm the HighLevel account and location the connection was approved with, and reconnect from the dashboard to re-approve the grant. If some tools work and others fail, the failing family is where the scope gap is.

Ask the agent to diagnose it:

List the HighLevel tools you actually have and tell me which location the account shows. Run highlevel_get_conversations once, quote the exact error, and do not retry it.

In the manual world the taught cause is un-checked scopes in the Private Integration: Settings, then Private Integrations, then selecting the required scopes, then updating the local configuration file. In the hosted world scopes ride the OAuth grant: if a whole tool family is absent, the connection lacks that scope, and reconnecting after re-approving is the fix. If one name fails, it is wrong rather than missing, and the error lists the nearest real tools. Schemas load on demand, so the first HighLevel call in a fresh session can arrive before the catalog and needs one retry. The taught "update your local configuration file" step does not apply, because there is no local configuration file.

Ask the agent to diagnose it:

List the HighLevel tools you have available and tell me whether the missing one is part of a family, for example calendars or emails. Then use the exact name from the list.

Double-check that the API key for HighLevel has the right scopes or account access. A valid key can still be too limited for some reads or writes.

Yes. ClawLink is the fastest way to connect Hermes to HighLevel: link your HighLevel account once in the browser and Hermes Agent can call the HighLevel API through 36 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 HighLevel in the dashboard and Hermes can use it from the next message — no config files, and the HighLevel key you paste is stored server-side instead of in your environment.

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

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 HighLevel working from chat.

HighLevel connects through hosted OAuth: you sign in to HighLevel on their screen, approve the access, and ClawLink holds the token server-side. The manual route exists because the engines only know it: generate a Private Integration Token, choose scopes, write an mcpServers entry pointing at services.leadconnectorhq.com, and restart the agent. The hosted flow removes the token generation and the config file. Revoking the connection in the dashboard ends the agent's access.

The 94 tools cover the platform's surface: conversations and messages, calendars with appointments, schedules, services, and bookings, pipelines, funnel pages, email templates and campaigns, invoices and schedules, tasks, notes, tags, blogs, custom values, media files, brand boards and brand voice, marketplace rebilling configuration, and the Agent Studio agents published for a location. Reads dominate. The writes to be deliberate about are creating a tag or generating an estimate number, both of which land in real account data.

HighLevel structures everything by location, and the permission errors the engines teach are location-shaped: mismatched location IDs, a company-level token used against location-level endpoints, and missing OAuth scopes. The hosted connection sees what the HighLevel account you signed in with can reach. If tools return location errors, the first check is which account and location the connection was approved with.

The safety advice the engines repeat is generic: use API keys wisely, limit permissions, monitor activity. This connection is the concrete version of that advice: no key exists to leak, the OAuth grant sets the permissions, the connection is revocable from the dashboard, and nothing is written to any machine you use.

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.