# How to connect FuseDesk to Hermes Agent (paste one key, 27 tools)

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

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

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

1. **Install ClawLink** — add the plugin to Hermes Agent once.
2. **Connect FuseDesk** — 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 fusedesk  # connect FuseDesk (browser OAuth)
npx -y @useclawlink/cli actions fusedesk  # list available actions
npx -y @useclawlink/cli run fusedesk <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 FuseDesk in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your FuseDesk API key once.

Verify the connection by asking Hermes:

> Pull the relevant data from FuseDesk, 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:

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

`login` opens the same browser approval and stores a credential locally. Once FuseDesk is connected in the dashboard, that agent calls the same 27 FuseDesk 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).

## FuseDesk MCP for Hermes

Looking for a FuseDesk MCP server for Hermes Agent? ClawLink connects FuseDesk to Hermes Agent and exposes 27 FuseDesk 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 FuseDesk integration](https://claw-link.dev/openclaw/fusedesk) works the same way.

## What the Hermes Agent FuseDesk integration can do

27 FuseDesk tools are ready for Hermes Agent once the account is connected.

### All 27 FuseDesk tools for Hermes

| Tool | What it does |
|---|---|
| **Get case** `fusedesk_get_case` | Get one FuseDesk support case and its complete history by case ID |
| **Get chat** `fusedesk_get_chat` | Get one FuseDesk chat and its complete message history by chat UUID |
| **Get contact** `fusedesk_get_contact` | Get a FuseDesk contact by UUID, including current data from its linked CRM contact |
| **Get department** `fusedesk_get_department` | Get a FuseDesk department's assignment, template, staleness, feedback, phone, and archive |
| **Get email** `fusedesk_get_email` | Get one FuseDesk email by its numeric ID, including its complete body |
| **Get rep** `fusedesk_get_rep` | Get a FuseDesk rep's detailed profile, permissions, and signatures |
| **List case tags** `fusedesk_list_case_tags` | List available FuseDesk case tags and their case counts |
| **List chats** `fusedesk_list_chats` | List active FuseDesk chats across connected chat platforms, including assignment links |
| **List departments** `fusedesk_list_departments` | List active, archived, or all FuseDesk departments using the current v2 representation |
| **List reps** `fusedesk_list_reps` | List active and disabled FuseDesk reps for assignment and ownership decisions |
| **List webhooks** `fusedesk_list_webhooks` | List configured FuseDesk webhook subscriptions |
| **Search cases** `fusedesk_search_cases` | Search support cases by customer, assignment, status, text, and lifecycle dates, returning one |
| **Search contacts** `fusedesk_search_contacts` | Search FuseDesk and linked CRM contacts by required text |
| **Search emails** `fusedesk_search_emails` | Search all or only unassigned FuseDesk emails, returning one controllable page with optionally |
| **Add case note** `fusedesk_add_case_note` | Add an internal note or call record to a case and optionally change its status |
| **Bulk update cases** `fusedesk_bulk_update_cases` | Apply an assignment, department, status, tag, CRM automation, CRM tag, or snooze operation to |
| **Change case tag** `fusedesk_change_case_tag` | Apply or remove one existing case tag from one FuseDesk case |
| **Create case** `fusedesk_create_case` | Open a support case for a customer in a FuseDesk department |
| **Create case tag** `fusedesk_create_case_tag` | Create a reusable FuseDesk case tag |
| **Create contact** `fusedesk_create_contact` | Create a FuseDesk contact |
| **Snooze case** `fusedesk_snooze_case` | Snooze a case until an absolute date/time or FuseDesk relative-time expression |
| **Update case** `fusedesk_update_case` | Change a case's content, customer link, assignment, department, or status |
| **Update chat** `fusedesk_update_chat` | Rename, transfer, relink, or mark a live FuseDesk chat seen or unseen |
| **Update contact** `fusedesk_update_contact` | Update a FuseDesk contact |
| **Bulk merge cases** `fusedesk_bulk_merge_cases` | Irreversibly merge multiple FuseDesk cases |
| **Close chat** `fusedesk_close_chat` | Irreversibly close a FuseDesk chat and end the live conversation |
| **Reply to case** `fusedesk_reply_to_case` | Send an external email reply on a FuseDesk case using supplied content or an existing reply |

## Example prompts

**Get Case**

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

**Get Chat**

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

**Get Contact**

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

**Get Department**

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

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

## ClawLink vs. Composio

Composio also exposes FuseDesk 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 FuseDesk in the browser, and the 27 tools above work from chat. There is no SDK and no config file, and the FuseDesk 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 FuseDesk
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 FuseDesk 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 FuseDesk tools
FuseDesk 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 FuseDesk 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.

### FuseDesk 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 FuseDesk 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 FuseDesk integration?
Yes. ClawLink is the fastest way to connect Hermes to FuseDesk: link your FuseDesk account once in the browser and Hermes Agent can call the FuseDesk API through 27 ready-made tools — no custom code or token handling.

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

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

### Why use ClawLink instead of wiring FuseDesk 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 FuseDesk working from chat.

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

- [Zendesk tools](https://claw-link.dev/hermes/zendesk) — Manage support tickets, macros, users, and organizations
- [Gleap](https://claw-link.dev/hermes/gleap) — Gleap is an all-in-one customer feedback tool for apps and websites, enabling direct communication with users to build better software by discovering their everyday pain points.
- [Freshdesk tools](https://claw-link.dev/hermes/freshdesk) — Handle support tickets, contacts, and helpdesk operations