Overview
The node provides extended Redis operations, allowing users to interact with a Redis database for various data management tasks. It supports common Redis commands such as publishing messages to channels, setting and getting keys, manipulating hashes, lists, and more.
Specifically, the Publish operation enables sending messages to a specified Redis channel. This is useful in scenarios where you want to broadcast events or data updates to multiple subscribers listening on that channel. For example, it can be used to notify other systems or services about changes in real-time, trigger workflows, or implement pub/sub messaging patterns.
Properties
| Name | Meaning |
|---|---|
| Channel | The name of the Redis channel to which the message will be published. |
| Data | The message content/data to publish to the specified Redis channel. |
| Value Is JSON | (Shown only if key type is "hash") Indicates whether the value is JSON or key-value pairs. |
Output
- The output contains the input items passed through unchanged after publishing the message.
- The
jsonfield does not contain additional data for the Publish operation since it only sends data to a channel without returning a response. - No binary data output is produced by this operation.
Dependencies
- Requires a connection to a Redis server.
- Needs an API authentication credential configured in n8n to connect securely to Redis.
- Uses Redis client library internally to perform operations.
- The node expects the Redis server to support the standard Redis Pub/Sub commands.
Troubleshooting
- Connection errors: If the node cannot connect to Redis, verify the credentials and network connectivity to the Redis server.
- Permission issues: Ensure the Redis user has permission to publish to the specified channel.
- Invalid channel or data: The channel name and data must be non-empty strings; otherwise, the operation may fail.
- Error handling: If an error occurs during publishing, the node either throws an error or continues based on the "Continue On Fail" setting.
- Common error messages include connection timeouts, authentication failures, or invalid command usage. Resolving these typically involves checking credentials, Redis server status, and input parameters.