Faq
Questions before you start.
The things people ask most often about how UIA runs, where it runs, and what happens to their data. If yours isn't here, the contact page reaches a person.
Getting started
What is UIA, in one sentence?
It turns a sequence of browser steps — open, type, click, wait, read — into a task you can schedule, chain into larger jobs, and watch run line by line.
Do I need to know how to code?
No. You build a task by adding steps and pointing each one at an element on the page. Conditions, loops and variables are there when you need them, but a useful automation can be nothing more than a list of clicks and typed values.
What can I automate with it?
Anything you can do in a browser and would rather not do by hand — logging into a portal and pulling a report, filling the same form across many records, checking a page on a schedule and emailing you when something changes. If a person can do it in a browser, a task can usually repeat it.
Running and workers
What is a worker, and why do I need one?
A worker is a small agent you install on a machine you own. It runs the browser and does the actual work. You need at least one because UIA runs your automations on your hardware, not on a shared server.
Does installing a worker mean opening ports on my network?
No. The worker makes an outbound connection to UIA over a WebSocket and keeps it open. Nothing connects inward to your machine, so there are no inbound ports to open and no firewall rules to change.
Can one job run on a schedule without me watching?
Yes — that is the point of scheduling. Choose which worker runs the job and how often it should fire: hourly, daily, weekly, monthly, or a pattern of your own. You can ask for an email each time a run finishes.
What happens when a step fails?
The run stops at the failing step and keeps the record. Every run is stored with its steps, timings and screenshots, so you can see which step failed, on which pass, and what the page looked like at that moment.
Security and data
Where does the browser actually run?
On the worker you installed, on your own machine. The server schedules the run, records what happened and shows it to you, but it never opens the browser or holds the session.
What happens to the passwords I save?
Credentials are encrypted against your account before they are stored, and decrypted only on the worker that needs them for a run. They are not held in readable form on the server.
Who can see my tasks and runs?
Your account does. A job becomes visible to others only when you choose to publish or share it, and even then what you share is a copy — your credentials and run history stay with you.
Sharing
Can I give a working automation to a teammate or customer?
Yes. 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.
If I improve a shared job, do subscribers get the change automatically?
No — not silently. When you update the original, subscribers can see exactly what changed and choose whether to take the update. Nothing changes under them without their say-so.