# How to connect Erpnext to Hermes Agent (paste one key, 50 tools)

> Connect Erpnext to Hermes with ClawLink: paste your Erpnext key once and 50 tools work from chat. No MCP server to run, nothing stored on your machine.

Web version: https://claw-link.dev/hermes/erpnext

Most guides for giving Hermes Agent Erpnext 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 Erpnext setup: pair once in the browser and your always-on Hermes agent can act on Erpnext 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 Erpnext.

1. **Install ClawLink** — add the plugin to Hermes Agent once.
2. **Connect Erpnext** — one-click OAuth in the ClawLink dashboard.
3. **Use it from chat** — ask Hermes Agent in plain English.

**Paste this into Hermes to set up ClawLink:**

> Set up ClawLink for Hermes and tell me when it's ready.
> 1. Install the plugin: `hermes plugins install ClawLink-HQ/hermes-plugin --enable`
> 2. Start pairing with `hermes clawlink begin`. It prints an approval link, so show me the link and stop, don't wait.
> 3. I'll approve it in my browser, then reply "approved".
> 4. When I say approved, finish setup: `hermes clawlink finish`
> 5. Then run `hermes clawlink test` and tell me whether ClawLink is ready.

**Alternative for any agent (no plugin needed):** if the Hermes Agent plugin route isn't available or doesn't work, any AI agent with shell access can use the ClawLink CLI instead:

```bash
npx -y @useclawlink/cli login          # sign in via browser — no API key to paste
npx -y @useclawlink/cli connect erpnext  # connect Erpnext (browser OAuth)
npx -y @useclawlink/cli actions erpnext  # list available actions
npx -y @useclawlink/cli run erpnext <action> --input '<json>'  # execute (add --confirm for writes)
```

### Install by command

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

