# How to connect Helpdesk to OpenClaw (paste one key, 14 tools) > Connect Helpdesk to OpenClaw with ClawLink: paste your Helpdesk key once and 14 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/helpdesk The usual route to Helpdesk access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical Helpdesk setup: install one ClawHub skill, connect Helpdesk in the browser, and OpenClaw can call real Helpdesk actions from any chat surface with no auth, token refresh, or tool wiring to build yourself. ## Setup It takes three steps to connect OpenClaw to Helpdesk. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Helpdesk** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask OpenClaw in plain English. **Paste this into OpenClaw to set up ClawLink:** > I want to connect my apps to OpenClaw through ClawLink. > Please install the ClawLink plugin from ClawHub and enable it: `openclaw plugins install clawhub:clawlink-plugin` > When it is installed, tell me and stop. After I reply, give me the ClawLink pairing link. Setup notes, if you need them: https://claw-link.dev/skill.md **Alternative for any agent (no plugin needed):** if the OpenClaw 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 helpdesk # connect Helpdesk (browser OAuth) npx -y @useclawlink/cli actions helpdesk # list available actions npx -y @useclawlink/cli run helpdesk --input '' # execute (add --confirm for writes) ``` ### Install by command The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval: ```bash openclaw plugins install clawhub:clawlink-plugin ``` Then ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say `done`. Finally, connect Helpdesk in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Helpdesk API key once. Verify the connection by asking OpenClaw: > List the relevant items in Helpdesk, group them by priority, and recommend what OpenClaw should do next. ### Using a different agent? The OpenClaw 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 Helpdesk is connected in the dashboard, that agent calls the same 14 Helpdesk 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). ## Helpdesk MCP for OpenClaw Looking for a Helpdesk MCP server for OpenClaw? ClawLink connects Helpdesk to OpenClaw and exposes 14 Helpdesk 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 Hermes instead? The [Hermes Helpdesk integration](https://claw-link.dev/hermes/helpdesk) works the same way. ## What the OpenClaw Helpdesk integration can do 14 Helpdesk tools are ready for OpenClaw once the account is connected. ### All 14 Helpdesk tools for OpenClaw | Tool | What it does | |---|---| | **List agents** `helpdesk_list_agents` | Retrieves all support agents (team members) in the HelpDesk account | | **List canned responses** `helpdesk_list_canned_responses` | List canned responses | | **List custom fields** `helpdesk_list_custom_fields` | List all custom fields defined in the account | | **List email domains** `helpdesk_list_email_domains` | Lists all email domains configured for the HelpDesk account | | **List licenses** `helpdesk_list_licenses` | Retrieves all licenses (account configurations) for the authenticated HelpDesk account | | **List reply addresses** `helpdesk_list_reply_addresses` | Lists all reply addresses configured in the HelpDesk account | | **List rules** `helpdesk_list_rules` | Retrieve a list of rules configured in the account | | **List subscriptions** `helpdesk_list_subscriptions` | Lists all billing subscriptions for the HelpDesk account, including active, expired, canceled | | **List teams** `helpdesk_list_teams` | Lists all teams in the HelpDesk account | | **List tickets** `helpdesk_list_tickets` | List all tickets from a specified silo with cursor-based pagination support | | **List trusted emails** `helpdesk_list_trusted_emails` | Retrieve a list of trusted email addresses or domains | | **List views** `helpdesk_list_views` | List agent views | | **List webhooks** `helpdesk_list_webhooks` | Lists all configured webhooks for the HelpDesk account | | **View agent** `helpdesk_view_agent` | Retrieves comprehensive details for a specific agent in the HelpDesk system | ## Example prompts **List Agents** > List the relevant items in Helpdesk, group them by priority, and recommend what OpenClaw should do next. **List Canned Responses** > List the relevant items in Helpdesk, group them by priority, and recommend what OpenClaw should do next. **List Custom Fields** > List the relevant items in Helpdesk, group them by priority, and recommend what OpenClaw should do next. **List Email Domains** > List the relevant items in Helpdesk, group them by priority, and recommend what OpenClaw should do next. ## 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 OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Helpdesk working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Helpdesk API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Helpdesk 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 Helpdesk. | 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 Helpdesk actions to the runtime in a format your agent can reliably use. | 14 tools for Helpdesk are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Helpdesk 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 OpenClaw users instead. You install the plugin once, connect Helpdesk in the browser, and the 14 tools above work from chat. There is no SDK and no config file, and the Helpdesk 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. ### OpenClaw installed the Helpdesk skill but can't call the tools The ClawHub skill teaches OpenClaw about Helpdesk, but the calls run through the ClawLink plugin and your connected account. Make sure Helpdesk is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register. ### Connection succeeds but no tools appear Reconnect Helpdesk 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 Helpdesk tools Helpdesk 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 Helpdesk 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. ### Helpdesk 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 Helpdesk has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Helpdesk integration? Yes. ClawLink is the fastest way to connect OpenClaw to Helpdesk: link your Helpdesk account once in the browser and OpenClaw can call the Helpdesk API through 14 ready-made tools — no custom code or token handling. ### How do I add Helpdesk to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Helpdesk skill from ClawHub, then you click Connect in the dashboard to authorize Helpdesk. OpenClaw calls the tools from the next message — no config files, and the Helpdesk key you paste is stored server-side instead of in your environment. ### How long does it take to connect Helpdesk to OpenClaw? About two minutes. Sign in, click Connect next to Helpdesk in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Helpdesk up myself? The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Helpdesk working from chat. ### OpenClaw installed the Helpdesk skill but can't call the tools The ClawHub skill teaches OpenClaw about Helpdesk, but the calls run through the ClawLink plugin and your connected account. Make sure Helpdesk is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register. ## Related - [Connect Zendesk](https://claw-link.dev/openclaw/zendesk) — Manage support tickets, macros, users, and organizations - [Gleap tools](https://claw-link.dev/openclaw/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. - [OpenClaw Freshdesk integration](https://claw-link.dev/openclaw/freshdesk) — Handle support tickets, contacts, and helpdesk operations