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

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

Before touching anything, separate two credentials that get confused constantly on this provider. The key that authenticates Hermes to a model provider — the one in a ~/.hermes env file — has nothing to do with this, and search results for "Hermes API key" overwhelmingly answer about that one instead. The credential in play here is the Postman API key you pasted at setup, held server-side. With that clear: if the key was regenerated or deleted in Postman afterwards, every Postman tool fails from that moment and re-pasting the current key from the dashboard is the fix. If only some calls fail, the key is valid and you are looking at what your Postman user can reach — workspace and team membership decide visibility, so a collection in a workspace you are not a member of returns a permission error rather than a not-found.

Ask the agent to diagnose it:

Call postman_get_accounts and list the workspaces you can see. Tell me which Postman account this connection is acting as, then quote the exact error from the failed call. Do not retry it yet.

Postman rate-limits its API, and an agent enumerating a large workspace is exactly the traffic shape that meets the limit: walking every collection, then every folder, then every request, one call at a time. The response is not to retry immediately but to change the shape of the work — ask for one collection rather than a whole workspace, and have the agent tell you what it intends to enumerate before it starts. Postman returns headers describing the remaining allowance alongside the error, so the agent can report where it stands rather than guessing. If a bulk audit is genuinely needed, running it in stages across a few turns is more reliable than one sweep.

Ask the agent to diagnose it:

Tell me how many Postman calls you have made in the last minute and what you were enumerating. Quote any rate-limit headers from the last response. Do not call Postman again until I reply.

Two different failures. If Hermes shows no Postman tools at all, the connection or the pairing is incomplete — confirm the plugin was installed with --enable, that both hermes clawlink begin and hermes clawlink finish ran, and that Postman shows as connected in the dashboard. If most tools work and a single name fails, that name is wrong rather than missing, and the error lists the closest real ones. There is also a first-call timing case unique to this setup: schemas load on demand, so the opening Postman call in a fresh session can arrive before the catalog and needs one retry. What does not apply is the usual advice for this symptom, which assumes a local MCP server declared in a client config file.

Ask the agent to diagnose it:

List the Postman tools you actually have access to. If there are none, say so plainly. If there are, tell me which one fetches a workspace and use that exact name.

Double-check that the API key for Postman 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 Postman: link your Postman account once in the browser and Hermes Agent can call the Postman API through 126 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 Postman in the dashboard and Hermes can use it from the next message — no config files, and the Postman key you paste is stored server-side instead of in your environment.

About two minutes. Sign in, click Connect next to Postman 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 Postman working from chat.

A Postman API key, generated in your Postman account settings, entered once on the hosted setup page. It carries your Postman user's access, so the agent sees the workspaces, collections, and teams that you see. Because it is stored server-side rather than in a .env or a CLI config, it is not sitting on any machine you happen to have used, rotating it in Postman means updating a single place, and disconnecting from the ClawLink dashboard revokes the agent's use of it immediately.

Read and write the things a team actually argues about: collections and their folders and requests, saved responses, comments on collections, folders, requests and responses, forks and pull requests, schemas and API specs including generated collections, monitors, workspaces and their activity feeds, and team and role membership. Creating collections, folders, and comments are the writes to be deliberate about, since collections are shared objects and a comment notifies people. The spec tools are the underrated part — pulling a spec and its generated collections is how an agent grounds itself in what an API is supposed to do before touching anything.

It reads monitors rather than acting as a runner. The value of this connection is in the API design and documentation surface — what exists, who changed it, what the spec says, what a saved response looks like — rather than in executing traffic. If you want the agent to actually call an API, having it read the request definition here and then make the call itself is usually more transparent than routing execution through Postman, because you can see exactly what it sent.

The underlying Postman API is the same, so the capability difference is small; the setup and upkeep difference is not. The Composio route that search results teach involves their Connect CLI or an MCP endpoint plus a key, and editing Hermes's config to point at it — infrastructure you then own. Here the plugin install and one pairing handshake are the entire client-side story, and Postman sits alongside your other connected accounts with one place to revoke. Choose on how much you want to run, not on features.

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.