Actions41
- Append
- Blocking Pop Left
- Blocking Pop Right
- Delete
- Eval
- Exists
- Expire At
- Get
- Get Set
- Hash Exists
- Hash Get
- Hash Keys
- Hash Length
- Hash Set
- Hash Values
- Increment
- Info
- Keys
- List Length
- List Range
- Multi Get
- Multi Hash Get
- Multi Mix Get
- Multi Mix Set
- 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 node "Redis Enhanced" provides advanced interaction capabilities with a Redis database. It supports a wide range of Redis operations, including pushing and popping elements from lists, managing keys, 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.
This node is beneficial in scenarios where you need to manage real-time data streams, queues, or caches using Redis within an n8n workflow. For example, you can push new messages or events into a Redis list for asynchronous processing by other services or workflows.
Practical example:
- Push a JSON-formatted message to the tail of a Redis list named "taskQueue" to enqueue a new task for background processing.
Properties
| Name | Meaning |
|---|---|
| List | 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 to the start (head) (false). |
| Value Is JSON | When the key type is a hash (not applicable for push operation), indicates if the value is JSON or key-value pairs. (Shown only for hash key types, not relevant here.) |
Output
The output of the "Push" operation returns the input item unchanged, meaning the node does not produce additional JSON output fields reflecting the push result. The main effect is the side-effect of pushing data into the specified Redis list.
No binary data output is produced by this operation.
Dependencies
- Requires a Redis server accessible via credentials configured in n8n.
- Needs an API authentication token or connection credentials for Redis.
- Uses the Redis client library internally to perform commands.
- No additional external dependencies beyond Redis and its client.
Troubleshooting
Common issues:
- Connection failures due to incorrect Redis credentials or network issues.
- Pushing data to a non-existent or misnamed list will create the list automatically, but ensure the list name is correct.
- If the Redis server is down or unreachable, the node will throw connection errors.
Error messages:
- Errors related to Redis connection or command execution will be thrown as node operation errors.
- Invalid JSON in other operations (not push) may cause parsing errors, but push simply sends the string as-is.
Resolution tips:
- Verify Redis credentials and connectivity.
- Ensure the list name is correctly specified.
- Use the "Tail" option appropriately depending on whether you want to push to the head or tail of the list.