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.
- Paste your Client ID and API Key, then click Test Credentials.
- Wait for the success message, then save and restart the Editor.
/img/editor/quick-start/license.pngCapture: Settings → Edit Configuration → Aiviro with a successful Test Credentials result. Mask: blur the Client ID and API Key. Why it must be retaken: licence entry moved into the categorized settings dialog — there is no separate licence prompt any more.
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.
/img/editor/quick-start/action-tree.pngCapture: the finished Commands tree for this scenario, with the section collapsed/expanded so all ~17 actions are visible. Why it must be retaken: the tree styling changed and the state column now shows the Run Action icons.
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 | Get | Tools — or Ctrl+Shift+G | Right-click the rate value. Object type On the right; Reference → Label 1 USD; Query → Label \b\d{1}[,.]\d{2}\b with Find method REGEX; Variable name current_rate |
| 4 | Key Shortcut | Keyboard | Alt + F4 to close the browser |
/img/editor/quick-start/example_get_rate.pngCapture: the Get form for step 3 — the On the right search object with Reference and Query filled in and Find method REGEX selected. Why it must be retaken: Get moved to the Tools group and the search-object editor was redesigned.
Anchoring the search to the fixed label 1 USD makes the automation immune to layout
shifts. The regular expression then picks only the numeric part, ignoring the trailing
currency name. See Positional Search.
Open Notepad and wait for it
| # | Action | Menu path | Parameters |
|---|---|---|---|
| 5 | [RDP] Custom Command | Start Process | notepad |
| 6 | Wait For | Wait | Text UTF-8 — always present in Notepad's status bar |
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 | Expression |
|---|---|---|
| 7 | first_line | f"Exchange rate for {CONSTANTS['DAY_OF_WEEK_NAME']}, {CONSTANTS['DAY']}/{CONSTANTS['MONTH']}/{CONSTANTS['YEAR']}" |
| 8 | second_line | f"1 USD = {current_rate} EUR" |
| 9 | filename | f"Rate_{CONSTANTS['FULL_DATE'].strftime(r'%d-%m-%Y')}.txt" |
Type, save and exit
| # | Action | Menu path | Parameters |
|---|---|---|---|
| 10 | Type Text | Keyboard | first_line, Key after typing Enter |
| 11 | Type Text | Keyboard | second_line |
| 12 | Key Shortcut | Keyboard | Ctrl + S |
| 13 | Wait For | Wait | Text *.txt — confirms the Save dialog is up |
| 14 | Type Text | Keyboard | filename, Key after typing Enter |
| 15 | Key Shortcut | Keyboard | Alt + F4 |
| 16 | Wait Until Disappear | Wait | the Notepad window title |
Key after typing replaces the separate Enter steps the old version of this walkthrough needed — two fewer actions to maintain.
What you have learned
- [RDP] Custom Command launches any executable with parameters.
- Get with a positional object and a regex pulls one value off a page without code.
- Create variable builds strings that mix
CONSTANTSand captured values. - Wait For / Wait Until Disappear keep the flow stable without fixed sleeps.
- Key Shortcut, Type Text and Click 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.
/img/editor/quick-start/run_success.pngCapture: the Runs panel with a successful run selected and its detail visible. Why it must be retaken: the panel is now called Runs and the log viewer was rebuilt in 0.23.
If it failed, use the log and screenshots in the run detail to find the step that broke — see Recent Runs.
The 0.14.2 version of this page ended with a copy-paste-ready scenario JSON. It was
removed because it serializes class paths from the old src.actions.* /
src.parameters.* layout and uses actions that are now deprecated
(Constant, the old e-mail actions), so pasting it into 0.23.1 would not reproduce the
walkthrough.
To restore it: build this scenario in the current Editor, then export it and paste the
JSON back into a collapsible <details> block here.
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.
/img/editor/quick-start/schedule.pngCapture: Scenario Settings with Active ticked, Schedule type: Daily, a time set, and the human-readable schedule description visible below. Why it must be retaken: the dialog gained the Localization section and a plain-language schedule summary.
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.
/img/editor/quick-start/auto_mode.pngCapture: the main toolbar with Auto Mode switched on, and the Scheduled panel showing the next planned run.
Return to the Runs panel after 09:00 — a new entry should be there 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.