Redis EnhancedInstall

Overview

The node "Redis Enhanced" provides a comprehensive interface to interact with a Redis database. It supports a wide range of Redis operations such as retrieving information about the Redis instance, managing keys and values, manipulating data structures like lists, sets, hashes, and sorted sets, executing Lua scripts, and publishing messages to channels.

This node is beneficial in scenarios where you need to integrate Redis caching, messaging, or data storage capabilities into your workflows. For example, you can use it to:

• Retrieve server info for monitoring Redis health.
• Get or set cached data with expiration.
• Manage lists or sets for queueing or membership tracking.
• Execute custom Lua scripts for advanced Redis logic.
• Publish messages to Redis channels for real-time notifications.

Properties

Note: The above property is specific to the "Info" operation context with keyType "hash". The full node supports many other properties depending on the selected operation, but here only the provided property is described.

Output

For the "Info" operation, the output is a JSON object containing generic information about the connected Redis instance. This includes various server statistics and configuration details parsed from the Redis INFO command.

Example output structure (simplified):

{
  "redis_version": "6.2.5",
  "connected_clients": 10,
  "used_memory_human": "1.23M",
  "uptime_in_seconds": 3600,
  ...
}

The node returns this information as a single item in the output array under the json field.

No binary data output is produced by the "Info" 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 Redis client library internally to connect and execute commands.

Troubleshooting

• Connection errors: If the node cannot connect to Redis, verify that the Redis server is running, reachable, and credentials are correct.
• Timeouts or slow responses: Large Redis instances or network latency may cause delays; consider adjusting timeouts or optimizing queries.
• Invalid command errors: Ensure the Redis server version supports the requested operation.
• Error handling: If an error occurs during execution, the node either throws an error or continues based on the "Continue On Fail" setting.
• Parsing errors: For operations involving JSON parsing (not relevant for "Info"), invalid JSON strings may cause failures.

Links and References

• Redis Official Documentation
• Redis INFO Command
• n8n Redis Integration Guide (general reference)