# How to connect BrowserAct to OpenClaw (paste one key, 11 tools) > Connect BrowserAct to OpenClaw with ClawLink: paste your BrowserAct key once and 11 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/browseract The usual route to BrowserAct 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 BrowserAct setup: install one ClawHub skill, connect BrowserAct in the browser, and OpenClaw can call real BrowserAct 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 BrowserAct. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect BrowserAct** — 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 browseract # connect BrowserAct (browser OAuth) npx -y @useclawlink/cli actions browseract # list available actions npx -y @useclawlink/cli run browseract --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 BrowserAct in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your BrowserAct API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from BrowserAct, 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 BrowserAct is connected in the dashboard, that agent calls the same 11 BrowserAct 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). ## BrowserAct MCP for OpenClaw Looking for a BrowserAct MCP server for OpenClaw? ClawLink connects BrowserAct to OpenClaw and exposes 11 BrowserAct 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 BrowserAct integration](https://claw-link.dev/hermes/browseract) works the same way. ## What the OpenClaw BrowserAct integration can do 11 BrowserAct tools are ready for OpenClaw once the account is connected. ### All 11 BrowserAct tools for OpenClaw | Tool | What it does | |---|---| | **Get task** `browseract_get_task` | Return either a task's current status or its full progress, outputs, files, live-view details | | **Get workflow** `browseract_get_workflow` | Return a custom workflow's metadata and expected input parameter definitions before a run | | **Get workflow template** `browseract_get_workflow_template` | Return an official template's metadata and expected input parameter definitions before a run | | **List proxy regions** `browseract_list_proxy_regions` | Return the supported proxy region names and codes for official template runs | | **List tasks** `browseract_list_tasks` | Return one cursor-controlled page of workflow tasks, optionally filtered by status, workflow | | **List workflow templates** `browseract_list_workflow_templates` | Search official BrowserAct workflow templates and return one cursor-controlled page of summaries | | **List workflows** `browseract_list_workflows` | Return one cursor-controlled page of custom workflows in the connected workspace | | **Resume task** `browseract_resume_task` | Resume a paused task from its current state | | **Cancel task** `browseract_cancel_task` | Immediately and permanently cancel a running BrowserAct task | | **Run workflow** `browseract_run_workflow` | Start a custom BrowserAct workflow | | **Run workflow template** `browseract_run_workflow_template` | Start an official BrowserAct workflow template | ## Example prompts **Get Task** > Pull the relevant data from BrowserAct, summarize it in plain English, and point out anything that needs attention. **Get Workflow** > Pull the relevant data from BrowserAct, summarize it in plain English, and point out anything that needs attention. **Get Workflow Template** > Pull the relevant data from BrowserAct, summarize it in plain English, and point out anything that needs attention. **List Proxy Regions** > List the relevant items in BrowserAct, 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 BrowserAct working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the BrowserAct API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected BrowserAct 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 BrowserAct. | 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 BrowserAct actions to the runtime in a format your agent can reliably use. | 11 tools for BrowserAct are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes BrowserAct 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 BrowserAct in the browser, and the 11 tools above work from chat. There is no SDK and no config file, and the BrowserAct 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 BrowserAct skill but can't call the tools The ClawHub skill teaches OpenClaw about BrowserAct, but the calls run through the ClawLink plugin and your connected account. Make sure BrowserAct 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 BrowserAct 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 BrowserAct tools BrowserAct 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 BrowserAct 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. ### BrowserAct 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 BrowserAct has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw BrowserAct integration? Yes. ClawLink is the fastest way to connect OpenClaw to BrowserAct: link your BrowserAct account once in the browser and OpenClaw can call the BrowserAct API through 11 ready-made tools — no custom code or token handling. ### How do I add BrowserAct to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink BrowserAct skill from ClawHub, then you click Connect in the dashboard to authorize BrowserAct. OpenClaw calls the tools from the next message — no config files, and the BrowserAct key you paste is stored server-side instead of in your environment. ### How long does it take to connect BrowserAct to OpenClaw? About two minutes. Sign in, click Connect next to BrowserAct in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring BrowserAct 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 BrowserAct working from chat. ### OpenClaw installed the BrowserAct skill but can't call the tools The ClawHub skill teaches OpenClaw about BrowserAct, but the calls run through the ClawLink plugin and your connected account. Make sure BrowserAct 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 - [DataRobot tools](https://claw-link.dev/openclaw/datarobot) — DataRobot is a machine learning platform that automates model building, deployment, and monitoring, enabling organizations to derive predictive insights from large datasets. - [Connect Chatbotkit](https://claw-link.dev/openclaw/chatbotkit) — ChatBotKit is a platform that enables developers to build and manage AI-powered chatbots, offering comprehensive APIs and SDKs for seamless integration into applications. - [Connect Just One API](https://claw-link.dev/openclaw/just-one-api) — Just One API provides unified access to public social media, creator, entertainment, and ecommerce data across hundreds of metered endpoints.