Overview
This node allows users to access global variables stored in a credential and inject them into the workflow data. It is useful when you want to centrally manage configuration values or secrets and reuse them across multiple workflows without hardcoding them. For example, you can store API keys, environment flags, or other constants as global variables and then retrieve them dynamically during workflow execution.
The node supports two modes:
- Putting all variables inside a single JSON key (e.g., under "vars")
- Adding each variable as a separate top-level key in the output JSON
This flexibility helps organize the output data according to your workflow needs.
Properties
| Name | Meaning |
|---|---|
| Put All Variables in One Key | Whether to group all global variables inside one JSON key or output them as separate keys. |
| Variables Key Name | The name of the key under which all variables will be grouped if the above option is enabled. Defaults to "vars". |
Output
The node outputs the global variables as JSON data on each input item:
- If Put All Variables in One Key is enabled, the output JSON contains a single key (default "vars") whose value is an object with all global variables as key-value pairs.
- If disabled, each global variable is added as a separate key directly on the output JSON object.
Example output when grouping variables under "vars":
{
"vars": {
"apiKey": "123abc",
"environment": "production",
"featureFlag": true
}
}
Example output when not grouping:
{
"apiKey": "123abc",
"environment": "production",
"featureFlag": true
}
No binary data is produced by this node.
Dependencies
- Requires a configured credential that stores the global variables securely.
- The node reads variables from this credential, so proper authentication setup is necessary.
- No external API calls are made; all data comes from the credential.
Troubleshooting
- Duplicate variable name detected: This error occurs if the same variable name appears more than once in the credential. To fix it, ensure all variable names are unique.
- Invalid variable format: If a variable's value cannot be parsed correctly (e.g., invalid JSON), an error will be thrown specifying which variable caused the issue. Check the formatting of your stored variables.
- If no input data is provided, the node creates a single output item containing the variables.
- Ensure the credential storing the global variables is properly set up and accessible by the node.