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
The "Redis Enhanced" node provides a comprehensive interface to interact with a Redis database, supporting a wide range of operations such as getting and setting keys, managing lists, sets, sorted sets, hashes, and executing Lua scripts. The "List Length" operation specifically retrieves the length of a specified list stored in Redis.
This node is beneficial in scenarios where you need to integrate Redis data storage or caching into your workflows, for example:
- Monitoring the size of task queues represented as Redis lists.
- Managing real-time data streams where list lengths indicate workload or backlog.
- Automating Redis data management tasks within larger automation pipelines.
Practical example: You have a Redis list named "jobQueue" that holds pending jobs. Using this node's "List Length" operation, you can retrieve how many jobs are currently queued and trigger alerts or scaling actions based on the queue size.
Properties
| Name | Meaning |
|---|---|
| List | The name of the Redis list whose length you want to retrieve. |
Note: The provided properties JSON includes an additional property "Value Is JSON" which applies only when the key type is "hash" (not relevant for "List Length" operation).
Output
The output JSON object contains:
list: The name of the Redis list queried.length: The integer length of the specified list.
Example output JSON:
{
"list": "myList",
"length": 42
}
This output allows downstream nodes or workflows to use the list length value for conditional logic, monitoring, or reporting.
Dependencies
- Requires a Redis server connection configured via credentials providing necessary authentication (e.g., API key or password).
- The node uses a Redis client library internally to communicate with the Redis instance.
- No additional external services are required beyond the Redis server.
Troubleshooting
Common issues:
- Connection failures due to incorrect Redis credentials or network issues.
- Specifying a non-existent list name will return a length of zero without error.
- Redis server unavailability or timeouts may cause errors.
Error messages:
- Connection errors typically indicate credential or network problems; verify Redis server accessibility and credentials.
- If the node throws an error about invalid parameters, ensure the "List" property is set and not empty.
- Unexpected errors during execution may be retried if "Continue On Fail" is enabled; otherwise, they will stop the workflow.