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 node "Redis Enhanced" provides a comprehensive interface to interact with a Redis database, supporting a wide range of operations such as getting, setting, deleting keys, manipulating lists, sets, sorted sets, hashes, and executing Lua scripts. It is designed for users who want enhanced control over Redis data within their n8n workflows.
The Delete operation specifically allows users to delete a key from the Redis store. This is useful in scenarios where you need to remove obsolete or sensitive data, clear cache entries, or manage Redis storage by deleting keys programmatically.
Practical example:
- Automatically delete a session token stored in Redis after a user logs out.
- Remove temporary data keys after processing is complete to free up memory.
Properties
| Name | Meaning |
|---|---|
| Key | The name of the key to delete from Redis. |
| Value Is JSON | (Shown only if key type is "hash") Whether the value is JSON or key-value pairs. |
Output
The output of the Delete operation returns the input item unchanged upon successful deletion. There is no specific JSON output indicating success; the node simply passes through the original data. If an error occurs during deletion, it will throw an error unless "Continue On Fail" is enabled, in which case the error message is included in the output JSON under an error property.
Dependencies
- Requires a connection to a Redis instance configured via credentials that provide necessary authentication (e.g., API key or password).
- The node uses a Redis client library internally to connect and execute commands.
- No additional environment variables are explicitly required beyond the Redis credentials.
Troubleshooting
Common issues:
- Attempting to delete a non-existent key will not cause an error but simply have no effect.
- Connection failures due to incorrect credentials or network issues.
- Permission errors if the Redis user does not have delete rights.
Error messages:
- Connection errors: Check Redis credentials and network connectivity.
- Command errors: Ensure the key name is valid and properly formatted.
- If the node throws an error, enabling "Continue On Fail" can help workflow resilience by capturing errors in output.