Variables
Variables store named values that automations can read and change.
AlphaWhen to use a variable
Use a variable when a value must remain available beyond one step or influence later automation runs. Examples include counters, feature switches and the last known state of a service.
How it works
Each variable has a name, value and type information used by editors and runtime conversion. Steps can read a variable by path or change it with a variable action.
Project variables and runtime variables
Project variables use vars.* paths and remain available across automation runs. Runtime variables use runtime.* paths, belong to one run and disappear when that run finishes.
Organization
The Variables view supports search and user-defined groups. Groups organize the editor; they do not create a separate runtime scope.
Usage tracking
Select a variable to view known usages in automations and macros. Use the usage list before renaming or deleting a variable.
Rename
Rename through the Variables view so known references can be updated. Review the usage list afterward because text or plugin-owned data may contain references that cannot be identified automatically.
Limitations
Variables are runtime state, not secure secret storage. Do not use them for access tokens or passwords.