Overview
Environment Variables in the UnifyApps platform are dynamic key-value pairs that allow you to configure environment-specific values used across apps, automations, and APIs. Similar to how environment variables function in traditional software development, these variables isolate critical values—such as URLs, tokens, or feature flags—specific to a given environment (e.g., dev, UAT, prod), ensuring seamless portability and environment isolation.
These variables are resolved at runtime based on the environment in which the asset is deployed, enabling streamlined configuration without manual code changes.


Key Capabilities & Use Cases
Environment-Specific Configuration
Each environment variable belongs to a workspace in the environment where it's created. If the same name is defined in another environment, it has its own value there, set in that environment.
Enables smooth deployments across UAT, staging, and production
Prevents hardcoded values in workflows
Supports environment-scoped values like API base URLs, keys, and flags
Storing Secrets Securely
Marking a variable as sensitive masks its value in the platform interface and ensures its secure storage. This is especially useful for:
API Tokens and Authentication Keys
Webhook secrets
Encrypted database URIs
Used in Automations and APIs
Environment variables can be referenced inside:
REST API steps (Base URLs, headers, params)
Callable automations
Node configurations
They help in dynamically adapting the behavior of these elements per environment.
Custom and System tabs
In the default workspace, if you have the required permission, the list splits into two tabs. Custom holds the variables your team created. System holds platform-defined variables that ship with the platform and drive platform behavior. System variables are global rather than workspace-scoped, so the Workspace column is hidden on that tab. Without the permission, or in any other workspace, you see only that workspace's own variables with no tabs.
Using variables in apps and automations
In apps, reference a variable in an expression as {{ envVariables['NAME'] }}, for example inside a data source input. In automations, the data panel shows an Environment Variables group next to Run Variables and User Variables. Pick a variable as a pill to map it into any node input. A name that doesn't exist resolves to an empty value without an error, so check for typos if you get a blank. Apps never receive variables marked sensitive, and public apps get no environment variables, so read secrets in an automation.
Managing variables from an automation
Automations can also create, update, and delete environment variables through the Environment Variables actions.
Create takes a name, a value, and a sensitive flag, and needs create permission. It fails if the name already exists.
Update changes a variable's value and sensitivity by name, and needs edit permission. Send the full value each time.
Delete removes a variable by name, and needs delete permission.
How to Create an Environment Variable?
To create a new environment variable, follow these steps:
In your workspace's side navigation, go to Enterprise Resources › Environment Variables, then select New Environment Variable.
Enter a unique variable name. Names can contain letters, numbers, hyphens, and underscores; uppercase names with underscores are recommended for readability.
Enter the
Variable Valueappropriate for the environmentOptionally, choose a
Workspace. This field appears only when you're in the Global workspace; otherwise the variable belongs to the current workspace.Check
Mark as sensitiveif the value is confidential (e.g., tokens, secrets)Click
Create
Example:
| Variable Name | Variable Value |
| BASE_URL_UAT | https://lead.matrix-uat.test.com |
| AUTH_TOKEN | Sensitive value |
Note
When an automation or application using environment variables is exported via a change set to another environment the variable key is retained but the value is not transferred.
Best Practice
When a change set includes referenced environment variables, their names travel with the assets, but values are not applied automatically on import. During the inbound change-set Environment Variables step, verify required variables and enter values for new variables or keep and update the target environment's values.