Actions35
- 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
- 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 setting, getting, deleting keys, manipulating lists, sets, sorted sets, hashes, and executing Lua scripts. It is designed for scenarios where users need to manage Redis data programmatically within an n8n workflow, enabling automation of caching, messaging, counters, and data storage tasks.
For the Delete operation specifically, the node deletes a specified key from the Redis database. This is useful when you want to remove obsolete or temporary data, clear cache entries, or manage Redis storage by deleting unwanted keys.
Practical example:
- Automatically delete a session token key after user logout.
- Remove cached API response data after it becomes stale.
Properties
| Name | Meaning |
|---|---|
| Key | Name of the key to delete from Redis |
Note: For the Delete operation, only the "Key" property is required and used.
Output
The output is an array of JSON objects corresponding to each input item processed. For the Delete operation, the output simply returns the original input item unchanged (i.e., the same JSON data that was input). There is no additional data returned from Redis on deletion.
Example output for one item:
{
"json": {
// original input data unchanged
}
}
No binary data output is produced by this operation.
Dependencies
- Requires a connection to a Redis instance.
- Needs an API authentication credential configured in n8n to connect to Redis.
- The node uses a Redis client library internally to perform commands.
- No additional environment variables are explicitly required beyond the Redis credentials.
Troubleshooting
Common issues:
- Connection failures due to incorrect Redis credentials or network issues.
- Attempting to delete a key that does not exist will not cause an error but simply have no effect.
- If Redis server is unavailable or times out, the node will throw an error unless "Continue On Fail" is enabled.
Error messages:
- Connection errors: Check Redis credentials and network connectivity.
- Permission errors: Ensure the Redis user has permission to delete keys.
- Invalid key format: Make sure the key name is a valid string.
To resolve errors, verify Redis server status, credentials, and key names.