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 appending data to strings, setting and getting keys, managing lists, sets, sorted sets, hashes, and executing Lua scripts. The "Append" operation specifically appends a given value to the end of an existing string stored at a specified key in Redis.
This node is beneficial in scenarios where you need to manipulate Redis data directly within an n8n workflow, for example:
- Appending log entries or incremental data to a Redis string.
- Building up messages or accumulating values over time without overwriting existing data.
- Managing real-time data streams or counters that require atomic append operations.
Practical example: You have a Redis key storing a string representing a chat message history. Using the Append operation, you can add new messages to this string without replacing the entire content.
Properties
| Name | Meaning |
|---|---|
| Value Is JSON | Whether the value to set or append is treated as JSON or as simple key-value pairs (only shown if key type is hash). Default is true. |
| Key | The name of the Redis key to which the value will be appended. |
| Value | The string value to append to the existing value of the specified key. |
Output
The output JSON object for the Append operation contains:
key: The Redis key to which the value was appended.newLength: The new length of the string after the append operation.
Example output JSON:
{
"key": "exampleKey",
"newLength": 42
}
This indicates the append was successful and shows the updated length of the string stored at the key.
The node does not output binary data for this operation.
Dependencies
- Requires a Redis server connection configured via credentials providing necessary authentication (e.g., API key or password).
- The node uses a Redis client library internally to connect and execute commands.
- No additional environment variables are explicitly required beyond the Redis credentials setup.
Troubleshooting
Common issues:
- Connection failures due to incorrect Redis credentials or network issues.
- Attempting to append to a key that holds a non-string data type may cause errors.
- Providing invalid JSON when
Value Is JSONis enabled for hash types could lead to parsing errors.
Error messages:
- Errors related to connection or authentication typically indicate credential misconfiguration.
- Errors about wrong data types usually mean the key exists but is not a string, so append cannot be performed.
- If the node throws an error about key-value pairs or JSON parsing, verify the input format matches expectations.
Resolution tips:
- Ensure Redis credentials are correct and the Redis server is reachable.
- Confirm the key's data type in Redis before appending.
- Validate JSON input if using JSON mode for hash key types.