Actions36
- Append
- Blocking Pop Left
- Blocking Pop Right
- Delete
- Eval
- Exists
- Expire At
- Get
- Get Set
- Hash Exists
- Hash Keys
- Hash Length
- Hash Values
- Increment
- Info
- Keys
- List Length
- List Range
- Multi Get
- Multi Set
- Persist
- Pop
- Publish
- Push
- Scan
- Set
- Set Add
- Set Cardinality
- Set Is Member
- Set Remove
- Sorted Set Add
- Sorted Set Cardinality
- Sorted Set Range
- Sorted Set Remove
- String Length
- TTL
Overview
The "Redis Enhanced" node provides a comprehensive interface to interact with Redis databases, supporting a wide range of operations including data retrieval, modification, and management. Specifically, the "Blocking Pop Left" operation allows the node to perform a blocking pop from the left side of a Redis list. This means it waits for an element to become available on the specified list and then removes and returns that element.
This operation is beneficial in scenarios where workflows need to process items from a queue or list as soon as they are available, such as task queues, message processing systems, or event-driven automation pipelines. For example, you can use this node to wait for new jobs pushed into a Redis list and process them immediately when they arrive.
Properties
| Name | Meaning |
|---|---|
| List | The name of the Redis list from which to perform the blocking pop (left side). |
| Timeout | The maximum time in seconds to wait for an element if the list is empty. 0 means wait indefinitely. |
| Name | The property name under which the popped value will be stored in the output JSON. Supports dot-notation. |
| Value Is JSON | Whether the popped value should be parsed as JSON or treated as a plain string. |
Output
The output JSON contains the following structure:
- A property named as specified by the "Name" input property.
- If an element was successfully popped, this property holds the element's value. The node attempts to parse the value as JSON; if parsing fails, the raw string is returned.
- If no element was popped (e.g., timeout expired without receiving data), the property is set to
null.
- Additionally, a
listproperty is included indicating the name of the Redis list from which the element was popped.
Example output JSON:
{
"propertyName": { /* parsed JSON object or string value */ },
"list": "myList"
}
Dependencies
- Requires a Redis server accessible via credentials configured in n8n.
- Needs an API key or authentication token for connecting to the Redis instance.
- Uses the Redis client library internally to communicate with Redis.
- No additional external services are required beyond Redis itself.
Troubleshooting
- Timeouts: If the node waits indefinitely or longer than expected, verify the "Timeout" setting and ensure the Redis list is being populated correctly.
- Parsing Errors: If the popped value is not valid JSON but "Value Is JSON" is enabled, the node will return the raw string instead. Ensure the data format matches the setting.
- Connection Issues: Errors related to connection failures usually indicate incorrect Redis credentials or network issues. Verify credentials and connectivity.
- Empty List: If the list is empty and the timeout expires, the output property will be
null. This is expected behavior. - Error Messages: Common errors include invalid key names or Redis command failures. Review error messages for details and check Redis server logs if needed.