Redis Pro icon

Redis Pro

Get, send and update data in Redis with enhanced features
Join our community

Actions9

Overview

This node interacts with a Redis database to perform various operations such as retrieving, setting, deleting keys, incrementing values, publishing messages, and manipulating lists. It supports connection pooling for performance optimization or direct connections for safer, isolated executions. The node is useful for workflows that require caching, real-time data processing, or message brokering using Redis.

Use Case Examples

  1. Retrieve a value from Redis by key and store it in the workflow data.
  2. Set a new key-value pair in Redis with optional expiration time.
  3. Delete a specific key from Redis.
  4. Increment a numeric key atomically in Redis and optionally set a TTL (time to live).

Properties

Name Meaning
Connection Mode Determines how Redis connections are managed: either pooled for reuse across executions or direct for new connections each time.
Name The property name in the workflow data where the retrieved Redis data will be stored. Supports dot-notation for nested properties.
Key The Redis key to operate on (get, set, delete, increment, etc.).
Key Type Specifies the data type of the Redis key to optimize retrieval: automatic detection, hash, list, set, or string.
Options Additional options such as whether to use dot-notation when setting properties in the output data.
Value Is JSON For hash key types, indicates whether the value is JSON or key-value pairs.

Output

JSON

  • propertyName - The property in the output JSON where the retrieved Redis data is stored, supporting dot-notation for nested structures.
  • error - Error message if the operation fails and continueOnFail is enabled.
  • keys - When retrieving keys by pattern, contains the list of matching keys.

Dependencies

  • Redis server connection
  • An API key credential for Redis authentication

Troubleshooting

  • Connection errors if Redis server is unreachable or credentials are incorrect. Verify connection details and credentials.
  • Operation failures if the specified key does not exist or the key type is mismatched. Ensure the key exists and the correct key type is selected.
  • Timeouts or slow responses when using automatic key type detection due to extra type requests. Use explicit key types when possible to improve performance.
  • Errors during JSON parsing if the stored data is not valid JSON when 'Value Is JSON' is enabled. Ensure stored data format matches the expected type.

Links

Discussion