BrowserAct
BrowserAct runs hosted browser-automation workflows and exposes task execution, workflow discovery, templates, and proxy-region APIs.
Integration
- Vendor
- BrowserAct
- Category
- other
- Auth
- API_KEY
- Tools
- 11
- Composio slug
browseract
Tools
- 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.
Setup
- Create or open a Switchy Project.
- Open Integrations and connect BrowserAct.
- Authorise through api_key. Switchy stores the connection against your org.
- Everyone in the Project can now @-mention the BrowserAct tools in chat.
What teammates see: by default, memories from BrowserAct are scoped to the Project (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Projects have used this MCP together with a given model.