Browse AI
Also an agent toolNo-code web scraping & change monitoring — run robots, retrieve captured data, manage monitors and bulk runs.
13 actions · 6 triggers
The Browse AI integration lets you connect Browse AI to your automations with 13 actions and 6 triggers — and every action is also a tool an AI agent can call. Examples: Get Status, List Robots, Get Robot, Run Task, List Robot Tasks. No blank-canvas wiring — connect it and use it in your workflows.
Every action below is also a tool an AI agent can call — the same pack powers your workflows and your agents.
Triggers 6
Events in Browse AI that can start a workflow.
Task Finished
Fires when any robot task completes (success or failure).
Task Succeeded
Fires when a robot task completes successfully.
Task Failed
Fires when a robot task completes with a failure.
Captured Data Changed
Fires when a monitor detects that captured data changed.
Table Export Finished
Fires when a table export completes successfully (Beta).
New finished task
Fires when a robot completes a new task. Set status=successful to ignore failures.
Actions 13
What Zervanor can do in Browse AI.
Robots12
List Robots
List all approved robots in the account (GET /robots).
Get Robot
Retrieve a single robot's details, including its declared input parameters, captured-text field names, and captured-list schema (GET /robots/{robotId}).
Run Task
Execute a single asynchronous data-extraction task on an approved robot (POST /robots/{robotId}/tasks). Returns immediately with the created task in in-progress status; captured data arrives via webhook or by polling get_task/list_tasks.
List Robot Tasks
Retrieve a paginated list of task executions for a robot, with status/date filters (GET /robots/{robotId}/tasks). Polling-trigger source for new finished tasks.
Get Task
Retrieve a single task's status and (on success) its captured data (GET /robots/{robotId}/tasks/{taskId}). Poll until status is terminal.
List Monitors
Retrieve a robot's configured monitors (GET /robots/{robotId}/monitors).
Get Monitor
Retrieve a single monitor by id (GET /robots/{robotId}/monitors/{monitorId}).
Create Monitor
Create a new monitoring schedule on a robot (POST /robots/{robotId}/monitors). Schedule frequency and the robot's input parameters are supplied in the body. This is a stateful recurring, billable schedule — not used as a PH-CTM-01 write test target.
Delete Monitor
Delete a robot's monitor (DELETE /robots/{robotId}/monitors/{monitorId}).
Create Webhook
Register a webhook on a robot for a given event (POST /robots/{robotId}/webhooks). No list/delete endpoint is published for v1 (browse-ai-06); manage lifecycle via the dashboard.
Create Bulk Run
Fan out a robot over many input rows in one call (POST /robots/{robotId}/bulk-runs; up to 1,000 per call, 500,000 per bulk run). Billable and irreversible.
Get Bulk Run
Retrieve a bulk run's status and per-status task counts (GET /robots/{robotId}/bulk-runs/{bulkRunId}). Individual tasks: list_tasks with robotBulkRunId filter.
Status1
Get Status
Connectivity / health check — verifies the API key and reports task-queue health (GET /status).
Nothing matches your search.
Automations using Browse AI
Build your own automation with Browse AI in the visual builder.
Frequently asked questions
What can I automate with Browse AI?
13 actions are available — for example: Get Status, List Robots, Get Robot, Run Task, List Robot Tasks, and more.
Which Browse AI events can start a workflow?
6 triggers — for example: Task Finished, Task Succeeded, Task Failed, Captured Data Changed.
Can Browse AI be used as an AI agent tool?
Yes. Every Browse AI action automatically becomes a tool an AI agent can call — the same pack powers both your workflows and your agents.
How is the Browse AI integration modelled?
Browse AI is modelled as a versioned connector pack, and the steps that need reasoning fall to first-party agents hosted in the same runtime as the workflows.