Quick Start
Estimated time: 30 minutes Follow this end-to-end walkthrough to go from a fresh installation of Aiviro Editor to a robot that runs by itself on a schedule.
1. Activate your licence
- Launch Aiviro Editor.
- Open Settings → Edit Configuration → Aiviro → Account.
- Paste your Client ID and API Key, then click Test Credentials.
- Wait for the success message, then save and restart the Editor.

2. Connect a robot
Click Connect (Shift+R) and pick a robot type:
- Desktop — runs on your local PC. Requires two monitors.
- RDP — connects to a remote Windows session. Recommended for production.
- Web — automates Google Chrome through ChromeDriver.
Give the configuration a Profile Name, fill in the connection details, save the profile, and click Connect. Details of every field are in Robot Types & Configuration.
3. Create a project
- File → New Project (Ctrl+N).
- File → Save Project (Ctrl+S), choose a folder and name it DemoQuickStart.
The project opens with an empty scenario.
4. Build the scenario
You will build a flow that:
- Opens a page showing the USD → EUR exchange rate.
- Reads the current rate into a variable.
- Closes the browser.
- Opens Notepad, waits until it is ready, and writes two lines mixing the date, plain text and the rate.
- Saves the note under a filename containing today's date, and exits.

Read the rate
| # | Action | Menu path | Parameters |
|---|---|---|---|
| 1 | [RDP] Open URL | Tools | https://dollarstoeuro.com/usd-to-euro |
| 2 | Teach robot | — | Shift+E in the live view, so the page's elements are detected |
| 3 | AI Read | AI | Source Type Screen; Instructions get rate usd to eur; Extract template one row — name current_rate, type float; Save to variable current_rate |
| 4 | Get | Tools — or Ctrl+Shift+G | Reads when the rate was last updated. Object type On the right; Reference → Text, Label Last Updated:; Query → Text, Label left empty; Variable name rate_time |
| 5 | Key Shortcut | Keyboard | Alt + F4 to close the browser |

Anchoring the search to the fixed label Last Updated: makes the automation immune to
layout shifts — the value next to it changes every run, the label does not. Leaving the
Query label empty matches whatever text sits to the right of the reference. See
Positional Search.
Extract template defines the shape of the result, so current_rate holds a structure
keyed by the field names you listed — not the bare number. Reference the value as
$current_rate['current_rate']. See AI Read.
Open Notepad and wait for it
| # | Action | Menu path | Parameters |
|---|---|---|---|
| 6 | [RDP] Custom Command | Start Process | notepad |
| 7 | Wait For | Wait | Text Notepad — wait until the window is really up |
Wait For guarantees typing only starts once Notepad is really on screen.
Build the text
Add three Create variable actions (Tools, or Ctrl+Shift+V):
| # | Variable | Value |
|---|---|---|
| 8 | notepad_entry_first_line | Exchange rate for $CONSTANTS['DAY_OF_WEEK_NAME'],$CONSTANTS['DAY']/$CONSTANTS['MONTH']/$CONSTANTS['YEAR'] |
| 9 | notepad_entry_second_line | 1 USD = $current_rate['current_rate'] EUR |
| 10 | filename | Rate_$CONSTANTS['FULL_DATE'] |
Write them as ordinary sentences and mark variables with $. Python f-strings are no
longer needed — see Values & Expressions.
Type, save and exit
| # | Action | Menu path | Parameters |
|---|---|---|---|
| 11 | Type Text | Keyboard | $notepad_entry_first_line, Key after typing Enter |
| 12 | Type Text | Keyboard | $notepad_entry_second_line, Key after typing Enter |
| 13 | Key Shortcut | Keyboard | Ctrl + S |
| 14 | Wait For | Wait | Text *.txt — confirms the Save dialog is up |
| 15 | Type Text | Keyboard | $filename, Key after typing Enter |
| 16 | Key Shortcut | Keyboard | Alt + F4 |
Key after typing replaces the separate Enter steps the old version of this walkthrough needed — three fewer actions to maintain.
What you have learned
- [RDP] Custom Command launches any executable with parameters.
- AI Read pulls a value out of a page by describing what you want, with no search object to maintain.
- Get with a positional object reads a value anchored to a stable label next to it.
- Create variable builds text that mixes
CONSTANTSand captured values, using$. - Wait For keeps the flow stable without fixed sleeps.
- Key Shortcut and Type Text — with Key after typing — cover most desktop interaction.
5. Test it
- Click Run all in the Commands panel header.
- Watch the robot execute the actions step by step.
- Open the Runs panel and confirm a green Success status.

If it failed, use the log and screenshots in the run detail to find the step that broke — see Recent Runs.
The finished scenario, exported from the Editor. Paste it into a new project.Show / copy the JSON
In the export, the three Create variable actions use Python f-strings
(f"Rate_{CONSTANTS['FULL_DATE']}") instead of the plain $variable sentences shown in
the step tables. Both forms are equivalent and both work — see
Values & Expressions.
ai_descriptions in the fileThe ai_descriptions block holds the
AI descriptions shown under the actions in the
Commands tree, one high / low pair per action id — low is what Detailed
descriptions shows. They are stored in the project file, which is why they load
instantly and the AI is not called every time you open the scenario. New descriptions are
written only when the AI writes an action or you choose Describe with AI.
A scenario that uses a scenario template
also stores the template text here, in template_text.
6. Move credentials into the Vault
Before scheduling anything, take any password out of the actions:
- Click Vault in the toolbar.
- Add a Password entry, for example
RDP_PASSWORD. - Replace the plain-text value in the action with
{{SECRET:RDP_PASSWORD}}.
This scenario has no password, but every real one will — see Secure Vault.
7. Schedule it
- Click Settings in the Commands panel header to open Scenario Settings.
- Tick Active.
- Set Schedule type to Daily and choose 09:00.
- Pick the robot Profile the scheduled run should use.
- Confirm the Time zone, and save.

8. Turn on Auto Mode
Flip Auto Mode in the main toolbar to On and leave Aiviro Editor running. The Orchestrator now executes the scenario every day at 09:00.

The next planned run appears at the top of the Runs panel with a Scheduled badge. Return there after 09:00 — the entry should have turned into a finished run with today's date.
Next steps
- Explore Loop actions to process CSV files or mailboxes row by row.
- Add a run report with Notification actions.
- Read Best Practices before your scenario grows.
- Install the Editor on a VM and keep it open for 24/7 robots.
Need help? Check the sidebar or reach out to Aiviro Support.