Overview
The node "RedisExtended" provides extended interaction capabilities with a Redis database. It supports various operations such as deleting keys, retrieving values, setting values, incrementing counters, publishing messages to channels, manipulating lists, and working with hashes. This node is beneficial in scenarios where you need to integrate Redis data storage or messaging into your workflows, for example:
- Deleting a specific key from Redis to clean up outdated cache entries.
- Retrieving the value of a key or hash field to use in subsequent workflow steps.
- Incrementing counters atomically for rate limiting or tracking events.
- Publishing messages to Redis channels for real-time notifications.
- Pushing or popping items from Redis lists to manage queues.
Specifically, the Delete operation removes a specified key from the Redis store.
Properties
| Name | Meaning |
|---|---|
| Key | Name of the key to delete from Redis. |
| Value Is JSON | Whether the value is JSON or key-value pairs (only relevant for hash key types). |
Note: For the Delete operation, only the Key property is required and used.
Output
The output for the Delete operation returns the original input item unchanged after successfully deleting the specified key from Redis. The output JSON structure corresponds directly to the input data without additional fields.
Example output JSON for a deleted key:
{
// Original input data passed through unchanged
}
No binary data is produced by this operation.
Dependencies
- Requires a connection to a Redis instance configured via an API key credential.
- The node uses a Redis client library to connect and execute commands.
- The Redis server must be accessible and properly authenticated for the node to function.
Troubleshooting
- Connection errors: If the node cannot connect to Redis, verify that the credentials and network access are correct.
- Key not found: Deleting a non-existent key does not throw an error; it simply has no effect.
- Permission issues: Ensure the Redis user has permission to delete keys.
- Error handling: If an error occurs during deletion and "Continue On Fail" is disabled, the node will stop execution and report the error. Enable "Continue On Fail" to handle errors gracefully within workflows.