Actions37
- Append
- Blocking Pop Left
- Blocking Pop Right
- Delete
- Eval
- Exists
- Expire
- 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 Members
- Set Remove
- Sorted Set Add
- Sorted Set Cardinality
- Sorted Set Range
- Sorted Set Remove
- String Length
- TTL
Overview
This node, named "Redis Enhanced," provides a comprehensive interface to interact with a Redis database. It supports a wide range of Redis operations including publishing messages to channels, manipulating keys and data structures (strings, hashes, lists, sets, sorted sets), executing Lua scripts, and managing key expiration.
The Publish operation specifically allows sending messages to a specified Redis channel, which is useful in scenarios involving real-time messaging, event broadcasting, or pub/sub communication patterns. For example, you can use this node to publish notifications or updates to subscribers listening on a Redis channel.
Properties
| Name | Meaning |
|---|---|
| Channel | The name of the Redis channel to which the message will be published. |
| Data | The message content to publish to the specified Redis channel. |
| Value Is JSON | (Only shown if key type is "hash") Indicates whether the value is JSON or key-value pairs. |
Output
- The output contains the input item unchanged after publishing the message.
- The
jsonoutput field does not contain additional data for the Publish operation since publishing is a fire-and-forget action. - No binary data output is produced by this operation.
Dependencies
- Requires a connection to a Redis instance configured via credentials that provide necessary authentication (e.g., an API key or password).
- The node uses a Redis client library internally to connect and execute commands.
- Proper Redis server access and permissions are required.
- No additional environment variables or external services beyond Redis are needed.
Troubleshooting
- Common issues:
- Connection failures due to incorrect Redis credentials or network issues.
- Publishing to a non-existent or unauthorized channel may fail silently or cause errors.
- Error messages:
- If the Redis server is unreachable or credentials are invalid, the node will throw a connection error.
- Errors during publishing will be reported unless the node is set to continue on failure, in which case the error is included in the output.
- Resolution:
- Verify Redis credentials and network connectivity.
- Ensure the Redis server is running and accessible.
- Confirm the channel name is correct and allowed by your Redis configuration.
Links and References
- Redis Pub/Sub Documentation
- Redis Official Website
- n8n Documentation (for general usage of the Redis Enhanced node)