Actions Overview
Aiviro Editor provides roughly 65 actions organized into thematic groups. Pick a group below — each page lists its commands with their parameters.
Adding an action
| Method | How |
|---|---|
| Context menu | Right-click an element in the robot live view to get the actions that can target it, or right-click in the Commands tree to insert a non-visual action. |
| Add button | The ⊕ Add button in the Commands panel header. |
| Search | Start typing in the search box at the top of the actions menu. Results show each action's menu path, and Enter inserts the highlighted one. |
| Shortcut | The most common actions have direct shortcuts — see Keyboard shortcuts. |
Pinned actions — Click, Double click, Key Shortcut, Type Text, Get, Wait For and Section — appear at the top of the menu, above the group hierarchy, because they cover most of everyday scenario building.
The menu only offers actions that work with the connected robot. If an action you expect is missing, check which robot type is connected — see Action availability per robot type.
Parameters every action shares
Run Action
Controls whether and when the action executes. This replaces the simple enabled/disabled flag from earlier versions.
| Value | Behaviour |
|---|---|
| Enabled | Runs normally. The default. |
| Disabled | Skipped entirely — the way to park an action without deleting it. |
| Enabled (Test) | Runs only in the Test environment. |
| Enabled (Prod) | Runs only in the Production environment. |
| Run Always | Runs even when a previous action failed — use it for cleanup that must happen regardless. |
| Run on Failure | Runs only when a previous action failed — use it for recovery or error reporting. |
The environment is switched with the Environment toggle in the main toolbar, so one scenario can behave differently in test and in production without branching.
Run Always and Run on Failure replace most defensive Condition blocks.
A typical ending is: Send As Email with Run on Failure to report the problem,
plus Close All Windows with Run Always to leave the machine clean.
Required success
Present on every action that searches the screen. When on (the default), a failure stops the scenario. When off, the failure is logged and the scenario continues — useful for optional dialogs such as a cookie banner that only sometimes appears.
Wait after
How long to pause once the action has finished: Default (the value from Settings → General → Default wait after timeout), None, or a custom number of seconds.
Advanced options
Less common parameters are collapsed into an Advanced options group on the action form. Turn on Settings → General → Always show additional options to keep it expanded everywhere. Throughout this documentation such parameters are marked (Advanced options).
Keyboard
Actions in the Keyboard group of the actions menu.
Mouse
Actions in the Mouse group of the actions menu.
Wait
Actions in the Wait group of the actions menu. Waits are what make a scenario
Screen
Actions in the Screen group. They narrow down where the robot looks, which both
Start Process
Actions in the Start Process group — launching programs and cleaning up windows on
Flow Control
Actions in the Flow Control group — branching, assertions, pauses and early exit.
Loop
Actions in the Flow Control → Loop sub-group. Actions nested under a loop run once
Tools
The Tools group holds the workhorses that do not belong to a single input device —
Files
The Files group and its three sub-groups — Excel, PDF and RDP.
AI
The AI group is new since 0.14.2. It covers two different jobs: generating parts of
Project
The Project group holds actions that structure the scenario itself rather than drive
Notification
The Notification group builds a human-readable summary of what a run did, and
The Email group reads, sends and files e-mail. It was rebuilt from scratch since