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

Zoho Inventory 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 Zoho Inventory 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.

ChatGPT enumerates five causes and asks for exact error codes like AUTHORIZATION_FAILED, NO_PERMISSION, 401, or 403. In order: the Zoho user's role lacks module permissions, since only admins are unrestricted by default and custom roles must explicitly grant modules; insufficient OAuth scopes, fixed by reauthorizing from the dashboard; the wrong organisation in the call; a stale or revoked token; or a module the plan cannot reach. Plus the placeholder trap: an id copied from documentation. Quote the exact code and check organisation and role before reconnecting.

Ask the agent to diagnose it:

Quote the exact error code from the failed call. Then call zoho_inventory_get_current_user and zoho_inventory_list_organizations and tell me which user and organisations this connection acts on. Do not retry the failed call yet.

Zoho's docs publish 100 requests per minute per organisation plus a daily allowance tied to the subscription plan, with 429 on breach. The bulk tools are exactly the traffic shape that meets it: zoho_inventory_bulk_export_invoices, bulk email, or bulk print on a large set. Stage the work: one date range per turn, report the count, then continue, rather than retrying the same sweep.

Ask the agent to diagnose it:

Tell me how many Zoho Inventory calls you made in the last minute and which bulk tool you were running. Quote the error verbatim. Do not call Zoho Inventory again until I reply.

The engines blame a misconfigured MCP server, wrong scopes, or a stale tool cache, all self-hosted causes. The hosted causes: pairing incomplete, fixed by rerunning hermes clawlink begin and hermes clawlink finish and confirming Zoho Inventory shows as connected; schemas loading on demand, so the opening call in a fresh session can arrive before the catalog and needs one retry; and a wrong tool name, where the error lists the closest real ones.

Ask the agent to diagnose it:

List the Zoho Inventory tools you actually have access to. If there are none, say so plainly. If there are, tell me which one lists items and use that exact name.

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

No. Hermes Agent is the AI assistant; the courier formerly named Hermes, now Evri, is a shipping company. Google disambiguates the two, ChatGPT does not, which is why this page spells it out: if you are wiring a parcel carrier into Zoho Inventory, that is a shipping-integration flow, not this one.

Because Zoho deprecated static API authtokens in 2021; the current API requires OAuth 2.0 with a registered app. The hosted platform is the registered app here: you authorize in the browser, the OAuth grant is held server-side, and no token or client secret ever lands on your machine. The 'no token' claim other answers make about Zoho's own MCP Console works the same way, with the console setup this route removes.

Stock questions are direct: list items and item groups, bills, invoices, credit notes, sales orders, purchase orders, contacts, currencies, invoice payments, and the organisations you can reach. Writes exist for bills, contacts, credit notes, and customer payments, plus bulk export, bulk email, and bulk print of invoices, and comments and attachments on invoices and credit notes.

The connection acts on the organisation of the account you authorized. zoho_inventory_list_organizations shows which ones you can reach, and a call for the wrong organisation reads as a 403 rather than a not-found, which is why the troubleshooting card below starts there.

The engines teach OAuth scopes and revocation as the safety answer. Here the OAuth grant is scoped to what the tools need, held server-side, and revocable from the dashboard or inside Zoho; when scopes change, reauthorize so the consent screen grants what the tools need. The taught prompt-injection framing applies as always: treat anything the agent reads from documents as untrusted input.

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.