🇬🇧 EN

📡 Emit Event

Emits a named event that can trigger other workflows configured with an Event Trigger node. Use Emit Event to create event-driven pipelines where one workflow hands off work to another, enabling modular, loosely-coupled workflow architectures.

Category: Notifications & Messaging · Type identifier: emit_event

Overview

Emit Event implements a publish-subscribe pattern entirely within Flusso. When this node runs, it publishes a named event to Flusso's internal event bus. Any workflow whose trigger is an Event Trigger listening for the same event name is started automatically, receiving the payload you define.

This allows you to decouple workflows from each other. The emitting workflow does not need to know how many listeners exist — you can add or remove listening workflows at any time without touching the emitter. All matching listeners run in parallel when the event fires.

Configuration

Field	Status	Description
Event Name	Required	The name of the event to emit, e.g. `order.completed` or `user.registered`. This must match the Event Name configured on the receiving workflow's Event Trigger node. Supports `{{ variable }}` references.
Payload	Optional	A JSON object to pass as data to the triggered workflow. The receiving workflow can access this data via its trigger output. Supports `{{ variable }}` references.
Wait for Completion	Optional	Toggle. When off (default), the event is emitted and the current step completes immediately without waiting for triggered workflows to finish. When on, the step waits for all triggered workflow runs to complete before continuing.

Output Data

After the event is emitted, the following fields are available on the step output:

Field	Type	Description
`event_name`	string	The name of the event that was emitted.
`triggered_runs`	array	IDs of the workflow runs that were started by this event.
`triggered_count`	number	Number of workflow runs triggered.

Example Usage

Workflow A processes an order and, at the end, adds an Emit Event node. Set Event Name to order.completed and Payload to:
{ "order_id": "{{ process_order.output.order_id }}", "customer_email": "{{ process_order.output.customer_email }}", "total": "{{ process_order.output.total }}" }
Workflow B uses an Event Trigger set to listen for order.completed. It sends a confirmation email using {{ trigger.output.payload.customer_email }}.
Workflow C also uses an Event Trigger on order.completed and sends a Slack notification to the sales team. Both Workflow B and C are started simultaneously when Workflow A emits the event.

Tips & Notes

Event names are case-sensitive. order.completed and Order.Completed are different events. Use a consistent naming convention such as noun.verb across your workflows.
No listeners is not an error. If no workflows are listening for the emitted event name, the node still succeeds and triggered_count will be 0.
Fire-and-forget by default. Unless Wait for Completion is on, the emitting workflow does not wait for listeners to finish. Use this for non-blocking fan-out patterns.
Conditional emit. Place a Logic Gate before the Emit Event node if you only want to emit under certain conditions, avoiding unnecessary downstream runs.

Related Nodes

Event Trigger — the trigger used in workflows that listen for events emitted by this node.
Webhook Notification — notify an external URL instead of triggering another Flusso workflow.
Logic Gate — conditionally decide whether to emit an event based on prior step output.