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
The "Redis Enhanced" node provides a comprehensive interface to interact with a Redis database, supporting a wide range of operations such as getting, setting, deleting keys, working with hashes, lists, sets, sorted sets, and executing Lua scripts. The "Multi Get" operation specifically allows retrieving multiple keys at once from Redis in a single call, which is efficient for batch data retrieval.
This node is beneficial in scenarios where you need to efficiently fetch multiple values stored in Redis without making separate calls for each key. For example, it can be used to retrieve cached user session data for multiple users simultaneously or to get configuration values stored under different keys 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 | (Shown only if the key type is "hash") Boolean indicating whether the value is JSON or key-value pairs. |
Output
The output is an array of items, each containing a json object with key-value pairs corresponding to the requested keys and their values from Redis.
For the "Multi Get" operation:
- The
jsonfield contains an object where each property is a key from the input list, and its value is the corresponding value retrieved from Redis. - If a key does not exist in Redis, its value will be
null.
Example output JSON structure for keys "key1", "key2":
{
"key1": "value1",
"key2": "value2"
}
No binary data output is produced by this operation.
Dependencies
- Requires a Redis server connection configured via credentials that provide necessary authentication (e.g., API key or password).
- The node uses a Redis client library internally to connect and execute commands.
- No additional environment variables are explicitly required beyond the Redis credentials setup.
Troubleshooting
- Common issues:
- Connection failures due to incorrect Redis credentials or network issues.
- Requesting keys that do not exist returns
nullvalues; ensure keys are correct. - Providing an empty or malformed keys string will result in no data returned or errors.
- Error messages:
- Errors during Redis command execution will throw exceptions unless "Continue On Fail" is enabled.
- If the number of key-value pairs is uneven in other operations like "Multi Set," an error is thrown.
- Resolution tips:
- Verify Redis credentials and connectivity.
- Ensure keys are correctly formatted and separated by spaces.
- Use "Continue On Fail" option to handle partial failures gracefully.