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
The "Redis Enhanced" node provides a comprehensive interface to interact with a Redis database, supporting a wide range of operations including string manipulation, list handling, set operations, sorted sets, hashes, and Lua script execution. The "Set Is Member" operation specifically checks whether a given member exists within a specified Redis set.
This node is beneficial in scenarios where you need to manage and query Redis data structures directly from an n8n workflow. For example, it can be used to verify user membership in a group stored as a Redis set, manage caching layers, or implement feature flags by checking if a key or member exists.
Practical example: You have a Redis set named "activeUsers" and want to check if the user ID "user123" is currently active. Using the "Set Is Member" operation, you can quickly determine membership and branch your workflow accordingly.
Properties
| Name | Meaning |
|---|---|
| Set | The name of the Redis set to operate on. |
| Member | The specific member value to check for membership in the set (used only in "Set Is Member"). |
| Value Is JSON | Indicates whether the value is JSON or key-value pairs; relevant when the key type is hash. |
Output
The output JSON object for the "Set Is Member" operation 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,falseotherwise).
Example output:
{
"set": "activeUsers",
"member": "user123",
"isMember": true
}
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 details for Redis.
- Uses the Redis client library internally to perform operations.
Troubleshooting
Common issues:
- Connection failures due to incorrect Redis credentials or network issues.
- Errors if the specified set does not exist or the member parameter is missing.
- Invalid input formats, such as empty set names or members.
Error messages:
"Key-value pairs must be even number of arguments": Occurs if key-value pairs are malformed in other operations but not relevant here.- Connection errors: Check Redis credentials and network connectivity.
- If the node throws an error about missing parameters, ensure that both "Set" and "Member" fields are correctly filled.
To resolve errors, verify all required inputs, confirm Redis server availability, and ensure proper permissions.