Environment Variables
Store API keys and other secrets in named stores that workflows can reference securely
Environment variable stores let you define key-value pairs, such as API keys, tokens, or configuration values, that workflows can reference without hardcoding sensitive values in the workflow definition itself.
Stores
Variables are organized into stores. A store is a named collection of related variables, for example one store per external service or deployment environment.
Creating a Store
- Open Environment Variables in the Workflows sidebar
- Click New Store
- Give the store a name and an optional description
- The store opens in the editor, ready for variables
Deleting a Store
Open the store's context menu on the overview page and select Delete. All variables in the store are removed permanently.
Managing Variables
Inside a store you can add, edit, and delete individual variables.
Adding a Variable
Fill in a key and value, choose whether the value is a secret, and save.
- Regular variables are stored and displayed as plain text
- Secret variables are encrypted server-side. After saving, the value is masked and cannot be read back in plain text, only replaced
Revealing a Secret
Click the eye icon next to a secret entry to temporarily reveal its masked value. This requires an additional server request to decrypt the value.
Editing and Deleting
Click on a variable's key or value cell to edit it inline. Use the delete icon to remove a variable.
Importing from a .env File
Click Import .env to paste the contents of an existing .env file. Each KEY=VALUE line is parsed and added to the store. Lines starting with # are ignored. Variables marked as secrets in the import dialog are encrypted automatically.
Using Variables in Workflows
Reference a store's variables inside any workflow node that accepts environment input. Select the store and then the key to inject its value at runtime.
Secret values are never exposed in workflow logs or run outputs. They are substituted server-side at execution time.