Actions37
- Append
- Blocking Pop Left
- Blocking Pop Right
- Delete
- Eval
- Exists
- Expire
- 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 Members
- 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, managing keys, hashes, sets, sorted sets, executing Lua scripts, and more.
The Push operation specifically allows users to add data to a Redis list either at the head (start) or tail (end). This is useful in scenarios such as implementing queues, task scheduling, or buffering data streams where new elements need to be appended to a list structure in Redis.
Practical example:
- Adding a new job or message to a queue stored as a Redis list by pushing it to the tail.
- Prepending urgent notifications to the start of a list for priority processing.
Properties
| Name | Meaning |
|---|---|
| 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 (true) or the start (false) of the list. |
| Value Is JSON | (Shown only if key type is hash) Indicates whether the value is JSON or key-value pairs. |
Output
The output is an array of items corresponding to each input item processed. For the Push operation, the output item is essentially the same as the input item, augmented with any Redis operation results if applicable (in this case, no additional result is returned from the push command).
The json field contains the original input data passed through without modification, confirming the push operation was executed.
No binary data output is produced by this operation.
Dependencies
- Requires a Redis server accessible via credentials configured in n8n.
- Needs an API key credential or connection details for Redis authentication.
- Uses the Redis client library internally to perform commands.
- No additional external services are required beyond Redis itself.
Troubleshooting
- Connection errors: Ensure Redis credentials are correct and the Redis server is reachable from the n8n instance.
- Invalid list name or data: The list name must be a valid Redis key string; data should be a string. Non-string data should be serialized before pushing.
- Operation failures: If pushing fails, check Redis server logs and network connectivity.
- Tail property confusion: Setting
Tailincorrectly may cause data to be pushed to the wrong end of the list, affecting queue order.
Common error messages:
"ECONNREFUSED"or similar: Redis server not reachable. Verify host, port, and firewall settings."WRONGTYPE Operation against a key holding the wrong kind of value": The specified key exists but is not a list. Use a different key or delete the existing key.