Secret Stores
Keep API keys, tokens and configuration in named stores that workflows read at runtime
Secret stores hold key-value pairs such as API keys, tokens or base URLs. Workflows read them at runtime, so the values never sit in a node's configuration. You find them under Secret Stores in the Data & Integrations group of the Workflows sidebar.
Creating a Store
A store groups related values, for example one store per external service or per environment.
- Open Secret Stores and click New Store.
- A store named "New Secret Store" is created and opens.
- On the Settings tab, set the name and an optional description and click Save.
Managing Variables
The Variables tab lists the store's entries. To add one, click Add variable, enter Key and Value, decide on Secret (encrypted) and click Add. The secret option is switched on by default.
- Plain variables are stored and shown as text.
- Secrets are encrypted on the server. The list shows a placeholder marked as encrypted instead of the value. Reveal decrypts and shows it for you; Hide masks it again.
To change a value, add the key again with the new value; it replaces the old one. The trash icon deletes a variable.
Importing from a .env File
Click Import from .env and paste the contents of a .env file. Every KEY=VALUE line becomes a variable; empty lines and lines starting with # are skipped. The dialog shows how many variables it found. With Mark all as secret (encrypted) every imported value is encrypted.
Using Values in Workflows
In the node picker, open Integrations → Secret Stores:
- Get All Secrets returns all entries of a store as the object
variables - Get Single Secret returns one entry by Variable Key as
value
Later nodes reference these outputs, for example {{getAllSecrets.outputs.variables.API_KEY}}. Secrets are passed on as a reference and only resolved when the next node runs, so node outputs and the execution history show the reference, not the value. Details in Action Nodes.
A store belongs to the person who created it. If you share a workflow, its runs keep access to the stores it uses.
Archiving a Store
To remove a store, archive it from the overview. Archived stores are no longer available to workflows, and nodes that read from them fail.