# How to connect Hotspotsystem to OpenClaw (paste one key, 19 tools) > Connect Hotspotsystem to OpenClaw with ClawLink: paste your Hotspotsystem key once and 19 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/hotspotsystem The usual route to Hotspotsystem 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 Hotspotsystem setup: install one ClawHub skill, connect Hotspotsystem in the browser, and OpenClaw can call real Hotspotsystem 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 Hotspotsystem. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Hotspotsystem** — 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 hotspotsystem # connect Hotspotsystem (browser OAuth) npx -y @useclawlink/cli actions hotspotsystem # list available actions npx -y @useclawlink/cli run hotspotsystem --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 Hotspotsystem in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Hotspotsystem API key once. Verify the connection by asking OpenClaw: > Use Hotspotsystem to customers list and walk me through the result in plain English. ### 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 Hotspotsystem is connected in the dashboard, that agent calls the same 19 Hotspotsystem 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). ## Hotspotsystem MCP for OpenClaw Looking for a Hotspotsystem MCP server for OpenClaw? ClawLink connects Hotspotsystem to OpenClaw and exposes 19 Hotspotsystem 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 Hotspotsystem integration](https://claw-link.dev/hermes/hotspotsystem) works the same way. ## What the OpenClaw Hotspotsystem integration can do 19 Hotspotsystem tools are ready for OpenClaw once the account is connected. ### All 19 Hotspotsystem tools for OpenClaw | Tool | What it does | |---|---| | **Customers list** `hotspotsystem_customers_list` | Lists all customers in the HotspotSystem account with optional filtering | | **Customers list by location** `hotspotsystem_customers_list_by_location` | Lists all customers associated with a specific HotspotSystem location | | **Get locations options** `hotspotsystem_get_locations_options` | Get simplified list of locations as dropdown options | | **Get me** `hotspotsystem_get_me` | Verify the resource owner's credentials and retrieve authenticated user information | | **List paid transactions** `hotspotsystem_list_paid_transactions` | List paid transactions globally across all locations | | **Locations list** `hotspotsystem_locations_list` | List the resource owner's locations | | **Misc ping** `hotspotsystem_misc_ping` | Perform health check against the HotspotSystem API | | **Subscribers list** `hotspotsystem_subscribers_list` | List newsletter subscribers across all locations with optional filtering, sorting, and | | **Subscribers list by location** `hotspotsystem_subscribers_list_by_location` | List subscribers by location | | **Transactions list mac** `hotspotsystem_transactions_list_mac` | List MAC-based transactions | | **Transactions list mac by location** `hotspotsystem_transactions_list_mac_by_location` | Lists MAC address authentication transactions for a specific location | | **Transactions list paid by location** `hotspotsystem_transactions_list_paid_by_location` | List paid transactions by location | | **Transactions list social** `hotspotsystem_transactions_list_social` | List social transactions | | **Transactions list social by location** `hotspotsystem_transactions_list_social_by_location` | List social transactions by location | | **Transactions list voucher** `hotspotsystem_transactions_list_voucher` | List voucher transactions globally across all locations | | **Transactions list voucher by location** `hotspotsystem_transactions_list_voucher_by_location` | List voucher transactions by location | | **Vouchers list** `hotspotsystem_vouchers_list` | List the resource owner's vouchers across all locations | | **Vouchers list by location** `hotspotsystem_vouchers_list_by_location` | Retrieves all vouchers associated with a specific location in the HotspotSystem | | **Generate voucher v1** `hotspotsystem_generate_voucher_v1` | Generates an access voucher code on-demand for a specific location | ## Example prompts **Customers List** > Use Hotspotsystem to customers list and walk me through the result in plain English. **Customers List By Location** > Use Hotspotsystem to customers list by location and walk me through the result in plain English. **Get Locations Options** > Pull the relevant data from Hotspotsystem, summarize it in plain English, and point out anything that needs attention. **Get Me** > Pull the relevant data from Hotspotsystem, 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 OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Hotspotsystem working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Hotspotsystem API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Hotspotsystem 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 Hotspotsystem. | 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 Hotspotsystem actions to the runtime in a format your agent can reliably use. | 19 tools for Hotspotsystem are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Hotspotsystem 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 Hotspotsystem in the browser, and the 19 tools above work from chat. There is no SDK and no config file, and the Hotspotsystem 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 Hotspotsystem skill but can't call the tools The ClawHub skill teaches OpenClaw about Hotspotsystem, but the calls run through the ClawLink plugin and your connected account. Make sure Hotspotsystem 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 Hotspotsystem 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 Hotspotsystem tools Hotspotsystem 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 Hotspotsystem 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. ### Hotspotsystem 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 Hotspotsystem has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Hotspotsystem integration? Yes. ClawLink is the fastest way to connect OpenClaw to Hotspotsystem: link your Hotspotsystem account once in the browser and OpenClaw can call the Hotspotsystem API through 19 ready-made tools — no custom code or token handling. ### How do I add Hotspotsystem to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Hotspotsystem skill from ClawHub, then you click Connect in the dashboard to authorize Hotspotsystem. OpenClaw calls the tools from the next message — no config files, and the Hotspotsystem key you paste is stored server-side instead of in your environment. ### How long does it take to connect Hotspotsystem to OpenClaw? About two minutes. Sign in, click Connect next to Hotspotsystem in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Hotspotsystem 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 Hotspotsystem working from chat. ### OpenClaw installed the Hotspotsystem skill but can't call the tools The ClawHub skill teaches OpenClaw about Hotspotsystem, but the calls run through the ClawLink plugin and your connected account. Make sure Hotspotsystem 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 - [OpenClaw GitHub integration](https://claw-link.dev/openclaw/github) — Manage repositories, issues, pull requests, and workflows - [PagerDuty](https://claw-link.dev/openclaw/pagerduty) — Manage incidents, on-call schedules, and services - [Connect SafetyCulture](https://claw-link.dev/openclaw/safetyculture) — SafetyCulture (formerly iAuditor) is a workplace operations platform that enables teams to conduct digital inspections, manage audits, track issues, schedule tasks, and maintain compliance through mobile and web applications.