ambacti
Explore workflows
Browser Use × Ambacti

Bring Browser Use into
the flow of work.

A little less busywork with Browser Use.

Start with Ambacti Browse capabilities
Roman aqueduct developing from a precise architectural drawing into marble.
Gather contextDo the workReview & share
Task5 capabilities
  • Execute a task

    Execute a task using an AI agent

  • Get a task

    Retrieve details of a task

  • Get many tasks

    List all tasks in your account

  • Stop a task

    Stop a running task

  • Update a task
Run8 capabilities
  • Cancel a run

    Cancel a running run

  • Create a run

    Dispatch a run without waiting for it to finish

  • Get a run

    Get the full summary of a run

  • Get run attachments

    List files the agent attached to a run

  • Get run events

    List the step-by-step event stream of a run

  • Get many runs

    List runs

  • Get run status

    Get only the status of a run, which is the cheapest poll target

  • Run a task and wait

    Dispatch a run and poll until it reaches a terminal status

Session6 capabilities
  • Cancel a queued message

    Cancel a message that is still pending on the session queue

  • Get a session

    Get session metadata

  • Get many sessions

    List sessions, one entry per conversation

  • Get the session queue

    List messages waiting on the session queue

  • Purge a session

    Permanently delete a session on a Zero Data Retention project

  • Queue a session message

    Send a follow-up message to a session

Browser5 capabilities
  • Create a browser session

    Create a standalone browser session with live and CDP URLs

  • Get a browser session

    Get browser session details

  • Get browser session downloads

    List files the browser downloaded during the session

  • Get many browser sessions

    List browser sessions

  • Stop a browser session

Frequently asked
questions.

What could an Ambacti integration do with Browser Use?

The documented operations include Task: Execute a task; Task: Get a task; Task: Get many tasks; Task: Stop a task.

Could I keep a workflow read-only?

For a read-only workflow, limit account permissions to reading data and exclude actions that create, update, or delete records.

Will every action run automatically?

Choose which steps could run on their own and which should pause for review. Changes should follow the permissions and approval rules you set.

Do I need to review actions in Browser Use?

Decide which work could run on its own and which steps need your review.