```bash
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 Erpnext in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Erpnext API key once.

Verify the connection by asking Hermes:

> Use Erpnext to download file and walk me through the result in plain English.

### 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:

```bash
npx -y @useclawlink/cli login
```

`login` opens the same browser approval and stores a credential locally. Once Erpnext is connected in the dashboard, that agent calls the same 50 Erpnext tools over MCP. Full setup for MCP clients and shell agents: [connect apps to any AI agent](https://claw-link.dev/learn/connect-apps-to-any-ai-agent).

## Erpnext MCP for Hermes

Looking for a Erpnext MCP server for Hermes Agent? ClawLink connects Erpnext to Hermes Agent and exposes 50 Erpnext tools your agent can call over [MCP](https://claw-link.dev/learn/what-is-an-mcp-server), with [hosted auth](https://claw-link.dev/learn/oauth-for-ai-agents) and nothing to run or maintain yourself. Using OpenClaw instead? The [OpenClaw Erpnext integration](https://claw-link.dev/openclaw/erpnext) works the same way.

## What the Hermes Agent Erpnext integration can do

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

### 30 of 50 Erpnext tools for Hermes

| Tool | What it does |
|---|---|
| **Download file** `erpnext_download_file` | Download a file from ERPNext by its URL |
| **Download PDF** `erpnext_download_pdf` | Download a document as PDF from ERPNext with optional print format |
| **Get all languages** `erpnext_get_all_languages` | Get a list of all available languages in the ERPNext/Frappe system |
| **Get all roles** `erpnext_get_all_roles` | Get a list of all roles available in the ERPNext system |
| **Get client** `erpnext_get_client` | Get a single document by DocType and name or filters from Frappe/ERPNext |
| **Get count** `erpnext_get_count` | Get the count of documents matching specified filters in ERPNext/Frappe |
| **Get doc with meta** `erpnext_get_doc_with_meta` | Retrieve a document with full metadata including attachments, comments, activity logs, and |
| **Get doctype meta** `erpnext_get_doctype_meta` | Retrieve complete DocType metadata/schema including field definitions, field types |
| **Get document** `erpnext_get_document` | Retrieve a specific document by its DocType and name (ID) |
| **Get exchange rate** `erpnext_get_exchange_rate` | Get the currency exchange rate between two currencies in ERPNext |
| **Get fiscal year** `erpnext_get_fiscal_year` | Get fiscal year information for a given date in ERPNext |
| **Get framework version** `erpnext_get_framework_version` | Get the Frappe framework version and all installed app versions |
| **Get item details** `erpnext_get_item_details` | Get detailed item information including pricing, taxes, and stock details from ERPNext |
| **Get list** `erpnext_get_list` | Retrieve a list of documents from ERPNext/Frappe with filtering, field selection, and pagination |
| **Get logged user** `erpnext_get_logged_user` | Get the email/ID of the currently authenticated user |
| **Get party details** `erpnext_get_party_details` | Get comprehensive customer or supplier details including addresses, contacts, and default |
| **Get payment entry** `erpnext_get_payment_entry` | Get payment entry details for an invoice or order from ERPNext |
| **Get stock balance** `erpnext_get_stock_balance` | Retrieve the current stock balance for a specific item in a warehouse |
| **Get timezones** `erpnext_get_timezones` | Get a list of all available timezones in the ERPNext system |
| **Get user roles** `erpnext_get_user_roles` | Get roles assigned to a user |
| **Get value** `erpnext_get_value` | Get specific field value(s) from a document in ERPNext |
| **Get workflow transitions** `erpnext_get_workflow_transitions` | Get available workflow transitions for a document |
| **List doctypes** `erpnext_list_doctypes` | Get a list of all DocTypes available in the ERPNext system |
| **List documents** `erpnext_list_documents` | List documents of a specific DocType from ERPNext |
| **List employees** `erpnext_list_employees` | Retrieve a list of Employee records from ERPNext |
| **List projects** `erpnext_list_projects` | Retrieve a list of Project records from ERPNext |
| **List timesheets** `erpnext_list_timesheets` | Get a list of Timesheet records from ERPNext |
| **List webhooks** `erpnext_list_webhooks` | List webhook configurations in ERPNext |
| **Ping** `erpnext_ping` | Check if the ERPNext/Frappe API is reachable |
| **Search global** `erpnext_search_global` | Perform global text search across ERPNext documents |

## Example prompts

**Download File**

> Use Erpnext to download file and walk me through the result in plain English.

**Download Pdf**

> Use Erpnext to download pdf and walk me through the result in plain English.

**Get All Languages**

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

**Get All Roles**

> Pull the relevant data from Erpnext, 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 Erpnext working from chat.

| | Manual | ClawLink |
|---|---|---|
| **Credential handling** | Collect, validate, store, and rotate the Erpnext API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Erpnext 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 Erpnext. | 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 Erpnext actions to the runtime in a format your agent can reliably use. | 50 tools for Erpnext are already exposed through ClawLink, so the agent can read and act from chat immediately. |

## ClawLink vs. Composio

Composio also exposes Erpnext 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 Erpnext in the browser, and the 50 tools above work from chat. There is no SDK and no config file, and the Erpnext key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full [Composio alternatives](https://claw-link.dev/hub/composio-alternatives) comparison.

### Hermes paired but still can't use Erpnext
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 Erpnext 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 Erpnext tools
Erpnext 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 Erpnext 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.

### Erpnext 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 Erpnext has the right scopes or account access. A valid key can still be too limited for some reads or writes.

### Is there a Hermes Agent Erpnext integration?
Yes. ClawLink is the fastest way to connect Hermes to Erpnext: link your Erpnext account once in the browser and Hermes Agent can call the Erpnext API through 50 ready-made tools — no custom code or token handling.

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

### How long does it take to connect Erpnext to Hermes Agent?
About two minutes. Sign in, click Connect next to Erpnext in the dashboard, authenticate, and Hermes Agent can use it from the next chat message.

### Why use ClawLink instead of wiring Erpnext up myself?
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 Erpnext working from chat.

### Hermes paired but still can't use Erpnext
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`.

## Related

- [Trello tools](https://claw-link.dev/hermes/trello) — Manage boards, lists, and cards
- [Moco](https://claw-link.dev/hermes/moco) — MOCO is a business management software offering project management, time tracking, and invoicing solutions.
- [Connect ClickUp](https://claw-link.dev/hermes/clickup) — Manage tasks, docs, goals, and sprints
