Overview
This node interacts with a Redis database to perform various operations such as retrieving generic information about the Redis instance, managing keys, and manipulating data stored in Redis. It supports connection pooling for performance optimization or direct connections for safer but slower operations. Common use cases include monitoring Redis server status, managing cache keys, incrementing counters, publishing messages to channels, and handling lists within Redis.
Use Case Examples
- Use the node to get Redis server info for monitoring purposes.
- Delete a specific key from Redis to manage cache or session data.
- Increment a numeric key atomically to track event counts.
- Publish messages to a Redis channel for real-time notifications.
Properties
| Name | Meaning |
|---|---|
| Connection Mode | How to manage Redis connections, either by reusing pooled connections for better performance or creating a new connection each time for safety. |
| Value Is JSON | Indicates whether the value stored in a Redis hash key is JSON or key-value pairs (only applicable when key type is 'hash'). |
Output
JSON
info- Generic information about the Redis instance as an object.propertyName- Property name to write received data to, supports dot-notation for nested properties.key- The Redis key involved in the operation, e.g., incremented key or deleted key.keys- List of keys matching a pattern when using the keys operation.error- Error message if an operation fails and continueOnFail is enabled.
Dependencies
- Requires a Redis server connection with appropriate credentials (API authentication token).
Troubleshooting
- Common issues include failure to establish a Redis connection, which may be due to incorrect credentials or network issues. The node throws errors if it cannot connect or if Redis commands fail.
- If the node is set to use pooled connections, stale or disconnected clients may cause errors; restarting the workflow or clearing connections may help.
- When using the 'get' operation with automatic key type detection, performance may be slower due to additional type requests.
- Errors during JSON parsing of values may occur if the stored data is not valid JSON when 'Value Is JSON' is enabled.
Links
- Redis INFO Command - Official Redis documentation for retrieving server information.
- Redis KEYS Command - Official Redis documentation for retrieving keys matching a pattern.