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. It supports a wide range of Redis operations such as retrieving information about the Redis instance, managing keys and values, manipulating data structures like lists, sets, hashes, and sorted sets, executing Lua scripts, and publishing messages to channels.
This node is beneficial in scenarios where you need to integrate Redis caching, messaging, or data storage capabilities into your workflows. For example:
- Fetching server info or key metadata for monitoring.
- Setting or getting cached data with various data types.
- Managing queues using list push/pop operations.
- Executing atomic increments or conditional sets for locks.
- Publishing messages to Redis channels for event-driven architectures.
The "Info" operation specifically returns generic information about the connected Redis instance, useful for diagnostics or monitoring purposes.
Properties
| Name | Meaning |
|---|---|
| Value Is JSON | Whether the value is JSON or key-value pairs (only relevant when the key type is "hash") |
Note: The above property is shown only when the key type is set to "hash" during certain operations.
Output
The output is an array of items, each containing a json object with the results of the Redis operation performed.
For the Info operation:
- The
jsonoutput contains an object representing parsed Redis server information, converted from the raw string returned by the RedisINFOcommand. - This includes various server statistics, configuration details, memory usage, clients, persistence status, replication info, CPU usage, and more.
No binary data output is produced by this operation.
Dependencies
- Requires a Redis server accessible via credentials configured in n8n.
- Needs an API authentication token or connection credentials for Redis (configured in n8n credentials).
- Uses the Redis client library internally to connect and execute commands.
Troubleshooting
- Connection errors: If the node cannot connect to Redis, verify that the Redis server is running, reachable, and credentials are correct.
- Timeouts or slow responses: Large datasets or network latency can cause delays; consider optimizing queries or increasing timeouts.
- Invalid input parameters: Ensure required fields like keys, patterns, or scripts are correctly formatted.
- Lua script errors: When using the Eval operation, syntax or runtime errors in the Lua script will cause failures.
- Key-value pair mismatch: For multi-set operations, ensure an even number of arguments (key-value pairs) is provided.
If the node is set to continue on failure, errors will be included in the output JSON under an error field instead of stopping execution.