Get All
AI-generatedOverview
This node acts as a global configuration store within n8n workflows, allowing users to set, get, delete, and manage configuration variables across workflows. It supports operations such as storing a single variable, retrieving a single variable, setting multiple variables at once, getting all stored variables, deleting a variable, and clearing all variables. This is useful for managing environment-specific settings, API keys, or any global data that needs to be shared and reused across multiple workflows.
Use Case Examples
- Store an API key securely and retrieve it in different workflows without exposing it in logs.
- Manage environment-specific configuration variables like project IDs or URLs that can be updated centrally.
- Clear all stored configuration variables when resetting the environment.
Properties
| Name | Meaning |
|---|---|
| Options | Additional settings for the operation |
Output
JSON
_configStoreoperation- The operation performed (e.g., getAll)variables- An object containing all stored variables with their values or masked values if securecount- The number of variables stored
- The value of each variable if not secure
Dependencies
- Uses an internal in-memory Map to store variables globally within the n8n instance
Troubleshooting
- If a variable is not found during a get operation, the output will indicate 'Variable not found'. Ensure the variable name is correct and has been set previously.
- Secure variables are masked in logs and output to protect sensitive data; if you see '***SECURE***', it means the value is hidden for security reasons.
- Since the store is in-memory, all variables will be lost if the n8n instance restarts. Consider this when relying on persistent configuration.
Links
- n8n Config Store Node Documentation - Official documentation for the Config Store node in n8n.