Actions35
- 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
- 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
This node, named "Redis Enhanced," provides a comprehensive interface to interact with a Redis database. It supports a wide range of Redis operations including pushing and popping data from lists, setting and getting keys, managing hashes, sets, sorted sets, and executing Lua scripts. The "Push" operation specifically allows users to add data to a Redis list either at the head or tail.
Common scenarios where this node is beneficial include:
- Managing queues or stacks using Redis lists.
- Storing and retrieving structured data in Redis for caching or messaging.
- Implementing real-time data pipelines by pushing messages into Redis lists.
- Automating Redis data manipulation within workflows without writing custom code.
Practical example:
- Use the "Push" operation to enqueue JSON-formatted messages into a Redis list that acts as a task queue. Downstream workers can then pop tasks from the list for processing.
Properties
| Name | Meaning |
|---|---|
| Value Is JSON | Whether the value being pushed is JSON formatted or simple key-value pairs (only for hash type keys). |
| List | The name of the Redis list to which data will be pushed. |
| Data | The actual data string to push onto the list. |
| Tail | Boolean flag indicating whether to push data to the end (tail) of the list (true) or the beginning (head) (false). |
Output
The output consists of the input items passed through unchanged after the push operation completes successfully. There is no additional JSON output generated by the "Push" operation itself since it performs a write action.
If an error occurs during execution, the node may output an error message in the JSON under the error property if "Continue On Fail" is enabled.
No binary data output is produced by this operation.
Dependencies
- Requires a Redis server accessible via credentials configured in n8n.
- Needs an API key or authentication token configured as Redis credentials in n8n.
- Uses the Redis client library internally to connect and execute commands.
Troubleshooting
- Connection errors: Ensure Redis credentials are correct and the Redis server is reachable.
- Invalid list name or data: The list name must be a valid Redis key string; data should be properly formatted if expected as JSON.
- Permission issues: The Redis user must have permissions to perform list push operations.
- Error messages: If the node throws errors related to command execution, verify the Redis server status and command syntax.
- Data format errors: If "Value Is JSON" is set incorrectly for hash types, data parsing might fail.
Links and References
- Redis Lists Documentation
- Redis Commands Reference
- n8n Redis Integration Guide (general reference for Redis nodes in n8n)