Event Start

Marks the entry point for flows used by Event to Flow and Cron to Flow agents.

Use Event Start in flows that are executed by Event to Flow and Cron to Flow agents. A single flow can contain more than one Event Start node, and the agent configuration selects which entry point to use. The Condition field is only evaluated for Event to Flow agents.

Config

• Name - optional display name for the node in the editor

• Condition - optional JSONata expression used when an Event to Flow agent needs to choose among multiple Event Start nodes in the same flow. Cron to Flow agents do not use this field.

Multiple matching Event Start nodes: If more than one Event Start node's Condition matches the same event, the Event to Flow agent delivers the event to only one matching node, not to all of them. Which node receives the event is decided by an internal node order that you cannot see or set in the editor. To make routing predictable, configure Event Start conditions so that only one condition can match a given event. If no Condition matches, the event goes to the flow's default Event Start node.

Output

Downstream nodes should read the event payload from msg.event.

Flows used by Event to Flow and Cron to Flow agents should terminate on one or more Event End or Event Error nodes so the runtime can resolve the execution cleanly.