BrowserAct integrations and automation

Describe what should happen in BrowserAct, and when, in plain words. Whenever builds the workflow and runs it on a schedule, on a webhook, or when another app sends an event.

Connection requirements, provider permissions and optional AI usage apply. Read the runtime limits.

Start for freeNo credit card requiredAI building has weekly usage limits.

BrowserAct on Whenever

About BrowserAct

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

How Whenever connects

Through its API, using the credentials and permissions required by the provider.

Build it from your AI client

Connect Claude, Cursor or Codex to the Whenever MCP server and your coding agent can build and deploy the BrowserAct workflow. It runs on Whenever afterwards, on its schedule or webhook, with the chat closed.

Set up the Whenever MCP server