Custom
AI-generatedSummary
Listen for and trigger workflow executions upon receiving RabbitMQ messages matching a custom routing key pattern, with configurable message acknowledgement and processing options.
Inputs
- routingKeyPrefix — Optional prefix added before the custom pattern (separated by a dot) to form the full routing key.
- pattern (required) — The prefix-free custom pattern to match for routing keys. Combined with the routing key prefix to subscribe to specific messages.
- queue — The queue name to listen on; if empty, a unique queue name is generated automatically.
- options.acknowledge — Controls when to acknowledge and delete the message from the queue: immediately on receipt, after execution finishes (successfully or not), or later via workflow action.
- options.jsonParseBody — Determines whether to parse the message body as JSON into an object.
- options.onlyContent — If true, returns only the content of the message rather than the full message object.
- options.parallelMessages — Limits how many message executions can run in parallel; -1 means no limit. Only applicable if acknowledgement is not immediate.
Output shape
a single item per consumed message emitted from the node's main output
The data returned depends on options: if onlyContent is true, the output is the parsed message content only; otherwise the full message object. Messages are acknowledged according to the configured acknowledge option, supporting immediate, after execution (successfully or generally), or deferred acknowledgement via workflow action. Supports manual trigger mode to fetch one message or continuous listening mode with parallel processing limits.