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
This node, "Redis Enhanced," provides a comprehensive interface to interact with a Redis database. It supports a wide range of Redis operations such as getting and setting keys, manipulating lists, sets, sorted sets, hashes, executing Lua scripts, and more. The "Multi Get" operation specifically allows retrieving multiple keys at once from Redis in a single call.
This node is beneficial in scenarios where you need to efficiently fetch multiple values from Redis without making separate calls for each key, improving performance and reducing latency. For example, it can be used in caching layers to retrieve several cached items simultaneously or in session management systems to get multiple user session data in one request.
Properties
| Name | Meaning |
|---|---|
| Keys | Space-separated list of key names to retrieve from Redis (e.g., "key1 key2 key3"). |
| Value Is JSON | Boolean flag indicating whether the value stored in Redis hash keys is JSON (true) or simple key-value pairs (false). Only relevant when the key type is a hash. |
Output
The output is an array of JSON objects, each representing the result of the operation for an input item.
For the "Multi Get" operation:
- The
jsonfield contains an object where each property corresponds to a requested key. - Each key's value is the retrieved value from Redis or
nullif the key does not exist or retrieval failed. - The structure looks like this:
{
"key1": <value_of_key1_or_null>,
"key2": <value_of_key2_or_null>,
"key3": <value_of_key3_or_null>
}
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 (configured in n8n credentials).
- Uses the Redis client library internally to connect and perform commands.
- No additional external services are required beyond the Redis instance.
Troubleshooting
- Common issues:
- Incorrect Redis credentials or connection details will cause connection failures.
- Providing keys that do not exist in Redis will return
nullvalues for those keys. - If the keys string is empty or improperly formatted, the node may throw an error or return no results.
- Error messages:
- Connection errors typically indicate invalid credentials or unreachable Redis server.
- Errors about key-value pairs being uneven occur in other operations but not in "Multi Get."
- If the node throws an error during execution, enabling "Continue On Fail" allows processing remaining items.
- Resolution tips:
- Verify Redis credentials and network connectivity.
- Ensure keys are space-separated and valid.
- Use "Continue On Fail" option to handle partial failures gracefully.