Overview
The node "RedisExtended" provides a versatile interface to interact with a Redis database. It supports multiple operations such as getting, setting, deleting keys, working with hashes, lists, sets, and publishing messages to channels. The "Hash Get" operation specifically retrieves the value of a specified field from a hash stored in Redis.
This node is beneficial when you need to integrate Redis data retrieval or manipulation into your n8n workflows. For example, you can use it to fetch user session data stored as hashes, retrieve configuration settings, or manage counters and lists dynamically during automation.
Practical example for "Hash Get":
You have a Redis hash key named user:1001 containing fields like name, email, and age. Using this operation, you can get the value of the email field and store it in your workflow's JSON data under a custom property for further processing.
Properties
| Name | Meaning |
|---|---|
| Hash Key | The name of the Redis hash key from which to retrieve the field value. |
| Field | The specific field name within the hash whose value you want to get. |
| Property Name | The name of the property in the output JSON where the retrieved value will be stored. Supports dot-notation to create nested objects (e.g., "data.person[0].name"). |
| Options | Collection of additional options: - Dot Notation (boolean): Whether to interpret the property name using dot-notation. If enabled, "a.b" creates nested objects { "a": { "b": value } }. If disabled, it sets the property literally as "a.b". |
| Value Is JSON | (Shown only if key type is hash) Boolean indicating whether the value is JSON or key-value pairs. |
Output
The output JSON contains the retrieved value from the specified hash field stored under the property name defined by the user. If dot-notation is enabled, the property name can represent nested structures.
Example output JSON structure if propertyName is "user.email" and the field value is "test@example.com":
{
"user": {
"email": "test@example.com"
}
}
If dot-notation is disabled and propertyName is "user.email", the output would be:
{
"user.email": "test@example.com"
}
No binary data is output by this operation.
Dependencies
- Requires a Redis server accessible via credentials configured in n8n.
- Needs an API key or authentication token for connecting to Redis.
- Uses the Redis client library internally to perform commands.
- No additional external services are required beyond Redis itself.
Troubleshooting
- Connection errors: Ensure that the Redis credentials (host, port, password) are correctly configured and the Redis server is reachable.
- Field not found: If the specified field does not exist in the hash, the output value will be
nullor empty. Verify the field name spelling. - Invalid property name: Incorrect dot-notation usage in
propertyNamemay cause unexpected JSON structure. Disable dot-notation if unsure. - Permission issues: Make sure the Redis user has permissions to read the specified hash key and field.
- Timeouts or slow responses: Large hashes or network latency can cause delays; consider optimizing Redis or network setup.
Common error message example:
"Error: Connection refused"— indicates Redis server is unreachable or credentials are incorrect."Error: ERR no such key"— the specified hash key does not exist in Redis.
To resolve errors, verify connection details, key names, and ensure Redis server health.