Why run automation locally
Cloud automation services connect web apps well, but every run passes your data through the provider and is usually counted against a plan. Much everyday automation never needed the internet in the first place: renaming and filing documents, reshaping a CSV, running a script at a set time, or clicking through a desktop program that has no API. Running those locally keeps data on the machine and removes per-run limits.
Aevornix Automate
Aevornix AutomateA visual canvas with branching, loops, retries and subflows, triggers of seven kinds and a background runner.
Aevornix WorkspaceStarts Automate workflows from workspace changes and Forms responses, and lets workflows create tasks, records and pages.
Aevornix FormsCollects the data that workflows then process, with watch folders importing response files as they arrive.
What Automate can do
The verified capabilities of the current release.
- Triggers: manual, schedule, file and folder, polling, hotkey, clipboard and application events.
- Recorded steps and Windows UI Automation for programs without an API.
- File, data, JSON, CSV and XML steps.
- HTTP requests with saved, encrypted credentials, for when you do want a web service.
- PowerShell, command and Python script steps.
- Run history with each step's input and output, breakpoints and pinned test data.
- A permission review before a workflow is activated or imported.
What works offline and what does not
Everything that happens on the computer runs with no connection. A step that calls a web service needs that service to be reachable, and connecting to a service needs the service's own API or endpoint. Automate runs on Windows 10 or 11 (64-bit) only.
Examples of local workflows
Local automation is at its best on the repetitive jobs that sit between applications on one computer.
- Watch a scans folder and file each new PDF into a client folder by a name pattern.
- Take a CSV export every morning, reshape it, and save it as JSON or XML for another system.
- Run a PowerShell or Python script on a schedule and keep the input and output of every run in the run history.
- Operate a desktop program that has no API by replaying recorded Windows UI Automation steps.
- When a Forms response arrives in Workspace, create a task and a record for someone to follow up.
Compare and learn
Our guide what is desktop workflow automation explains the category. For side by side views, see Aevornix Automate and Zapier, Aevornix Automate and Power Automate and desktop alternatives to Zapier. Automate is a one-time purchase; see licences.
Frequently asked questions
Do workflows keep running when the editor is closed?
Yes. A background runner keeps triggers active while the editor is closed.
Can Automate control desktop programs?
Yes, through recorded steps and Windows UI Automation.
Are there limits on how many times a workflow runs?
Automate runs on your own computer under a one-time licence; the product does not meter runs.
Is my data sent to a cloud service?
No. Workflows run locally with no account, no cloud service and no telemetry. Only steps you build to call a web service send data to that service.