References & Resources

Built-in constants

Every scenario has a CONSTANTS dictionary available in expressions — in Create variable, Condition, Assert and Python Code. All values are evaluated once, when the run starts.

Key	Value
FULL_DATE	The run date as a date object — use .strftime(...) to format it.
YEAR	Four-digit year, e.g. 2026.
MONTH	Two-digit month, e.g. 08.
DAY	Two-digit day of the month.
DAY_OF_WEEK	Day of the week as a number, Sunday = 0.
DAY_OF_WEEK_NAME	Day name, e.g. Wednesday.
START_TIME	Full timestamp of when the run started.
IS_WORK_DAY	True Monday–Friday, False at the weekend.
QUARTER	Calendar quarter, 1–4.
WEEK_NUMBER	ISO week number.

Example:

f"Report_{CONSTANTS['YEAR']}_Q{CONSTANTS['QUARTER']}.xlsx"

AIVIRO_NOTIFICATIONS holds the messages collected by Add Message so far, which lets a Python Code block or a Condition react to what the run has already reported.

tip

IS_WORK_DAY is the neat way to make a daily schedule skip weekends without touching the cron expression: wrap the body in a Condition on CONSTANTS['IS_WORK_DAY'].

---

Referencing variables

In any value field, $ followed by a variable name inserts that variable's value:

$Helios_path
$project_name

This is what the Commands tree and the Diagram view show in their one-line action summaries — Command: $Helios_path, Subject: $project_name.

The $ applies in expressions too — $amount * 1.21, $record['state'] == "OK". The two exceptions are inside the braces of a hand-written f-string (f"Hello {name}", not {$name}) and inside the Python Code action, which is ordinary Python.

For the full rules — text with variables, arithmetic, dates, operators, list handling — see Values, Variables & Expressions.

Secret placeholders

Reference a Vault entry from any text parameter:

{{SECRET:MY_KEY}}

---

Python SDK documentation (core product)

The Aiviro Python SDK powers every action block in Aiviro Editor. It is the place to start when you want to extend a scenario with a Python Code node, or run whole robots headless from your own scripts.

API reference and examples: docs.core.aiviro.com

Covers search objects, command syntax, the robot lifecycle and much more.

Everything you do visually in the Editor maps 1:1 to SDK calls, and File → Export as Python shows you that mapping for your own scenario. The SDK documentation also describes advanced parameters and integration options that the low-code UI does not expose.

TODO — check the SDK URL

The 0.14.2 page linked to docs.aiviro.com, while the Editor's own navbar links the core documentation as docs.core.aiviro.com. Confirm which is current and make both this page and docusaurus.config.ts agree.

---

Video tutorials

Hands-on demos of the Editor are collected in the YouTube playlist:

Aiviro Editor tutorials

TODO — check the playlist

Confirm the playlist still exists and that its videos show the 0.23 interface. Demos recorded against 0.14.2 show the old toolbar and the old actions menu, which will confuse new users.

---

In-application help

Resource	Where
Manual	Help → Manual
Version and build information	Help → About
Configuration folder	Settings → Open config folder — logs, profiles and settings on disk

---

Interface languages

The Editor interface is available in English, Czech and German (Settings → General → Language). Report language for Send As Email additionally offers Slovak.

This documentation is maintained in English and Czech.