Custom
AI-generatedSummary
Listen for RabbitMQ messages on a dynamically bound queue matching a custom routing key pattern and emit workflow executions upon receiving messages.
Inputs
- routingKeyPrefix — A string prefix added before the custom pattern in the routing key, separated by a dot (defaults to 'query').
- queue — The name of the RabbitMQ queue to listen to; if left empty, a unique queue name is generated.
- pattern (required) — Prefix-free string pattern used with routingKeyPrefix to form the routing key to bind and listen to.
- options — Collection of options controlling message processing and acknowledgement including when to acknowledge message (immediately, after execution finishes, after successful execution, or later by workflow node), whether to parse the message body as JSON, whether to return only the content property, and the parallel message processing limit.
Output shape
a stream of messages parsed according to the options, each triggering a workflow execution with the message content or full message object depending on settings
The node connects to a RabbitMQ exchange (default named 'cqrs') of type 'topic' and binds to the queue using routing key composed by concatenating routingKeyPrefix and pattern with a dot. The node supports manual and activated modes with configurable parallelism and acknowledgment strategies for robust message processing. Workflow responses can influence when messages are acknowledged to allow retries or manual acknowledgement via other nodes.
Examples
Example 1: Trigger workflow with messages from RabbitMQ queue bound to routing key 'query.my.custom.pattern'
Set routingKeyPrefix to 'query', pattern to 'my.custom.pattern', optionally set queue name or leave empty to generate one; tune options for message acknowledgement and parsing as needed.