Symbiosika Key-Value StoreInstall

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 can be useful for caching data temporarily, sharing state between different parts of a workflow, or managing small pieces of transient information without external databases.

Typical use cases include:

• Caching API responses to reduce redundant calls.
• Storing temporary flags or counters used across multiple workflow executions.
• Managing session-like data or short-lived tokens within a workflow.

For example, you could store a token with a specific key and retrieve it later in the workflow, ensuring it is only valid for a certain time period after last access.

Properties

Output

The node outputs JSON objects representing the result of the operation for each input item:

• For Store Value:

  • operation: "stored" if the value was successfully stored, or "dropped" if the value was empty/invalid and thus removed.
  • 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 whether the value exists and is valid.

• For Delete Value:

  • operation: "deleted".
  • key: The key deleted.
  • existed: Boolean indicating whether the key existed before deletion.

If binary data were supported, it would be indicated here, but this node only handles JSON-compatible values.

Dependencies

• No external services or APIs are required.
• The node uses an internal in-memory JavaScript Map to store key-value pairs.
• Values persist only during the lifetime of the workflow execution environment; they do not survive process restarts.
• No special credentials or environment variables are needed.

Troubleshooting

• No key provided error: The node requires a non-empty key string. Ensure the "Key" property is set for every input item.
• Value parsing issues: When storing values with a specified type (e.g., JSON object), invalid JSON strings will cause the value to be dropped silently. Use correct formatting or the "Auto-Detect" option.
• Expired values: Values expire after the configured lifetime since last use. If a value is unexpectedly missing, check the "Value Lifetime" setting.
• Data persistence: Since storage is in-memory, all data is lost when the workflow stops or the node is reloaded. For persistent storage, consider external databases or services.

Links and References

• n8n Documentation on Creating Nodes
• JavaScript Map Object
• JSON.parse() Method