CQRS Event Trigger icon

CQRS Event Trigger

EventTrigger

Custom

AI-generated

Summary

Listen for RabbitMQ events with a custom routing key pattern to trigger workflow executions.

Inputs

  • routingKeyPrefix — String prefix added before the custom pattern separated by a dot, default is 'event'.
  • queue — Name of the queue to listen on; if empty, a unique queue name is generated.
  • pattern (required) — Custom routing key pattern without prefix, used to form the full routing key with the prefix.
  • options.acknowledge — When to acknowledge and delete the message from the queue: immediately on receipt, after execution finishes (successfully or otherwise), or later as specified by the workflow.
  • options.jsonParseBody — Whether to parse the message body JSON string to an object, defaults to true.
  • options.onlyContent — Whether to return only the content of the message instead of the entire message object, defaults to true.
  • options.parallelMessages — Maximum number of messages to process in parallel; use -1 for no limit. Only applicable if acknowledgment is not immediate.

Output shape

outputs one main stream of messages triggering workflow executions, each output item containing either the parsed message content or the full message object depending on options

Manually triggered executions receive at most one message. In regular trigger mode, listens continuously to the specified RabbitMQ queue and routing key. The routing key combines the prefix (default 'event') and the custom pattern (separated by a dot). The queue is bound to a topic exchange named 'cqrs'. Message acknowledgment behavior is configurable and affects workflow execution concurrency. Errors during message processing are logged. The node requires RabbitMQ credentials.

Links

Discussion