Actions37
- Append
- Blocking Pop Left
- Blocking Pop Right
- Delete
- Eval
- Exists
- Expire
- Expire At
- Get
- Get Set
- Hash Exists
- Hash Keys
- Hash Length
- Hash Values
- Increment
- Info
- Keys
- List Length
- Multi Get
- Multi Set
- Persist
- Pop
- Publish
- Push
- Scan
- Set
- Set Add
- Set Cardinality
- Set Is Member
- Set Members
- 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 setting, getting, deleting keys, manipulating lists, sets, sorted sets, hashes, and executing Lua scripts. It is designed for users who want enhanced control over Redis data directly within their n8n workflows.
For the Delete operation specifically, the node deletes a specified key from the Redis database. This is useful in scenarios where you need to remove obsolete or sensitive data, clear cache entries, or manage Redis storage by deleting keys that are no longer needed.
Practical example:
- Automatically delete a session token key after user logout.
- Remove temporary cache keys after processing data to free up memory.
Properties
| Name | Meaning |
|---|---|
| Key | The name of the key to delete from Redis. |
Note: The provided properties JSON only includes "Key" and "Value Is JSON" (the latter applies only when key type is "hash" and not relevant for Delete operation).
Output
The output of the Delete operation returns the input item unchanged for each processed item. There is no additional JSON data returned on successful deletion. If an error occurs and "Continue On Fail" is enabled, the output will contain an error message under json.error.
Example output on success (passes through original input item):
{
"json": {
// original input data fields
}
}
Example output on failure with continueOnFail enabled:
{
"json": {
"error": "Error message describing the failure"
},
"pairedItem": {
"item": 0
}
}
Dependencies
- Requires a Redis server accessible via credentials configured in n8n.
- Needs an API key or authentication token credential for Redis connection.
- Uses the Redis client library internally to connect and execute commands.
- No additional external services required beyond Redis itself.
Troubleshooting
Common issues:
- Connection failures due to incorrect Redis credentials or network issues.
- Attempting to delete a key that does not exist will not throw an error but simply have no effect.
- Permissions issues if the Redis user does not have delete rights.
Common error messages:
"ECONNREFUSED"or similar connection errors: Check Redis server availability and credentials."WRONGTYPE Operation against a key holding the wrong kind of value": Unlikely for delete, but may occur if Redis is misconfigured."Key-value pairs must be even number of arguments": Not applicable for delete, but relevant for other operations like mset.
Resolution tips:
- Verify Redis credentials and connectivity using the node's credential test feature.
- Ensure the key name is correctly specified and exists if expecting confirmation.
- Enable "Continue On Fail" to handle errors gracefully in workflows.
Links and References
- Redis Official Documentation
- Redis DEL Command
- n8n Documentation - Creating Nodes
- n8n Redis Node (Community) (for comparison)
This summary focuses exclusively on the Delete operation of the Redis Enhanced node based on the provided source code and property definitions.