How to connect Conveyor to Hermes Agent (paste one key, 25 tools)

Most guides for giving Hermes Agent Conveyor access start with registering your own OAuth app or pasting API keys into env files, then leave the token refresh and tool wiring to you. ClawLink gives Hermes a more practical Conveyor setup: pair once in the browser and your always-on Hermes agent can act on Conveyor for you, reading and doing real work on your behalf with no auth, token refresh, or tool wiring to build yourself.

Setup

It takes three steps to connect Hermes to Conveyor.

1
Install and pair
Install the ClawLink plugin, then pair Hermes with a one-time browser approval:
hermes plugins install ClawLink-HQ/hermes-plugin --enable
2
Connect Conveyor
Paste your API key in the dashboard.
3
Use it from chat
Ask Hermes Agent: "What can you do with Conveyor?"

Install by command

The prompt above walks Hermes through this. By hand, it is four commands and a browser approval:

hermes plugins install ClawLink-HQ/hermes-plugin --enable
hermes clawlink begin    # prints an approval link — open it and approve
hermes clawlink finish   # after approving in the browser
hermes clawlink test

Then connect Conveyor in the ClawLink dashboard — paste your Conveyor API key once.

Verify the connection by asking Hermes:

Pull the relevant data from Conveyor, summarize it in plain English, and point out anything that needs attention.

Using a different agent?

The Hermes plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI:

npx -y @useclawlink/cli login

login opens the same browser approval and stores a credential locally. Once Conveyor is connected in the dashboard, that agent calls the same 25 Conveyor tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.

Conveyor MCP for Hermes

Looking for a Conveyor MCP server for Hermes Agent? ClawLink connects Conveyor to Hermes Agent and exposes 25 Conveyor tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using OpenClaw instead? The OpenClaw Conveyor integration works the same way.

What the Hermes Agent Conveyor integration can do

25 Conveyor tools are ready for Hermes Agent once the account is connected. The 23 below are the ones people reach for most; your agent can call all 25.

23 of 25 Conveyor tools for Hermes

Tool	What it does
Get access groups `conveyor_get_access_groups`	Retrieve all access groups for a program
Get authorization request `conveyor_get_authorization_request`	Retrieves details of a specific authorization request from Conveyor Exchange by its ID
Get authorization requests `conveyor_get_authorization_requests`	Retrieves authorization requests from Conveyor's Trust Center
Get authorizations `conveyor_get_authorizations`	Retrieve authorizations from your Conveyor Trust Center
Get connections `conveyor_get_connections`	Retrieve all connections
Get documents `conveyor_get_documents`	Retrieves all documents from the Conveyor trust center
Get folders `conveyor_get_folders`	Retrieves all folders from the Conveyor Exchange workspace
Get interactions `conveyor_get_interactions`	Get all interactions (document interactions, q&a interactions) with optional filters
Get interactions by connection ID `conveyor_get_interactions_by_connection_id`	Fetch interactions associated with a specific connection
Get interactions by document ID `conveyor_get_interactions_by_document_id`	Fetch interactions associated with a specific document
Get knowledge base questions `conveyor_get_knowledge_base_questions`	Retrieves knowledge base questions from Conveyor
Get product lines `conveyor_get_product_lines`	Retrieves all product lines configured in Conveyor
Get questionnaires `conveyor_get_questionnaires`	Retrieves all questionnaires from Conveyor with optional filters
Post single question `conveyor_post_single_question`	Submit a single question to Conveyor's AI knowledge base and receive an immediate answer
Patch document `conveyor_patch_document`	Update a Conveyor document's metadata
Patch questionnaire request `conveyor_patch_questionnaire_request`	Update a questionnaire request in Conveyor
Post authorization `conveyor_post_authorization`	Create a new authorization in Conveyor Exchange
Post document `conveyor_post_document`	Upload a new document to Conveyor's Knowledge Library
Post folder `conveyor_post_folder`	Create a new folder in Conveyor Exchange
Post questionnaire `conveyor_post_questionnaire`	Submit a new questionnaire to Conveyor
Post questionnaire request `conveyor_post_questionnaire_request`	Create a new questionnaire request in Conveyor
Post review `conveyor_post_review`	Create a review in Conveyor with optional references to external VM unique IDs
Patch authorization `conveyor_patch_authorization`	Update an existing authorization by revoking access or modifying Access Group assignments

Try it: find the Conveyor tool you need

Browse the 23 Conveyor tools

Click any tool to see exactly what Hermes can do and copy a ready-to-use prompt.

Example prompts

Pull the relevant data from Conveyor, summarize it in plain English, and point out anything that needs attention.

ClawLink vs. building it yourself

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

	Manual	ClawLink
Credential handling	Collect, validate, store, and rotate the Conveyor API key yourself, then make sure every tool call uses the right account.	Users complete the hosted ClawLink setup once and the connected Conveyor account becomes available to the agent without you building credential management.
Ongoing maintenance	You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Conveyor.	ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure.
Agent usability	You still need to expose the right Conveyor actions to the runtime in a format your agent can reliably use.	25 tools for Conveyor are already exposed through ClawLink, so the agent can read and act from chat immediately.

ClawLink vs. Composio

Composio also exposes Conveyor to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for Hermes Agent users instead. You install the plugin once, connect Conveyor in the browser, and the 25 tools above work from chat. There is no SDK and no config file, and the Conveyor key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full Composio alternatives comparison.

Troubleshooting

Hermes paired but still can't use Conveyor

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.

Connection succeeds but no tools appear

Reconnect Conveyor from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded.

"Tool schema not loaded yet" error when calling Conveyor tools

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

Conveyor returns 403 or "permission denied" on one action while others work

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.

API key setup works but results look incomplete

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

FAQ

Is there a Hermes Agent Conveyor integration?

Yes. ClawLink is the fastest way to connect Hermes to Conveyor: link your Conveyor account once in the browser and Hermes Agent can call the Conveyor API through 25 ready-made tools — no custom code or token handling.

How do I connect Conveyor to Hermes with ClawLink?

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 Conveyor in the dashboard and Hermes can use it from the next message — no config files, and the Conveyor key you paste is stored server-side instead of in your environment.

How long does it take to connect Conveyor to Hermes Agent?

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

Why use ClawLink instead of wiring Conveyor up myself?

Hermes paired but still can't use Conveyor

How to connect Conveyor to Hermes Agent

Setup

Install and pair

Connect Conveyor

Use it from chat