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

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

monday.com's 403 causes, as taught by the engines and confirmed against the toolset: the connected account is not a member of the private board in the request; the account has read-only or guest rights where the tool needs more; the app is missing the scopes the action needs; or a workspace admin has restricted the connected account from creating integrations or API tokens. The last cause is the one this page did not previously list, and it is the one that produces a 403 on a healthy-looking connection. Also check the request itself: boards and items are addressed by id, so an example id from documentation fails exactly like a missing membership does. Run monday_boards first and retry with real ids from its results.

Ask the agent to diagnose it:

Call monday_get_me and monday_boards to confirm the account and the boards it can see, then retry the failing call once and quote the exact error.

The fix search engines teach for this error is a workspace-level switch: Admin, then Permissions, then AI Connectors, with 'AI Connectors & MCP Access' enabled. That switch gates AI and MCP access for the whole workspace, so if it is off, a connected integration can look healthy and still fail to load tools. Have a workspace admin check it before assuming a connection problem. On the ClawLink hosted flow the analogous error is 'Tool schema not loaded yet', which clears on retry: schemas load on demand the first time a tool runs. Reconnect from the dashboard only if every call keeps failing in a fresh chat.

Try reconnecting Monday 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 Monday: link your Monday account once in the browser and Hermes Agent can call the Monday API through 121 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 Monday 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 Monday 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 Monday working from chat.

No. The connection uses hosted OAuth: you sign in to monday.com in the browser once and ClawLink stores the session server-side. You never open monday.com's developer console, never create a personal API token, and never paste one into a config file. The engine answer to this query currently teaches the manual token flow or monday's internal agents; the hosted-OAuth path for an external agent is what this page covers.

Agent Builder and Agent Factory create agents that run inside monday.com and act on its boards natively, which is why those answers can say no API key is involved. ClawLink connects an agent that already runs outside monday: Hermes Agent. The agent stays in its own runtime and reaches monday through hosted OAuth, with 121 tools covering boards, items, columns, updates, and documents. If your agent is Hermes, ClawLink is the connector; if you want a monday-internal agent, use monday's own builder.

It is a workspace admin toggle on monday.com: Admin, then Permissions, then AI Connectors, then 'AI Connectors & MCP Access' on. Search engines teach this switch as the fix when monday tools fail to load, and it matters for a hosted connection too: if the workspace has AI connector access disabled, connected integrations can be blocked at the workspace level no matter what your account permissions say. If tools fail to appear after connecting, ask a workspace admin whether that toggle is on.

The connection is scoped OAuth: your agent can do what your monday.com account can do, including nothing on boards you are not a member of, and the connection is revocable from the ClawLink dashboard at any time. monday.com's own security answers (permission scoping, private boards) apply as they would to any authorized app, because the agent is exactly that: an authorized app acting under your account's permissions. Connect with the account whose permissions you intend the agent to have.

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.