All articles

Automation (RPA)

A flow is a list of steps a profile's browser carries out like a person: the mouse travels to elements, clicks land at a random point inside them, typing has uneven pauses and pages scroll in small steps. No code needed.

The Automation page with a flow, and the buttons for import, the template gallery, mailboxes and a new flow

Make a flow

Automation → New flow, then start empty or from a template, add steps and save. Or record: open a Chrome profile with the recorder and the steps you take are written down for you.

The flow editor with a cookie-robot step

StepsFor
Open address, new tab, switch tab, close tab, reload, go back, scroll, screenshotPages
Click, hover, type text, clear, focus, choose from list, upload a file, read textElements
Press a key, move the mouse, clipboardInput
Wait (random), wait for an element, for an address, for the page, for a network answer, listen to requestsWaiting
Set a variable, random value, calculate, text operations, regex, JSON field, current address, extract to results, save to a text file, cookies, download, read an e-mail codeData
If, repeat, for each (data rows or elements), while, break, continue, stop, close the browserFlow control
Cookie robot, run JavaScript, HTTP request, run another flow, update the profile's notes and tags, log, notify, ask AI, Google SheetsOther

Elements are found with CSS selectors (#login, input[name=email]) or by text (text=Sign in). Text, addresses and selectors can use variables such as ${profile.name}, ${profile.no}, ${date}, ${random:6} (six random digits), ${loop.index}, ${row.<column>} and ${item.text}.

Read an e-mail code waits for a new message in a mailbox (IMAP) and takes the code out of it — for sign-ins that send a code by e-mail. Mailboxes are saved on this computer (Mailboxes), with their passwords in the system's protected storage.

Ask AI sends a question (variables work, such as text a step just read) to any OpenAI-compatible chat API — also one running on your own computer — and puts the answer into a variable. Google Sheets adds a row to a sheet or reads rows from it as JSON, through a service account from your own Google Cloud project (share the sheet with the account's e-mail; as an editor to add rows). Both use Connections on the Automation page: they're saved on this computer only, with the keys in the system's protected storage, and flows refer to them by name. The app sends these requests itself with your key, not the profile's browser.

Flows belong to the team: everyone in the workspace sees and runs them.

Run

Click Run, choose the profiles, how many run at the same time and how often to repeat the flow. A data file (Excel or CSV) gives each profile its own row (${row.email}), or lets every profile go through all rows. Profiles that weren't open are started and, with Close profiles this run opened on, closed again afterwards. Follow progress, logs, screenshots and errors under Runs; Export results saves what extract steps collected.

You can also run a flow on selected profiles from the profile list, and from your own scripts through the Local API.

Schedule

Schedules → New schedule runs a flow once, every day at a time, on chosen weekdays, every few minutes or hours, or by a cron rule — on chosen profiles or on every profile in a group. Schedules run on the computer where you made them while the app is open (it can be in the background).

Template gallery has flows other people shared, checked by our team before they appear. Import adds one to your flows; read its steps before you run it.

The template gallery with categories, search and Import buttons

To share one of your flows, click the share icon next to it, describe what it does and choose a category. Only the steps are shared — not your profiles, proxies or results — and only after you confirm that passwords, e-mail addresses, keys and other personal data are removed. You'll find it under Shared by me, where you can also remove it.

Plans

Automation is part of Pro and higher (the number of flows and the scheduler depend on the plan). In a team it needs the "Use automation (RPA)" permission.

Automation must follow the websites' rules and our Acceptable Use Policy. Solving captchas is not part of the app.