Connect BrowserAct to your AI agent

Data & Analytics 11 actions available

BrowserAct runs hosted browser-automation workflows and exposes task execution, workflow discovery, templates, and proxy-region APIs.

We set up the connection using your own BrowserAct account, with keys you control, and keep it running. Your agent picks it up and starts doing the work.

What your agent can do in BrowserAct

Each one is a real action the agent can take on its own, the same things a person clicking around BrowserAct could do. Read-only by default; write actions are confirmed against your policy.

  • Cancel Task Immediately and permanently cancel a running BrowserAct task. The canceled run cannot be resumed or recovered. A task already in a terminal state is also treated as successfully canceled.
  • Get Task Return either a task's current status or its full progress, outputs, files, live-view details, and failure information.
  • Get Workflow Return a custom workflow's metadata and expected input parameter definitions before a run.
  • Get Workflow Template Return an official template's metadata and expected input parameter definitions before a run.
  • List Proxy Regions Return the supported proxy region names and codes for official template runs.
  • List Tasks Return one cursor-controlled page of workflow tasks, optionally filtered by status, workflow, name, or creation time.
  • List Workflows Return one cursor-controlled page of custom workflows in the connected workspace.
  • List Workflow Templates Search official BrowserAct workflow templates and return one cursor-controlled page of summaries.
  • Resume Task Resume a paused task from its current state. Finished, failed, and canceled tasks cannot be resumed. BrowserAct also treats an already-running task as a successful request.
  • Run Workflow Start a custom BrowserAct workflow. This consumes credits and executes its configured browser actions, which may irreversibly modify external websites.
  • Run Workflow Template Start an official BrowserAct workflow template. This consumes credits and executes its browser actions, which may cause irreversible effects on external websites.

How we connect it

  1. 1

    Connect your account

    You create a key in BrowserAct, a key you create and control, and paste it in once. It lives in a secrets store on your server, not with us.

  2. 2

    Set the guardrails

    Read-only by default. You choose which write actions the agent may take, and anything outside that policy gets confirmed with you first.

  3. 3

    We keep it running

    Health checks on every connection, updates handled for you, and we watch the first week of activity to make sure the work lands.

BrowserAct questions, answered.

With a key you create and control. You paste it in once, it is stored in a secrets store on your server, permissions are scoped to the minimum the agent needs, and you can revoke it at any time.
The actions BrowserAct's API allows, the same things a person clicking around the app could do. Connections start read-only by default; write actions are confirmed against the policy you set before the agent takes them.
Connections are priced per tool on top of the base plan. Some are included, some are premium. See pricing for how connection charges work.
Standard tools are ready inside 7 business days of the setup call. We test the connection end to end, walk you through how the agent uses it, and watch the first week of activity.

Ready to put BrowserAct to work?

Tell us what your team runs on. We set up the connection, secure it, and your agent takes it from there.

All product names, logos, and brands are property of their respective owners; used for identification only. ZeroToClaw is not affiliated with or endorsed by BrowserAct.