🇬🇧 EN

📡 Event Trigger

The Event Trigger fires a workflow when another workflow in your Flusso account emits a named event using the Emit Event node. This enables you to chain workflows together — one workflow completes a task and signals the next to begin — without tightly coupling them into a single, large workflow.

Category: Triggers · Type identifier: event_trigger

Overview

As your automation grows in complexity, it becomes valuable to split work across multiple focused workflows rather than building one enormous workflow that does everything. The Event Trigger, together with the Emit Event node, is the mechanism that connects those workflows at runtime.

The pattern works like this: Workflow A completes its task, then uses an Emit Event node to broadcast a named event (for example, order.processed) along with a payload of data. Any workflow in your account that has an Event Trigger listening for that exact event name will be started automatically, receiving the emitted payload as its input.

Multiple workflows can listen for the same event name — all of them will be started in parallel when the event is emitted. This makes the Event Trigger ideal for fan-out patterns, where a single upstream event needs to kick off several independent downstream processes, such as sending a confirmation email, updating a CRM record, and logging to an analytics system all at once.

Configuration

Field	Required	Description
Event Name	Required	The name of the event this workflow listens for. This must match exactly the event name emitted by the Emit Event node in the upstream workflow — including capitalisation and punctuation. For example, if the emitting workflow uses `order.processed`, this field must also contain `order.processed`.

Naming convention tip: Use dot-notation names that describe the domain and action, for example: user.registered, invoice.paid, report.generated. This makes the relationship between emitting and listening workflows immediately clear.

Output Data

The Event Trigger exposes the event name and the payload emitted by the upstream workflow:

Variable	Type	Description
`trigger.output.event_name`	String	The name of the event that fired this trigger, exactly as emitted.
`trigger.output.payload`	Object	The data emitted by the upstream Emit Event node's Payload Mapping configuration.

// Access the event name {{ trigger.output.event_name }} // Access payload fields passed by the emitting workflow {{ trigger.output.payload.order_id }} {{ trigger.output.payload.customer_email }} {{ trigger.output.payload.total_amount }}

Example Usage

Chaining: order processing to notification

You have two workflows: Process Order and Notify Customer. When an order finishes processing, you want the notification workflow to run automatically.

In the "Process Order" workflow, add an Emit Event node at the end. Set the event name to order.processed and map order_id and customer_email in the Payload Mapping.
Create a new "Notify Customer" workflow and add an Event Trigger as the first node. Set the Event Name to order.processed.
In the notification workflow, add an Email Notification node. Set the recipient to {{ trigger.output.payload.customer_email }} and include the order ID in the subject: Your order {{ trigger.output.payload.order_id }} is ready.
Set both workflows to Active. Now every time the Process Order workflow finishes, the Notify Customer workflow fires automatically.

Tips & Notes

Event names are case-sensitive. Order.Processed and order.processed are treated as two different events. Always use a consistent capitalisation convention across all your workflows.
No listeners is not an error. If a workflow emits an event that no other workflow is listening for, Flusso silently discards the event. The emitting workflow completes normally.
Multiple listeners are supported. Several workflows can all listen for the same event. They will all be started when the event fires, running in parallel and independently of each other.
Circular chains will loop indefinitely. If Workflow A emits an event that triggers Workflow B, and Workflow B emits an event that triggers Workflow A, you will create an infinite loop. Always check that your event chain has a defined end point.

Related Nodes

Emit Event — the node used in upstream workflows to fire an event.
Error Trigger — fires when any workflow encounters a fatal execution error.
Schedule Trigger — fires automatically on a cron schedule.