Overview
This node interacts with a Redis database, specifically performing a 'Pop' operation on a Redis list. It allows popping data from either the head or the tail of a specified Redis list. The node supports JSON parsing of the popped value and can write the result to a specified property in the output data, supporting dot-notation for nested properties. This is useful for workflows that need to consume and process data stored in Redis lists, such as message queues or task lists.
Use Case Examples
- Pop a JSON object from the head of a Redis list named 'taskQueue' and store it in the output under 'data.task'.
- Pop a string value from the tail of a Redis list named 'eventLog' and store it in the output under 'event.lastEntry'.
Properties
| Name | Meaning |
|---|---|
| Connection Mode | How to manage Redis connections, either reusing pooled connections for better performance or creating a new connection each time for safety. |
| Value Is JSON | Indicates whether the value in the Redis list is JSON or key-value pairs (only shown for hash key types). Defaults to true. |
| List | The name of the Redis list from which to pop data. |
| Tail | Whether to pop data from the end (tail) of the list instead of the beginning (head). Defaults to false (pop from head). |
| Name | Optional name of the property to write the received data to in the output. Supports dot-notation for nested properties, e.g., 'data.person[0].name'. |
| Options | Additional options for the pop operation, including whether to use dot-notation when setting the output property. |
Output
JSON
propertyName- The property in the output JSON where the popped data from the Redis list is stored. Supports dot-notation for nested structure.
Dependencies
- Redis server connection via credentials
Troubleshooting
- Connection issues: Ensure Redis credentials are correct and the Redis server is reachable.
- JSON parsing errors: If the popped value is not valid JSON but 'Value Is JSON' is true, parsing will fail. Consider disabling JSON parsing or validating data format.
- Dot-notation issues: If the output property name uses dot-notation but the structure is not as expected, disable dot-notation in options to treat the property name as a flat key.