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 publishing messages, managing keys, lists, sets, hashes, sorted sets, and executing Lua scripts. The "Publish" operation specifically allows sending messages to a specified Redis channel, which is useful for real-time messaging scenarios, event broadcasting, or inter-service communication.
Practical examples include:
- Broadcasting notifications or events to multiple subscribers via Redis Pub/Sub channels.
- Sending commands or data updates to other systems listening on specific Redis channels.
- Integrating Redis-based messaging into workflows for asynchronous processing.
Properties
| Name | Meaning |
|---|---|
| Channel | The name of the Redis channel to which the message will be published. |
| Data | The actual message content to publish to the specified channel. |
| Value Is JSON | (Not applicable for Publish operation) Indicates if the value is JSON or key-value pairs; relevant only when key type is hash. |
Note: For the "Publish" operation, only "Channel" and "Data" are required and used.
Output
The output of the "Publish" operation does not produce new data in the json output field; it simply returns the input data unchanged after successfully publishing the message to the Redis channel.
No binary data output is produced by this operation.
Dependencies
- Requires a connection to a Redis server configured via an API key credential or equivalent authentication method.
- The node depends on the Redis client library to connect and communicate with the Redis instance.
- Proper Redis credentials must be set up in n8n for the node to authenticate and perform operations.
Troubleshooting
- Connection Issues: If the node cannot connect to Redis, verify that the Redis server is reachable, credentials are correct, and network/firewall settings allow access.
- Publish Failures: Errors during publishing may occur if the channel name or message data is missing or invalid. Ensure both are provided and correctly formatted.
- Timeouts or Latency: High latency or timeouts might indicate network issues or Redis server overload.
- Error Messages: Common errors include connection refused, authentication failure, or invalid command syntax. Review error details and check Redis server logs for more information.
- Continue On Fail: If enabled, the node will continue processing subsequent items even if some fail, returning error details in the output.
Links and References
- Redis Pub/Sub Documentation
- Redis Official Website
- n8n Redis Node Documentation (generic) (for general Redis usage in n8n)