# How to connect Fluxguard to OpenClaw (paste one key, 13 tools) > Connect Fluxguard to OpenClaw with ClawLink: paste your Fluxguard key once and 13 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/fluxguard The usual route to Fluxguard 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 Fluxguard setup: install one ClawHub skill, connect Fluxguard in the browser, and OpenClaw can call real Fluxguard 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 Fluxguard. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Fluxguard** — 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 fluxguard # connect Fluxguard (browser OAuth) npx -y @useclawlink/cli actions fluxguard # list available actions npx -y @useclawlink/cli run fluxguard --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 Fluxguard in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Fluxguard API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from Fluxguard, 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 Fluxguard is connected in the dashboard, that agent calls the same 13 Fluxguard 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). ## Fluxguard MCP for OpenClaw Looking for a Fluxguard MCP server for OpenClaw? ClawLink connects Fluxguard to OpenClaw and exposes 13 Fluxguard 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 Fluxguard integration](https://claw-link.dev/hermes/fluxguard) works the same way. ## What the OpenClaw Fluxguard integration can do 13 Fluxguard tools are ready for OpenClaw once the account is connected. The 10 below are the ones people reach for most; your agent can call all 13. ### 10 of 13 Fluxguard tools for OpenClaw | Tool | What it does | |---|---| | **Get all categories** `fluxguard_get_all_categories` | Retrieves all categories defined in your FluxGuard account | | **Get page data** `fluxguard_get_page_data` | Retrieve comprehensive data for a monitored page in FluxGuard | | **Get sample webhook** `fluxguard_get_sample_webhook` | Retrieve a sample webhook payload | | **Get user** `fluxguard_get_user` | Retrieves the authenticated FluxGuard account's information as a user profile | | **Get webhooks** `fluxguard_get_webhooks` | Retrieves all configured webhooks for the FluxGuard account | | **Webhook notification** `fluxguard_webhook_notification` | Simulate Fluxguard webhook notification by sending change detection data to your webhook | | **Add page** `fluxguard_add_page` | Add a new page for monitoring in FluxGuard | | **Create site category** `fluxguard_create_site_category` | Creates a new site category in FluxGuard for organizing monitored websites | | **Create webhook** `fluxguard_create_webhook` | Creates a webhook endpoint registration in FluxGuard to receive real-time notifications when | | **Initiate crawl** `fluxguard_initiate_crawl` | Initiate a crawl for a session identified by siteId and sessionId | ## Example prompts **Get All Categories** > Pull the relevant data from Fluxguard, summarize it in plain English, and point out anything that needs attention. **Get Page Data** > Pull the relevant data from Fluxguard, summarize it in plain English, and point out anything that needs attention. **Get Sample Webhook** > Pull the relevant data from Fluxguard, summarize it in plain English, and point out anything that needs attention. **Get User** > Pull the relevant data from Fluxguard, 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 Fluxguard working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Fluxguard API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Fluxguard 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 Fluxguard. | 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 Fluxguard actions to the runtime in a format your agent can reliably use. | 13 tools for Fluxguard are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Fluxguard 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 Fluxguard in the browser, and the 13 tools above work from chat. There is no SDK and no config file, and the Fluxguard 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 Fluxguard skill but can't call the tools The ClawHub skill teaches OpenClaw about Fluxguard, but the calls run through the ClawLink plugin and your connected account. Make sure Fluxguard 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 Fluxguard 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 Fluxguard tools Fluxguard 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 Fluxguard 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. ### Fluxguard 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 Fluxguard has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Fluxguard integration? Yes. ClawLink is the fastest way to connect OpenClaw to Fluxguard: link your Fluxguard account once in the browser and OpenClaw can call the Fluxguard API through 13 ready-made tools — no custom code or token handling. ### How do I add Fluxguard to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Fluxguard skill from ClawHub, then you click Connect in the dashboard to authorize Fluxguard. OpenClaw calls the tools from the next message — no config files, and the Fluxguard key you paste is stored server-side instead of in your environment. ### How long does it take to connect Fluxguard to OpenClaw? About two minutes. Sign in, click Connect next to Fluxguard in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Fluxguard 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 Fluxguard working from chat. ### OpenClaw installed the Fluxguard skill but can't call the tools The ClawHub skill teaches OpenClaw about Fluxguard, but the calls run through the ClawLink plugin and your connected account. Make sure Fluxguard 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 PostHog integration](https://claw-link.dev/openclaw/posthog) — Track user behavior and feature flags - [OpenClaw DataforSEO integration](https://claw-link.dev/openclaw/dataforseo) — SEO data APIs for keywords, SERP, and site audits - [Metabase](https://claw-link.dev/openclaw/metabase) — Metabase is an open-source business intelligence tool that lets you ask questions about your data and visualize answers as charts, graphs, and dashboards.