The Message Queue Node enables connection to custom message queues and provides message publishing functionality. Message Queue Node belongs to Basic Node.
Note:
The Message Queue Node is designed only for message publishing. Subscribing to queues and consuming messages requires custom service development by the user.
Directions
Input Variables
The input variable only takes effect inside the node and cannot be used cross-node. Click "Add" to configure as follows and add an input variable.
Configuration
Description
Variable Name
The variable name can only contain letters, digits, or underscores, must start with a letter or underscore. Required.
Description
Description of this variable. Optional
Data source
The data source of this variable supports two options: "Refer" and "Input". "Refer" allows selecting output variables from all preceding nodes, and "Input" lets you manually fill in a fixed value. Required
Type
The data type of this variable cannot be selected and defaults to the variable type referred or the string type entered.
Message Queue Type
Message Queue Node supports interfacing with Kafka (for details, please refer to Kafka introduction) and RocketMQ (for details, please refer to RocketMQ introduction). These two commonly used message queues have different detailed settings. Users can choose appropriate message queues according to their use case requirements.
Connection Settings
Configure the connection method according to the selected message queue type. The current node supports common connection configuration information for Kafka, RocketMQ.
Message content
The message content is the information sent to the Message Queue, supporting references to the node's input variables or manual entry of message content.
Output Variable
The output variables of the message publishing action after execution. Includes the message queue's send status SendStatus, error info ErrorMsg, timestamp Timestamp, message size MessageSize, and runtime error info Error (data type is object, this field is empty when running normally).
Handling error
Exception handling can be enabled manually (off by default), supporting timeout-triggered handling, exception retry, and exception handling method configuration. The configuration content is in the table below.
Currently only support duration set by the user for "timeout-triggered handling", other exceptions are automatically identified by the platform.
Configuration
Description
Timeout-triggered handling
The maximum duration for node operation, trigger exception handling when exceeded. The default timeout value for Message Queue node is 60s, timeout setting ranges from 1-60s.
Max Retry Attempts
Maximum number of times to rerun when the node is running exceptionally. If retries exceed the set number, consider the node call failed and execute the exception handling method below. Default is 3 times.
Retry Interval
Interval between each rerun, default is 1 second.
Exception handling method
Support three types: "Output Specific Content", "Execution Exception Flow", and "Interrupt Flow".
Exception Output Variable
Select the exception handling method as "Output Specific Content". The output variable returned when retries exceed the maximum number.
Select the exception handling method as "Output Specific Content". When an exception occurs, the workflow will not be interrupted. After exception retry, the node will return directly the output variable and variable value set by the user in the output content.
Select the exception handling method as "Execution Exception Flow". When an exception occurs, the workflow will not be interrupted. After exception retry, the node will execute the exception handling process customized by users.
Select the exception handling method as "Interrupt process". There are no more setting items. When an exception occurs, the workflow execution is interrupted.
Application Example
Batch analyze social media articles and tag them accordingly. Use the Message Queue node to send the analysis results to the message queue. Other services can subscribe to the message queue and consume the article analysis results. Example workflow as follows:
FAQs
1. Is message processing sequence important? How to control it in the workflow?
For approval, order processing and other stateful dependent scenarios, message sequence is very important. In the workflow, orchestrate the leading and trailing order of Message Queue nodes to achieve control message sending order.
2. Are there any requirements for the message format or content?
The workflow Message Queue Node provides a message configuration text box, supporting users to output any message content with no mandatory requirements for the message format.
