Event-driven notifications. Return a msg back to the event-out node that originated this flow.
This node must be at the end of a flow that starts with an event-in node. It requires the msg._eventOriginator property to exist and contain the node-id of the originating event-out node.
This allows you to create a code LOOP in your flows.

Inputs

_eventOriginator string

REQUIRED, the node ID of the originating event-out node.

All other input msg properties are passed back to the originating event-out node.

Outputs

All input msg properties are passed back to the originating event-out node. The input msg.topic may be overridden using the Node Settings.

msg._eventOriginator is added to the output msg to help with flow debugging should you need it.

If passthrough is set, the input message is sent to the output.

Node Settings

Name string

A short description shown in the admin interface

Topic string

If provided, will overwrite the topic provided in the input msg.

passthrough boolean

If selected, an output port will appear and any input msg will be also delivered to the output. This allows you to use the node in-line with a flow but still benefit from listeners elsewhere in your flows and tabs.