Actions3
Overview
The Symbiosika Key-Value Store node provides a simple in-memory key-value storage system within an n8n workflow. It allows users to store, retrieve, and delete values associated with unique keys during workflow execution. This is useful for caching data temporarily, sharing state between different parts of a workflow, or persisting small pieces of information without external databases.
Common scenarios include:
- Caching API responses to reduce redundant calls.
- Storing temporary flags or counters used across multiple workflow executions.
- Passing data between different nodes or executions where persistent storage is not required.
For example, you could store a token retrieved from an authentication API and reuse it later in the workflow until it expires.
Properties
| Name | Meaning |
|---|---|
| Operation | The action to perform: Store Value, Get Value, or Delete Value. |
| Key | A unique identifier string for the key-value pair. |
| Value | The value to store (only for Store Value operation). |
| Value Type | The type of the value to store. Options: Auto-Detect, Boolean, Number, Object (JSON), String. Determines how the input value is interpreted and stored. |
| Value Lifetime (Minutes) | How long (in minutes) the stored value remains valid after last use. Applies to Store Value and Get Value operations. Defaults to 60 minutes. |
Output
The node outputs an array of JSON objects, each representing the result of the operation for an input item. The structure varies by operation:
Store Value
operation:"stored"if the value was successfully stored,"dropped"if the value was invalid and removed.key: The key used.value: The stored value (parsed according to the selected type).
Get Value
operation: One of"retrieved","expired", or"not_found".key: The key requested.value: The stored value if found and valid.exists: Boolean indicating whether the key exists and is valid.
Delete Value
operation:"deleted".key: The key deleted.existed: Boolean indicating whether the key existed before deletion.
No binary data output is produced by this node.
Dependencies
- This node uses an internal in-memory JavaScript
Mapobject to store key-value pairs. - No external services or APIs are required.
- No special credentials or environment variables are needed.
- Data persists only during the lifetime of the workflow execution environment; restarting n8n clears the store.
Troubleshooting
- Missing Key Error: If no key is provided, the node throws an error "No key provided". Ensure the
Keyproperty is set and not empty. - Invalid Value Parsing: When storing a value, if the value cannot be parsed as the selected type (e.g., invalid JSON for Object type), the value will be dropped (deleted) silently. Double-check the format of your input value matches the selected
Value Type. - Value Expiry: Values expire after the specified lifetime since last access. If a value is expired, a
getValueoperation returns"expired"and deletes the entry. Increase theValue Lifetimeif you want longer persistence. - Non-Persistent Storage: Remember that this store is in-memory only. All stored data is lost if n8n restarts or the node is reloaded.
Links and References
- n8n Documentation – General resource for building workflows.
- JavaScript Map Object – Explanation of the underlying data structure used for storage.
- JSON.parse() – Used for parsing JSON strings into objects.