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
The node "Redis Enhanced" provides a comprehensive interface to interact with a Redis database, supporting a wide range of operations such as publishing messages, manipulating keys and data structures (strings, hashes, lists, sets, sorted sets), executing Lua scripts, and retrieving server information. The "Publish" operation specifically allows sending messages to a Redis channel, which is useful in scenarios involving real-time messaging, event broadcasting, or pub/sub communication patterns.
Practical examples:
- Broadcasting notifications or events to multiple subscribers via Redis channels.
- Sending commands or updates to other services 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 message content to publish to the specified Redis channel. |
| Value Is JSON | (Only relevant if key type is "hash") Indicates whether the value is JSON or key-value pairs. |
Output
The output of the "Publish" operation does not return any new data from Redis; it simply returns the input data unchanged. This means the json output field contains the same data as the input item, confirming that the publish action was executed.
No binary data output is produced by this operation.
Dependencies
- Requires a connection to a Redis instance configured via credentials that include necessary authentication (e.g., an API key or password).
- The node depends on the Redis client library to connect and communicate with the Redis server.
- Proper Redis server access and permissions are required to publish messages to channels.
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.
- Invalid or empty channel names or message data will cause the node to throw errors.
Error messages:
- Errors related to connection (e.g., timeout, authentication failure) require checking credentials and network connectivity.
- If the node throws an error about missing required parameters, ensure that both "Channel" and "Data" fields are correctly set.
- If the node is set to continue on fail, errors will be returned in the output JSON under an
errorproperty.