Browser automation & IPA
Build the task once. A worker runs it from then on.
UIA turns a sequence of browser steps — open, type, click, wait, extract — into a task you can schedule, chain into jobs, and watch run line by line. The browser opens on a machine you own, so the accounts you automate never leave it.
- 01Openportal.example.com/loginqueued
- 02Type#usernamequeued
- 03Type#passwordqueued
- 04Clickbutton[type=submit]queued
- 05Wait.orders-tablequeued
- 06Extracttr.order → orders.csvqueued
- 07Send Emailops@example.comqueued
What you build
Three things, and they nest.
Everything in UIA is made of the same parts, so what you learn on a two-step task still applies when a job is running forty of them across three sites.
An ordered list of steps
Pick an action, point it at an element, give it a value. Conditions, loops and variables are there when a page fights back — and you can call one task from inside another instead of copying steps.
Tasks strung together
Chain tasks into a flow, pass values between them, branch on what a page returned. A job keeps its own run history, so you can see which step failed and on which pass.
When it should happen
Hourly, daily, weekly, monthly, or a rule of your own. Choose which worker takes it and whether you want an email when the run finishes.
How it runs
From a blank task to a scheduled run.
- 01
Build the steps
Add steps in the builder and run them one at a time while you watch the live browser view. When a selector is wrong you see it immediately, not in tomorrow's log.
- 02
Register a worker
Download the agent, run it on the machine that should do the work, and paste the token once. It connects back over a WebSocket and appears in your worker list. No inbound ports, no firewall rules.
- 03
Hand it a schedule
Assign the job to a worker and set when it should fire. Runs stream to the console as they happen, and every one is kept with its steps, timings and screenshots.
Where it executes
Your machines do the work.
Tasks run on agent workers you install and control — a desk PC, an office machine, a VM in your own rack. The server schedules, records and shows you the run; it never opens the browser or holds the session. Credentials are encrypted against your account before they are stored, and decrypted only on the worker that needs them.
- Runs onWindows · macOS · Linux
- Connectionoutbound WebSocket only
- BrowserChromium
- Credentialsencrypted per account
- InterfaceEnglish · 한국어 · Español
Sharing
Hand a working job to someone else.
Publish a job to the marketplace, or keep it unlisted and send a private link. Whoever subscribes gets a read-only copy that runs on their worker with their own credentials — and when you change the original, they see exactly what changed before they take it.