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
This node, named "Redis Enhanced," provides a comprehensive interface to interact with a Redis database. It supports a wide range of Redis operations including string manipulation, list operations, set operations, sorted sets, hashes, key management, and Lua script execution.
The specific operation "Set Is Member" checks whether a given member exists within a specified Redis set. This is useful in scenarios where you want to verify membership before performing further actions, such as access control, feature toggling, or filtering data based on set membership.
Practical example:
You have a Redis set containing user IDs who have premium access. Using the "Set Is Member" operation, you can check if a particular user ID is part of this set to grant or deny premium features dynamically.
Properties
| Name | Meaning |
|---|---|
| Set | The name of the Redis set to check for membership. |
| Member | The member value to check if it exists in the set. |
| Value Is JSON | (Shown only if key type is hash) Indicates whether the value is JSON or key-value pairs. |
Note: For the "Set Is Member" operation, only the "Set" and "Member" properties are required and relevant.
Output
The output JSON object contains:
set: The name of the Redis set checked.member: The member value that was checked.isMember: A boolean indicating whether the member exists in the set (trueif member exists, otherwisefalse).
Example output JSON:
{
"set": "premiumUsers",
"member": "user123",
"isMember": true
}
No binary data output is involved in this operation.
Dependencies
- Requires a Redis server connection configured via an API key credential or equivalent authentication method.
- The node uses a Redis client library internally to communicate with the Redis instance.
- Proper Redis credentials must be provided in n8n for the node to connect successfully.
Troubleshooting
Common issues:
- Connection failures due to incorrect Redis credentials or network issues.
- Checking membership on a non-existent set will simply return
isMember: false. - Providing empty or invalid set/member names may cause errors or unexpected results.
Error messages:
- Errors related to connection or command execution will be thrown by the node.
- If the node is set to continue on failure, error details will be included in the output JSON under an
errorproperty. - Ensure that the Redis server is reachable and credentials are correct to avoid connection errors.