Redis Enhanced icon

Redis Enhanced

Get, send and update data in Redis with enhanced operations
Join our community

Actions37

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, hashes, sorted sets, and executing Lua scripts. The "Multi Get" operation specifically allows retrieving the values of multiple keys in a single request, improving efficiency when you need to fetch several keys at once.

This node is beneficial in scenarios where you want to integrate Redis data retrieval into your workflows, for example:

  • Fetching multiple cached values simultaneously to process or analyze them.
  • Retrieving configuration or session data stored under multiple keys.
  • Aggregating data from various Redis keys without multiple separate calls.

Practical example: You have keys user:1, user:2, and user:3 storing user profile data in Redis. Using the Multi Get operation, you can retrieve all three profiles in one step and use the results downstream in your workflow.

Properties

Name Meaning
Keys Space-separated list of key names to retrieve values for (e.g., "key1 key2 key3").
Value Is JSON (Shown only if key type is "hash") Boolean indicating whether the hash value is JSON or key-value pairs.

Output

The output is an array of JSON objects, each representing the result of the operation for an input item. For the "Multi Get" operation, the output JSON object contains key-value pairs where each key corresponds to one of the requested Redis keys, and the value is the associated data retrieved from Redis.

Example output JSON structure for keys key1, key2, key3:

{
  "key1": "value1",
  "key2": "value2",
  "key3": "value3"
}

If a key does not exist in Redis, its value will be null.

The node does not output binary data for this operation.

Dependencies

  • Requires a Redis server accessible via credentials configured in n8n.
  • Needs an API key credential or connection details for Redis authentication.
  • Uses the official Redis client library internally.
  • No additional environment variables are required beyond standard Redis connection credentials.

Troubleshooting

  • Common issues:

    • Connection failures due to incorrect Redis credentials or network issues.
    • Providing invalid or empty keys string for the Multi Get operation.
    • Redis server unavailability or timeouts.

  • Error messages:

    • Errors during connection or command execution will throw descriptive errors.
    • If "continue on fail" is enabled, errors for individual items will be returned in the output JSON under an error property.
    • Key-value pairs must be properly formatted; otherwise, errors will occur.

  • Resolutions:

    • Verify Redis credentials and network connectivity.
    • Ensure keys are provided as space-separated strings without extra whitespace.
    • Enable "continue on fail" to handle partial failures gracefully.

Links and References

Discussion