Sanaf AI
Start free
AI Web Scraping

BrowserAct, worked by an AI employee

Not another app for your team to learn, and not a set of rules for you to build. You hire an AI employee, you give it access to your BrowserAct account, and you ask it for things in Slack or Teams the way you would ask anyone else on the team. There is nothing to map and nothing to maintain.

  • AI Web Scraping
  • Connects with a key
  • 11 ready-made tools
  • Asked in Slack or Teams
At work

An illustration of how the conversation reads, not a transcript from a client account.

What BrowserAct is

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

You paste in a key from your own BrowserAct account. It is kept encrypted, and you can withdraw it from inside BrowserAct whenever you like.

How a run works

One message in, the work done in BrowserAct.

  1. 01

    You ask

    You message your AI employee in the chat your team already has open, in one sentence, in your own words.

  2. 02

    It works out the step

    It decides what the job needs in BrowserAct. You do not pick anything from a menu or wire anything together.

  3. 03

    It does the work

    Signed in to your own BrowserAct account, inside the access you granted it, doing the thing you asked for.

  4. 04

    It reports back

    It tells you what it did, in the same thread. If it could not do something, it says so rather than guessing.

11 tools it already has

What it can do in BrowserAct

These are the ready-made tools your AI employee already has in BrowserAct. It is not limited to them, but it never has to be taught these.

  • Cancel TaskImmediately 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 ca
  • Get TaskReturn either a task's current status or its full progress, outputs, files, live-view details, and failure information.
  • Get WorkflowReturn a custom workflow's metadata and expected input parameter definitions before a run.
  • Get Workflow TemplateReturn an official template's metadata and expected input parameter definitions before a run.
  • List Proxy RegionsReturn the supported proxy region names and codes for official template runs.
  • List TasksReturn one cursor-controlled page of workflow tasks, optionally filtered by status, workflow, name, or creation time.
  • List Workflow TemplatesSearch official BrowserAct workflow templates and return one cursor-controlled page of summaries.
  • List WorkflowsReturn one cursor-controlled page of custom workflows in the connected workspace.
  • Resume TaskResume 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 WorkflowStart a custom BrowserAct workflow. This consumes credits and executes its configured browser actions, which may irreversibly modify external websites.
  • Run Workflow TemplateStart an official BrowserAct workflow template. This consumes credits and executes its browser actions, which may cause irreversible effects on external websites.
Access, and who is in charge of it

You stay the boss of your BrowserAct account.

Nothing connects until you approve it. You grant access one app at a time, you can take it back the same way, and everything your AI employee does in there is written down where you can see it.

How we handle your data
  • It signs in to your own BrowserAct account. You are not moving anything into ours.
  • You grant access one app at a time, and you can take it back the same way.
  • Everything it does in BrowserAct is written down, with what it did and when.
  • Anything you tell it to check with you first, it checks with you first.
Other apps in the same corner of the business

It works in BrowserAct and the rest of your software in the same job

A real job rarely stays in one place. Reading a message in one app, checking a record in another and writing the result in a third is one request to your AI employee, not three.

See every app

Questions people ask about BrowserAct

Can an AI employee really work inside BrowserAct?
Yes. It signs in to your own BrowserAct account and works in it the way a new hire would, from the chat your team already has open. Nobody installs anything, and nobody learns a new screen.
Do I have to move anything out of BrowserAct?
No. Nothing moves and nothing is replaced. Your records stay in BrowserAct, your team carries on in the same screens they used yesterday, and your AI employee works alongside them in there.
How does it get into my BrowserAct account?
You paste in a key from your own BrowserAct account. It is kept encrypted, and you can withdraw it from inside BrowserAct whenever you like. You approve it before anything connects, and you can take the access back the same way you gave it.
What can it actually do in BrowserAct?
It has 11 ready-made tools in BrowserAct today, among them Cancel Task, Get Task and Get Workflow. The full list is on this page. It is not limited to those, but it never has to be taught them.
Can it use BrowserAct and the rest of my software in the same job?
Yes, and that is usually the point. Reading a message in one app, checking a record in BrowserAct and writing the result somewhere else is one request to your AI employee, not three separate ones you stitch together.
Who decides what it is allowed to do in BrowserAct?
You do. You grant access one app at a time and can withdraw it at any time, anything you ask it to check with you first it checks with you first, and everything it does in BrowserAct is written down with what it did and when.