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. Each stored value has a configurable lifetime, after which it expires and is automatically removed if not accessed.
This node is useful for scenarios where temporary data persistence is needed during workflow execution without external databases or services. For example:
- Caching API responses temporarily to reduce calls.
- Storing intermediate calculation results for reuse in later steps.
- Managing feature flags or toggles dynamically within workflows.
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 are: Auto-Detect, Boolean, Number, Object (JSON), String (only for Store Value) |
| Value Lifetime (Minutes) | How long (in minutes) the value remains valid after last use; applies to Store and Get operations |
Output
The node outputs JSON objects describing the result of the operation for each input item:
For Store Value:
operation:"stored"if the value was saved,"dropped"if the value was deleted due to invalid input.key: The key used.value: The stored value (parsed according to the selected type).
For Get Value:
operation: One of"retrieved"(value found and valid),"expired"(value expired and deleted), or"not_found"(no value found).key: The key requested.value: The retrieved value if found and valid.exists: Boolean indicating if the value exists and is valid.
For Delete Value:
operation: Always"deleted".key: The key deleted.existed: Boolean indicating if 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, APIs, or credentials are required.
- Data persists only during the runtime of the workflow execution and is lost when the workflow stops.
Troubleshooting
- Missing Key Error: If no key is provided, the node throws an error "No key provided". Ensure the "Key" property is set for every input item.
- Value Parsing Issues: When storing values with type "Auto-Detect" or "Object (JSON)", invalid JSON strings will cause the value to be dropped (deleted). Validate JSON format before storing.
- Expired Values: Values expire after the configured lifetime since last access. Retrieving an expired value returns
"expired"and deletes it from storage. - Zero or Negative Lifetime: If the lifetime is set to zero or negative, it defaults to 60 minutes.
- Data Volatility: Since storage is in-memory, all data is lost when the workflow stops or restarts. Use persistent storage nodes for long-term data retention.