User Guide
From a blank task to a scheduled automation.
UIA automates a browser by running the same steps a person would — open, type, click, wait, read. You build that sequence once; a worker you control runs it from then on. This guide walks the whole path, and takes about ten minutes to read.
The pieces
Five words that do most of the work.
Everything in UIA is built from these. Learn them on a two-step task and the same ideas hold when a job is running forty steps across three sites.
- Step
- A single browser action — open a page, type into a field, click a button, wait for something, read a value back out.
- Task
- An ordered list of steps that runs top to bottom. Conditions, loops and variables handle the pages that don't behave, and one task can call another instead of repeating steps.
- Job
- Several tasks strung together, passing values between them and branching on what a page returned. Each job keeps its own run history.
- Worker
- A small agent you install on a machine you own. It runs the browser and does the actual work; the server only schedules and records.
- Schedule
- The rule that decides when a job runs — hourly, daily, weekly, monthly, or a pattern of your own.
Walkthrough
Five steps, start to finish.
- 01
Build a task
Open the builder and add steps one at a time. Point each action at an element on the page and give it a value — a URL to open, text to type, a button to click. Steps run in the order you place them.
- 02
Test it while you watch
Run steps one at a time against a live browser view. When a selector points at the wrong element you see it immediately and fix it there, rather than discovering it in tomorrow's run log.
- 03
Install a worker
Download the agent and run it on the machine that should do the work. Paste your token once. It connects back to UIA over an outbound WebSocket and appears in your worker list — no inbound ports to open, no firewall rules to change.
- 04
Assign and schedule
Group your tasks into a job if you need more than one, choose which worker should run it, and set when it should fire. Ask for an email when a run finishes if you want to be told.
- 05
Watch the runs
Runs stream to the console as they happen. Every run is kept with its steps, timings and screenshots, so when something fails you can see which step, on which pass, and what the page looked like at the time.
Where things run
Your machine does the work.
The browser opens on the worker you installed, not on our servers. Credentials you save are encrypted against your account and decrypted only on the worker that needs them — so the accounts you automate stay on hardware you control. The server schedules the run, records what happened, and shows it to you; it never holds the session.
Sharing
Hand a working job to someone else.
Publish a job so others can find it, or keep it unlisted and send a private link. Whoever subscribes gets a read-only copy that runs on their own worker with their own credentials. When you change the original, they see exactly what changed before they choose to take the update.