# How to connect Beaconstac to OpenClaw (paste one key, 21 tools) > Connect Beaconstac to OpenClaw with ClawLink: paste your Beaconstac key once and 21 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/beaconstac The usual route to Beaconstac 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 Beaconstac setup: install one ClawHub skill, connect Beaconstac in the browser, and OpenClaw can call real Beaconstac 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 Beaconstac. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Beaconstac** — 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 beaconstac # connect Beaconstac (browser OAuth) npx -y @useclawlink/cli actions beaconstac # list available actions npx -y @useclawlink/cli run beaconstac --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 Beaconstac in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Beaconstac API key once. Verify the connection by asking OpenClaw: > List the relevant items in Beaconstac, 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 Beaconstac is connected in the dashboard, that agent calls the same 21 Beaconstac 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). ## Beaconstac MCP for OpenClaw Looking for a Beaconstac MCP server for OpenClaw? ClawLink connects Beaconstac to OpenClaw and exposes 21 Beaconstac 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 Beaconstac integration](https://claw-link.dev/hermes/beaconstac) works the same way. ## What the OpenClaw Beaconstac integration can do 21 Beaconstac tools are ready for OpenClaw once the account is connected. The 18 below are the ones people reach for most; your agent can call all 21. ### 18 of 21 Beaconstac tools for OpenClaw | Tool | What it does | |---|---| | **List bulk qr codes** `beaconstac_list_bulk_qr_codes` | List Bulk QR Code collections | | **List organizations** `beaconstac_list_organizations` | List all organizations accessible to the authenticated account | | **List places** `beaconstac_list_places` | List your Places | | **List qr templates** `beaconstac_list_qr_templates` | List all QR code templates in your account | | **List tags** `beaconstac_list_tags` | List all tags with optional filtering and pagination | | **List users** `beaconstac_list_users` | List all users with optional filtering, searching, ordering, and pagination | | **Period overview** `beaconstac_period_overview` | Get period overview analytics for products including counts, impressions, and conversion | | **Product overview** `beaconstac_product_overview` | Get analytics overview for a specified product type over a given time interval | | **Retrieve qr code** `beaconstac_retrieve_qr_code` | Retrieve detailed information about a specific QR Code by its ID | | **Retrieve user** `beaconstac_retrieve_user` | Retrieve the details of an existing User by ID | | **Create place** `beaconstac_create_place` | Create a new place for location-based assets | | **Create qr template** `beaconstac_create_qr_template` | Creates a new QR Code template with customizable design attributes | | **Create tag** `beaconstac_create_tag` | Create a new tag for organizing QR Codes and other objects | | **Create user** `beaconstac_create_user` | Create a new User | | **Update place** `beaconstac_update_place` | Update the specified Place by ID | | **Update qr code** `beaconstac_update_qr_code` | Update an existing QR Code by its ID | | **Update tag** `beaconstac_update_tag` | Update an existing tag by its ID | | **Update user** `beaconstac_update_user` | Update an existing User | ## Example prompts **List Bulk Qr Codes** > List the relevant items in Beaconstac, group them by priority, and recommend what OpenClaw should do next. **List Organizations** > List the relevant items in Beaconstac, group them by priority, and recommend what OpenClaw should do next. **List Places** > List the relevant items in Beaconstac, group them by priority, and recommend what OpenClaw should do next. **List Qr Templates** > List the relevant items in Beaconstac, 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 Beaconstac working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Beaconstac API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Beaconstac 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 Beaconstac. | 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 Beaconstac actions to the runtime in a format your agent can reliably use. | 21 tools for Beaconstac are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Beaconstac 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 Beaconstac in the browser, and the 21 tools above work from chat. There is no SDK and no config file, and the Beaconstac 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 Beaconstac skill but can't call the tools The ClawHub skill teaches OpenClaw about Beaconstac, but the calls run through the ClawLink plugin and your connected account. Make sure Beaconstac 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 Beaconstac 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 Beaconstac tools Beaconstac 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 Beaconstac 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. ### Beaconstac 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 Beaconstac has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Beaconstac integration? Yes. ClawLink is the fastest way to connect OpenClaw to Beaconstac: link your Beaconstac account once in the browser and OpenClaw can call the Beaconstac API through 21 ready-made tools — no custom code or token handling. ### How do I add Beaconstac to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Beaconstac skill from ClawHub, then you click Connect in the dashboard to authorize Beaconstac. OpenClaw calls the tools from the next message — no config files, and the Beaconstac key you paste is stored server-side instead of in your environment. ### How long does it take to connect Beaconstac to OpenClaw? About two minutes. Sign in, click Connect next to Beaconstac in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Beaconstac 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 Beaconstac working from chat. ### OpenClaw installed the Beaconstac skill but can't call the tools The ClawHub skill teaches OpenClaw about Beaconstac, but the calls run through the ClawLink plugin and your connected account. Make sure Beaconstac 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 ActiveCampaign](https://claw-link.dev/openclaw/activecampaign) — Marketing automation, CRM, and email marketing - [OpenClaw Benchmark Email integration](https://claw-link.dev/openclaw/benchmark-email) — Benchmark Email is a comprehensive email marketing platform offering tools for creating, sending, and analyzing email campaigns. - [Mailchimp tools](https://claw-link.dev/openclaw/mailchimp) — Create email campaigns and manage audiences