Redis Enhanced icon

Redis Enhanced

Get, send and update data in Redis with enhanced operations

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, key management, and Lua script execution. The node is designed for scenarios where users need to read, write, update, or manage data stored in Redis with enhanced flexibility and control.

A practical example includes checking if a specific member exists in a Redis set (useful for membership validation), adding or removing members from sets, managing expiration times on keys, or executing custom Lua scripts for complex atomic operations.

Specifically, the "Set Is Member" operation checks whether a given value is a member of a specified Redis set, which is useful for access control, feature toggles, or any scenario requiring quick membership verification.

Properties

Name Meaning
Value Is JSON Whether the value is JSON or key-value pairs (only shown when key type is hash).
Set Name of the Redis set to operate on (required for set-related operations).
Member The member value to check for membership in the set (required for "Set Is Member" operation).

Output

The output JSON structure 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 (true if member exists, false otherwise).

Example output JSON:

{
  "set": "mySet",
  "member": "user123",
  "isMember": true
}

The node does not output binary data.

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 and tested before execution.

Troubleshooting

  • Common issues:

    • Connection failures due to incorrect Redis credentials or network issues.
    • Errors when the specified set or member does not exist (usually returns false rather than error).
    • Misconfiguration of input properties such as missing required fields like "Set" or "Member".
  • Error messages:

    • Connection errors will indicate inability to connect or authenticate with Redis.
    • Input validation errors if required parameters are missing.
    • If the node is set to continue on fail, errors will be returned in the output JSON under an error property.
  • Resolutions:

    • Verify Redis credentials and network connectivity.
    • Ensure all required parameters are correctly set.
    • Use the "continue on fail" option to handle errors gracefully in workflows.

Links and References

Discussion