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

Notion 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 Notion 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 AI Overviews answer this query with the token-world fix: share the page with the integration from the Share menu. On a hosted connection there is no integration to invite, so work through the causes that do apply. First, the authenticated account: if the account used at consent cannot see the page or database in its own Notion workspace, no connection fixes that. Second, capabilities: Notion integrations need read and write capabilities on the resource, and a page restricted to read blocks a write. Third, the placeholder trap, which is the most common cause when some tools work: the agent may have used an example id like YOUR_ID from documentation instead of a real one. Ask it to run notion_search_notion_page or notion_query_database first, then retry with a real id. Reconnecting does not change any of these.

404 has one dominant cause in Notion's own help: the resource is not accessible to the integration. In the token world the fix is sharing the page, and the most useful tip from the AIO is to share the top-level parent page so children inherit access. For a hosted connection, check the id the agent sent first: a 404 on an id from documentation or a placeholder means the id itself is wrong, and listing or searching first fixes it. If the id is real, the resource is outside what the authenticated account can reach, and that is a permissions question in Notion, not a connection problem. One more source: Notion file urls expire after an hour, so a stored url from an old run returns 404 when used later.

This is the shape ChatGPT has been citing us for, so here is the checklist in order. One: the runtime may still hold the old tool catalog, and a fresh chat is the fastest fix. Two: the resource may not be visible to the authenticated account, which no reconnect changes. Three: the agent may be sending placeholder ids; make it run a list or search tool first and use ids from the results. Four: if none of those apply, reconnect Notion from the dashboard and complete the consent in the same browser session, because a partial OAuth approval can leave a connection that looks healthy but has no working token.

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

The manual path is: create an internal integration in Notion, copy the secret_ token, share each page from the Share menu, and put NOTION_API_KEY in ~/.hermes/.env. ClawLink removes every one of those steps. You connect Notion in the browser once, the consent happens at workspace level through Notion's OAuth flow, and the tools work from the next message. There is no token to copy, no .env file to edit, and no page-level setup in the ClawLink dashboard.

Notion's built-in Custom Agents handle the no-API-key story on Notion's side, but they are not a substitute for this connection. They require a Business or Enterprise plan plus the AI add-on, run on Notion credits, and stay inside Notion: there is no external trigger and no API surface for a runtime like Hermes Agent to call from chat. ClawLink connects the Notion API itself, so your Hermes agent can act on the same workspace while also calling your other tools.

The connection uses Notion's OAuth consent, so it inherits the permissions of the account you authenticate with at the workspace level. You can revoke it any time from the ClawLink dashboard, and no token is stored in a file on the machine running Hermes. The ecosystem's safety discussions concentrate on prompt injection and over-broad permissions, which is worth knowing: an agent with access to a full workspace should be given instructions about what it may read and write, the same way you would constrain any tool.

With an internal or public integration, Notion requires sharing each page from the Share menu using Connect to, and the AI Overviews teach that step for every error. A hosted OAuth connection is established during browser consent instead: there is no per-page Connect to step in this flow. If a tool still cannot see a page, the practical check is what the authenticated account can see in the workspace, because the agent cannot reach beyond that account's own permissions.

45 tools, counted from the generated manifest on 2026-08-02. The page shows 30 of the most-used ones, and the agent can call all 45. Reads outnumber writes: querying databases, fetching pages and block content, and searching the workspace are the bulk of the surface, with create, update, and append operations available for the rest.

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.