# BrowserAct integrations: bots and tasks

> Run a bot and run a bot template in BrowserAct, and start a workflow when BrowserAct sends “Task completed”.

**Canonical page:** https://tray.ai/connectors/browseract-integrations/
**Categories:** Data and analytics
**Connects through:** HTTP Connector

## Overview

BrowserAct is a no-code browser automation service that builds bots to browse websites, scrape structured data and run repeatable web tasks in the cloud. Tray.ai connects to BrowserAct through the HTTP Connector, so your workflows can call the BrowserAct API alongside the rest of your stack.

## Use cases

### Bots

Read and create bots in BrowserAct from any Tray.ai workflow. The BrowserAct API covers calls such as list bots and retrieve a bot.

- List bots
- Retrieve a bot
- Run a bot

### Tasks

Read, update, and delete tasks in BrowserAct from any Tray.ai workflow. The BrowserAct API covers calls such as list tasks and retrieve a task.

- List tasks
- Retrieve a task
- Retrieve a task status

### Bot templates

Read and create bot templates in BrowserAct from any Tray.ai workflow. The BrowserAct API covers calls such as list official bot templates and retrieve a bot template.

- List official bot templates
- Retrieve a bot template
- Run a bot template

### BrowserAct events

Start a Tray.ai workflow the moment something happens in BrowserAct. BrowserAct sends events such as task completed and task failed to a Tray.ai webhook trigger.

- Task completed
- Task failed
- Task canceled

## Challenges Tray.ai solves

### Keeping BrowserAct credentials out of logs

A raw API call usually means pasting a key or token into the request, where it ends up in step inputs, logs, and screenshots.

**How Tray.ai helps:** Store BrowserAct credentials once as a Tray.ai authentication and reference them from the HTTP Connector. Tray.ai masks authentication values in logs, so the secret never shows up in a step's input or output.

### Going from the BrowserAct API docs to a working call

Translating an example request from API docs into a workflow step means copying the method, URL, headers, and body by hand.

**How Tray.ai helps:** Paste a cURL example from the BrowserAct API docs into the HTTP Connector and Tray.ai fills in the method, URL, headers, and body for you.

### Handling files and non-JSON responses

Not every API answers in JSON. Some return XML, files, or binary data, or expect a multipart upload.

**How Tray.ai helps:** The HTTP Connector parses JSON and XML responses, returns files you can pass to the next step, and sends multipart form data for uploads.

## Frequently asked questions

### Does Tray.ai connect to BrowserAct?

Yes. Tray.ai connects to BrowserAct through the HTTP Connector, which calls the BrowserAct API directly. Any call the BrowserAct API documents can run as a step in a Tray.ai workflow.

### How does Tray.ai authenticate with BrowserAct?

The BrowserAct API uses a bearer token. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.

### Can I get a dedicated BrowserAct connector?

BrowserAct runs through the HTTP Connector rather than a dedicated connector. If your team wants one, the Tray.ai connector SDK can build a dedicated BrowserAct connector from the BrowserAct API.

## Learn more

- Intelligent Integration: https://tray.ai/platform/intelligent-ipaas/
- Merlin Agent Builder: https://tray.ai/platform/merlin-agent-builder/
- Agent Gateway for MCP: https://tray.ai/platform/agent-gateway/
- Book a demo: https://tray.ai/contact/