Redis Enhanced

Overview

The node "Redis Enhanced" provides a comprehensive interface to interact with a Redis database, supporting a wide range of Redis operations including string manipulation, list handling, set operations, sorted sets, hashes, and Lua script execution. It is designed for scenarios where users need to get, send, update, or manage data in Redis with enhanced capabilities beyond basic commands.

This node is beneficial when automating workflows that require caching, messaging, real-time data processing, or managing complex data structures in Redis. For example:

• Adding or removing members from a Redis set.
• Checking membership of an element in a set.
• Executing Lua scripts for atomic operations.
• Managing expiration times on keys.
• Publishing messages to Redis channels for event-driven architectures.

Specifically, the "Set Remove" operation allows users to remove one or more members from a Redis set by specifying the set name and the members to remove.

Properties

Note: The above properties are specific to the "Set Remove" operation under the default resource.

Output

The output JSON object for the "Set Remove" operation contains:

• set: The name of the Redis set from which members were removed.
• removed: The number of members successfully removed from the set.
• members: An array of the members that were requested to be removed.

Example output JSON:

{
  "set": "mySet",
  "removed": 2,
  "members": ["member1", "member2"]
}

This output confirms which members were targeted and how many were actually removed.

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 connect and execute commands.
• No additional external services are required beyond the Redis instance.

Troubleshooting

• Common issues:

  • Connection failures due to incorrect Redis credentials or network issues.
  • Attempting to remove members from a non-existent set will result in zero removals but no error.
  • Providing an empty or improperly formatted members list may cause errors or no action.

• Error messages:

  • Errors related to Redis command failures will include the Redis error message.
  • If the input members string does not split into valid members, the node may throw an error.
  • 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 connectivity.
  • Ensure the "Members" field contains valid space-separated values.
  • Use the "continue on fail" option to handle errors gracefully in workflows.

Links and References

• Redis Sets Documentation
• Redis Command SREM
• n8n Documentation