How to connect Onedesk to Hermes Agent
Connect Onedesk to Hermes with ClawLink: paste your Onedesk key once and 24 tools work from chat. No MCP server to run, nothing stored on your machine.
OnedeskAPI KEYMCPOneDesk is an all-in-one platform combining help desk and project management functionalities, enabling teams to manage customer support and project tasks seamlessly.. Once connected, Hermes Agent can read and act on Onedesk from chat — pairing, token refresh, and tool wiring handled for you.
Most guides for giving Hermes Agent Onedesk 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 Onedesk setup: pair once in the browser and your always-on Hermes agent can act on Onedesk 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 Onedesk.
1Install 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 Onedesk
Paste your API key in the dashboard.
- 3
Use it from chat
Ask Hermes Agent: "What can you do with Onedesk?"
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 testThen connect Onedesk in the ClawLink dashboard — paste your Onedesk API key once.
Verify the connection by asking Hermes:
Pull the relevant data from Onedesk, 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 loginlogin opens the same browser approval and stores a credential locally. Once Onedesk is connected in the dashboard, that agent calls the same 24 Onedesk tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Onedesk MCP for Hermes
Looking for a Onedesk MCP server for Hermes Agent? ClawLink connects Onedesk to Hermes Agent and exposes 24 Onedesk tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using OpenClaw instead? The OpenClaw Onedesk integration works the same way.
What the Hermes Agent Onedesk integration can do
24 Onedesk tools are ready for Hermes Agent once the account is connected. The 14 below are the ones people reach for most; your agent can call all 24.
14 of 24 Onedesk tools for Hermes
| Tool | What it does |
|---|---|
Get attachments onedesk_get_attachments | Retrieve attachments for a specific item by its external ID |
Get comment details onedesk_get_comment_details | Retrieve detailed information for a specific comment by its ID |
Get comments onedesk_get_comments | Attempts to retrieve comments (discussion posts) from OneDesk |
Get feedback onedesk_get_feedback | Retrieve all feedback items from OneDesk |
Get feedback details onedesk_get_feedback_details | Retrieve detailed information about a specific item in OneDesk by its internal ID |
Get issue details onedesk_get_issue_details | Retrieve comprehensive details of a specific issue by its ID |
Get issues onedesk_get_issues | Retrieve a list of issues from OneDesk |
Get messages onedesk_get_messages | Retrieve a list of messages from OneDesk |
Get requirements onedesk_get_requirements | Retrieve a list of requirements from OneDesk |
Get task details onedesk_get_task_details | Retrieves comprehensive details of a specific task/item in OneDesk by its ID |
Get tickets onedesk_get_tickets | Retrieve tickets from OneDesk by querying a range of item IDs |
Get timesheet details onedesk_get_timesheet_details | Retrieve details of a specific timesheet entry |
Get worklogs onedesk_get_worklogs | Retrieve a list of worklogs from OneDesk with optional filtering and pagination |
Create worklog onedesk_create_worklog | Create a worklog entry to track time spent on a work item (task, ticket, project, etc.) |
Try it: find the Onedesk tool you need
Browse the 14 Onedesk 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 Onedesk, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Onedesk, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Onedesk, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Onedesk, 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 Onedesk working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Onedesk API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Onedesk 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 Onedesk. | 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 Onedesk actions to the runtime in a format your agent can reliably use. | 24 tools for Onedesk are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Onedesk 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 Onedesk in the browser, and the 24 tools above work from chat. There is no SDK and no config file, and the Onedesk 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 Onedesk
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 Onedesk 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 Onedesk tools
Onedesk 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 Onedesk 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.
Onedesk 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 Onedesk 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 Onedesk integration?
Yes. ClawLink is the fastest way to connect Hermes to Onedesk: link your Onedesk account once in the browser and Hermes Agent can call the Onedesk API through 24 ready-made tools — no custom code or token handling.
How do I connect Onedesk 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 Onedesk in the dashboard and Hermes can use it from the next message — no config files, and the Onedesk key you paste is stored server-side instead of in your environment.
How long does it take to connect Onedesk to Hermes Agent?
About two minutes. Sign in, click Connect next to Onedesk in the dashboard, authenticate, and Hermes Agent can use it from the next chat message.
Why use ClawLink instead of wiring Onedesk 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 Onedesk working from chat.
Hermes paired but still can't use Onedesk
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.
