Redis Enhanced

Overview

The "Redis Enhanced" node provides a comprehensive interface to interact with a Redis database, supporting a wide range of operations such as getting, setting, deleting keys, manipulating lists, sets, sorted sets, hashes, and executing Lua scripts. It is designed for scenarios where users need to integrate Redis data storage and retrieval into their workflows with enhanced flexibility and control.

Common use cases include:

• Caching data or session information.
• Managing queues or lists for asynchronous processing.
• Publishing messages to Redis channels for real-time notifications.
• Performing atomic increments or conditional key updates.
• Executing custom Lua scripts for complex Redis operations.

For example, you can use this node to push new tasks onto a Redis list queue, pop tasks for processing, or increment counters atomically.

Properties

Note: This property appears only when the key type is set to "hash" during certain operations like setting values.

Output

The node outputs an array of JSON objects, each representing the result of the Redis operation performed on the corresponding input item. The structure of the output JSON depends on the operation:

• For get operations, the output contains the retrieved value under the specified property name, supporting dot notation for nested properties.
• For set operations, the output includes the original input data merged with the Redis operation result.
• For list, set, sorted set, and hash operations, the output JSON contains relevant metadata such as lengths, members added/removed, or retrieved elements.
• For publish, delete, and other commands, the output typically returns the original input item or confirmation details.
• For eval (Lua script execution), the output contains the script result.
• In case of errors, if "Continue On Fail" is enabled, the output includes an error message per failed item.

The node does not output binary data.

Dependencies

• Requires a Redis server connection configured via credentials that provide necessary authentication.
• Uses a Redis client library internally to communicate with the Redis instance.
• No additional external services are required beyond the Redis server.

Troubleshooting

• Connection issues: Ensure the Redis credentials are correct and the Redis server is reachable.
• Invalid key/value formats: When using JSON values, ensure they are properly formatted; otherwise, parsing errors may occur.
• Key-value pairs mismatch: For multi-set operations, the number of arguments must be even (pairs of keys and values).
• Unsupported operations: Using an unsupported operation value will cause errors.
• Timeouts: Blocking pop operations (blpop, brpop) may wait indefinitely if timeout is set to 0.
• Dot notation confusion: If dot notation is disabled, nested property paths will be treated as literal keys, which might affect data structure in output.

Error messages generally indicate the nature of the failure, such as connection errors, invalid parameters, or Redis command failures. Enabling "Continue On Fail" allows workflow continuation despite individual item errors.

Links and References

• Redis Official Documentation
• Redis Commands Reference
• Lua Scripting in Redis