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 node "Redis Enhanced" provides a comprehensive interface to interact with a Redis database, supporting a wide range of operations including data retrieval, insertion, deletion, and advanced data structure manipulations. Specifically, the "Sorted Set Remove" operation allows users to remove one or more members from a sorted set stored in Redis.
This node is beneficial in scenarios where you need to manage Redis data programmatically within an n8n workflow, such as cleaning up sorted sets by removing outdated or unwanted members, managing leaderboard entries, or maintaining priority queues.
Example use case:
You have a sorted set representing user scores in a game leaderboard. When a user leaves the game or their score needs to be invalidated, you can use this node's "Sorted Set Remove" operation to efficiently remove that user's entry from the sorted set.
Properties
| Name | Meaning |
|---|---|
| Sorted Set | The name of the sorted set in Redis from which members will be removed. |
| Members | Space-separated list of members to remove from the sorted set (e.g., "member1 member2"). |
| Value Is JSON | Whether the value is JSON or key-value pairs (only relevant if key type is hash; not used for sorted set removal). |
Output
The output JSON object contains information about the removal operation:
sortedSet: The name of the sorted set from which members were removed.removed: The number of members successfully removed.members: An array of the members that were requested to be removed.
Example output:
{
"sortedSet": "mySortedSet",
"removed": 2,
"members": ["member1", "member2"]
}
This output confirms which members were targeted and how many were actually removed from the sorted set.
Dependencies
- Requires a connection to a Redis instance configured via an API key credential or equivalent authentication method.
- The node uses the Redis client library to communicate with the Redis server.
- Proper Redis credentials must be configured in n8n for the node to connect and perform operations.
Troubleshooting
Common issues:
- Incorrect Redis credentials or connection details will cause connection failures.
- Specifying members that do not exist in the sorted set will result in fewer removals than requested (the node returns the count of actually removed members).
- Providing an empty or malformed members string may cause errors or no action.
Error messages:
- Errors related to connection issues typically indicate misconfigured credentials or network problems.
- If the members string has an odd number of elements when pairs are expected (not applicable here but relevant for other operations), an error will be thrown.
- If the sorted set name is missing or empty, the node will throw an error indicating a required parameter is missing.
Resolution tips:
- Verify Redis credentials and connectivity.
- Ensure the sorted set name and members are correctly specified.
- Use the "Continue On Fail" option in the node settings to handle errors gracefully in workflows.