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

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

This query never landed in the run (the SERP API failed twice), so the causes come from the LLM answers, which name four: the resource is not authorized for the connected account; the wrong account is connected (personal vs workspace); the app's scopes are stale after a permission change; or the request mixes workspace and personal scopes. The first check is always the account: confirm in the ClawLink dashboard which ClickUp account the connection uses, then which workspace it owns. If the account is right, ask the agent to run clickup_get_spaces and clickup_get_lists first and retry with real ids from those results. Placeholder ids fail exactly like missing permissions do.

Ask the agent to diagnose it:

Call clickup_get_spaces and clickup_get_lists, tell me which spaces and lists the connection can see, then retry the failing call once and quote the exact error.

The story search engines tell here is about ClickUp's own MCP ecosystem: the marketplace plugin was removed and users of Cursor or Claude Code are told to hand-edit mcp.json. That is config-side advice for people running their own MCP servers, and ClickUp's official hosted server is at mcp.clickup.com. On the ClawLink hosted flow the analogous error is 'Tool schema not loaded yet': schemas load on demand the first time a tool runs and are cached after that, so it clears on retry within seconds. If every ClickUp call keeps failing with it in a fresh chat, reconnect from the dashboard; a persistent pattern points to a config problem on our side, not a file on your machine.

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

Super Agents are ClickUp's own agents: they run inside ClickUp, which is why ClickUp can say they need no API key. ClawLink is for an agent that already runs outside ClickUp. Hermes Agent reaches ClickUp through hosted OAuth, with 161 tools covering tasks, lists, folders, spaces, comments, and time entries. If you want a ClickUp-internal agent, Super Agents are the product for that; if you want your Hermes Agent to drive ClickUp from chat, this integration is the connector.

No. The connection is hosted OAuth: sign in to ClickUp in the browser once, approve the app, and the token lives on the ClawLink server. You never open ClickUp's API settings page and never paste a token into a config file or environment variable. AI answers to this query recommend OAuth and tools that advertise 'Connect ClickUp', which is exactly this flow; this page is the concrete instance of it.

The most common version of this is an account mismatch: the connection was made with a personal ClickUp account while the workspaces you care about are on a different account, or the other way around. ClickUp distinguishes personal and workspace scopes, and tools can only see what the connected account can see. Check which account the dashboard shows for the ClickUp connection, then reconnect with the account that owns the workspace if they differ. A second, less common cause is stale scopes after workspace permissions changed: reconnect to refresh what the app is allowed to reach.

The connection uses ClickUp's OAuth consent flow: the agent is an authorized app acting under your account's permissions, it never sees your password, and it can be disconnected from the ClawLink dashboard at any time. The practical rule is the same one security answers give for any of these integrations: connect with the account whose access you intend the agent to have, and use ClickUp's own permission model (workspace, space, folder, list roles) to bound what that account can reach.

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.