How do I connect Browser Use to Lodol?

Authenticate Browser Use once from your workspace and every action and trigger it supports becomes available to drop into a workflow. There is no glue code to write or maintain.

All integrations

Browser Use

AI Agents

Hand a web task to a Browser Use cloud agent in plain English; it drives a real browser to research, fill in forms, pull data off pages, and report back. Follow up in the same session to keep the browser and context, and read the agent's step-by-step trace when you need to see how it got there.

Get Started Browse all integrations

8 actions

Actions

Steps your workflow can run in Browser Use.

Start a browser taskDescribe a task in plain English and a Browser Use cloud agent drives a real browser to do it: navigating, clicking, typing, and reading pages. The agent works in the background: this action returns a run ID straight away, so follow it with 'Get run status' until the run finishes, then 'Get run' to read what the agent found.

Get runFetch a Browser Use run by ID, including the agent's result, why it failed if it did, what it cost, and how many tokens it used.

Get run statusCheck just the status of a run, the cheap endpoint to poll while an agent works.

List runsList your Browser Use runs, newest first, optionally only the runs belonging to one session.

Cancel runStop a run that is still in flight. A run that has already finished is returned unchanged.

Get run eventsRead a run's event log, the agent's step-by-step trace of what it did in the browser.

List run attachmentsList the files attached to a run, with their names, types, and sizes.

Send follow-up messageSend another instruction to a session the agent is already working in; it runs as the next turn, keeping the same browser and conversation.