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
This node provides enhanced interaction with a Redis database, allowing users to perform a wide range of operations such as retrieving information about the Redis instance, managing keys and values, manipulating lists, sets, sorted sets, hashes, and executing Lua scripts. It is useful in scenarios where you need to integrate Redis data storage or caching capabilities into your workflows, for example:
- Fetching server info or key metadata.
- Reading or writing string, list, set, or hash data types.
- Incrementing counters atomically.
- Publishing messages to Redis channels.
- Executing custom Lua scripts for advanced Redis operations.
The "Info" operation specifically returns generic information about the connected Redis instance, which can be used for monitoring or debugging purposes.
Properties
| Name | Meaning |
|---|---|
| Value Is JSON | Whether the value stored in a hash key is JSON formatted or simple key-value pairs. This property appears when the key type is "hash". It defaults to true. |
Note: The above property is relevant only for the "Info" operation if the key type is "hash", but since "Info" does not use this property directly, it is more generally applicable to other operations involving hash keys.
Output
The output of the "Info" operation is a JSON object containing generic information about the Redis instance. This includes various server statistics and configuration details parsed from the raw Redis INFO command response into a structured object format.
Example output structure (simplified):
{
"redis_version": "6.2.5",
"connected_clients": 10,
"used_memory_human": "1.23M",
"uptime_in_seconds": 3600,
...
}
No binary data output is produced by this operation.
Dependencies
- Requires a Redis server connection configured via an API key credential that supports authentication to the Redis instance.
- The node uses a Redis client library internally to connect and execute commands.
- Proper network access to the Redis server must be ensured.
- No additional environment variables are required beyond the Redis credentials.
Troubleshooting
- Connection errors: If the node cannot connect to Redis, verify the credentials and network connectivity.
- Timeouts or slow responses: Large Redis instances or slow networks may cause delays; consider increasing timeout settings if available.
- Permission issues: Ensure the provided credentials have sufficient permissions to run the INFO command on the Redis server.
- Error messages: Errors thrown during execution will include the Redis error message. Use the "Continue On Fail" option to handle errors gracefully within workflows.