Variables
Named values reused by the workspace's configurations.
Variables stores named values that the workspace's configurations consume: an environment address, a system identifier, a parameter that differs between staging and production.
Instead of repeating the same value in several places, you name it once and reference the name.
The list
The table shows the Type (public or secret), the Variable, the Value and when it was Updated at. Search filters by name.
The value has reveal and copy actions. Copying is useful when it is long or needs to be checked against another system.
Create a variable
Click + Variable and enter the Variable name and the Value. The name follows the environment-variable convention, in uppercase with underscores, such as DATABASE_URL or API_BASE_URL.
Variable visibility is Public, when the value can be shown again, or Secret, when it stays hidden after saving.
In the narrow bar on the left, click Workspace.
Masked visibility hides the value on screen; it doesn't turn it into a managed secret. Access credentials for systems belong under Organization › Credentials, which is where the secret is actually protected.
Who can change them
Owner, Curator and Editor create and change variables. Auditor only reads.
Deleting a variable is the Owner's privilege. Curator and Editor can create and edit, but not remove, which keeps a value in use from disappearing by mistake.
Effect of changing a value
Changing a variable changes the value for everyone who references it, on the next run. There is no versioning or history.
Before changing a value in use, check where it is referenced: there is no screen that lists a variable's consumers.
Next steps
- Keep access secrets in Credentials.
- See where named values come into automation in Workflows.