# How to connect HelpSpot to OpenClaw (paste one key, 10 tools) > Connect HelpSpot to OpenClaw with ClawLink: paste your HelpSpot key once and 10 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/help-spot The usual route to HelpSpot 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 HelpSpot setup: install one ClawHub skill, connect HelpSpot in the browser, and OpenClaw can call real HelpSpot 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 HelpSpot. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect HelpSpot** — 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 help-spot # connect HelpSpot (browser OAuth) npx -y @useclawlink/cli actions help-spot # list available actions npx -y @useclawlink/cli run help-spot --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 HelpSpot in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your HelpSpot API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from HelpSpot, summarize it in plain English, and point out anything that needs attention. ### 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 HelpSpot is connected in the dashboard, that agent calls the same 10 HelpSpot 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). ## HelpSpot MCP for OpenClaw Looking for a HelpSpot MCP server for OpenClaw? ClawLink connects HelpSpot to OpenClaw and exposes 10 HelpSpot 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 HelpSpot integration](https://claw-link.dev/hermes/help-spot) works the same way. ## What the OpenClaw HelpSpot integration can do 10 HelpSpot tools are ready for OpenClaw once the account is connected. ### All 10 HelpSpot tools for OpenClaw | Tool | What it does | |---|---| | **Get current user** `help_spot_get_current_user` | Return the connected HelpSpot staff user's identity, defaults, and support capabilities without | | **Get request** `help_spot_get_request` | Return one support request with normalized history and optional time total; fail clearly when | | **List filters** `help_spot_list_filters` | List the connected staff user's saved and built-in queue filters, including symbolic selectors | | **List saved responses** `help_spot_list_saved_responses` | List reusable response templates available to the connected staff user, either all templates or | | **List support options** `help_spot_list_support_options` | List IDs and labels used to categorize, assign, route, or set the status of HelpSpot requests | | **Run filter** `help_spot_run_filter` | Return one cursor-controlled page of request summaries from a saved or built-in HelpSpot queue | | **Search requests** `help_spot_search_requests` | Search support requests by text, customer, state, assignment, or date and return one concise | | **Set request subscription** `help_spot_set_request_subscription` | Subscribe or unsubscribe a staff user from updates to one support request | | **Create request** `help_spot_create_request` | Create a staff-side support request with an initial customer-visible or internal note | | **Update request** `help_spot_update_request` | Update request, customer, assignment, and state fields and optionally append one | ## Example prompts **Get Current User** > Pull the relevant data from HelpSpot, summarize it in plain English, and point out anything that needs attention. **Get Request** > Pull the relevant data from HelpSpot, summarize it in plain English, and point out anything that needs attention. **List Filters** > List the relevant items in HelpSpot, group them by priority, and recommend what OpenClaw should do next. **List Saved Responses** > List the relevant items in HelpSpot, 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 HelpSpot working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the HelpSpot API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected HelpSpot 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 HelpSpot. | 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 HelpSpot actions to the runtime in a format your agent can reliably use. | 10 tools for HelpSpot are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes HelpSpot 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 HelpSpot in the browser, and the 10 tools above work from chat. There is no SDK and no config file, and the HelpSpot 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 HelpSpot skill but can't call the tools The ClawHub skill teaches OpenClaw about HelpSpot, but the calls run through the ClawLink plugin and your connected account. Make sure HelpSpot 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 HelpSpot 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 HelpSpot tools HelpSpot 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 HelpSpot 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. ### HelpSpot 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 HelpSpot has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw HelpSpot integration? Yes. ClawLink is the fastest way to connect OpenClaw to HelpSpot: link your HelpSpot account once in the browser and OpenClaw can call the HelpSpot API through 10 ready-made tools — no custom code or token handling. ### How do I add HelpSpot to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink HelpSpot skill from ClawHub, then you click Connect in the dashboard to authorize HelpSpot. OpenClaw calls the tools from the next message — no config files, and the HelpSpot key you paste is stored server-side instead of in your environment. ### How long does it take to connect HelpSpot to OpenClaw? About two minutes. Sign in, click Connect next to HelpSpot in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring HelpSpot 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 HelpSpot working from chat. ### OpenClaw installed the HelpSpot skill but can't call the tools The ClawHub skill teaches OpenClaw about HelpSpot, but the calls run through the ClawLink plugin and your connected account. Make sure HelpSpot 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 - [Zendesk](https://claw-link.dev/openclaw/zendesk) — Manage support tickets, macros, users, and organizations - [OpenClaw Gleap integration](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. - [Freshdesk](https://claw-link.dev/openclaw/freshdesk) — Handle support tickets, contacts, and helpdesk operations