Overview

Naming note: BrowserAct manages these automations as Bots. Some third-party integrations may still display labels such as Workflow, My Workflows, or Run a Workflow. In those interfaces, the Workflow refers to the corresponding BrowserAct Bot.

​

Before You Connect a Bot

• The Bot builds and runs successfully in BrowserAct
• Required inputs are clearly defined
• The output fields are stable
• You have copied the correct Bot ID
• You have an API Key when the connection requires one

​

Available Integration Paths

• Make: build visual business automation scenarios.
• n8n: build technical workflows with branching and transformations.
• Zapier: connect a Bot to supported triggers and actions.
• MCP: connect BrowserAct to compatible MCP clients.
• API Keys: create and manage the credentials used by supported integrations.

​

Integration Guides

• Send BrowserAct Data to Google Sheets
• Schedule BrowserAct Bot Runs
• Import and Export Make Scenarios as JSON
• Import and Export n8n Workflows as JSON

​

Typical Flow

External trigger
  -> Run BrowserAct Bot
  -> Check Task status
  -> Read structured result
  -> Send result to the next application