Event

Controlled node

Overview

The Event node acts as a trigger for your workflow, listening for a specific named event and firing when that event occurs. This node is essential for creating reactive workflows that respond to external actions such as form submissions, button clicks, webhook calls, or other asynchronous triggers.

When the workflow initializes, the Event node registers itself to listen for a global event with the name specified in its Name input. Once that event is triggered anywhere in the system (for example, from a form action or external API call), the node fires its Fired output event, allowing downstream nodes to execute.

Common Use Cases

• Triggering workflows from UI button clicks (using Form Event nodes)
• Starting workflows from external webhooks or API calls
• Creating event-driven architectures within your application
• Chaining workflows together by triggering events from one workflow to another

Inputs

Input	Type	Description	Default
Name	Text	The name of the event to listen for. When an event with this name is triggered globally, this node will fire.	-

Outputs

Output	Type	Description
Fired	Event	Fires when the specified event name has been triggered in the system.

Runtime Behavior and Defaults

During workflow initialization, the Event node automatically connects itself to the global event bus using the value provided in the Name input. It registers a connection from the global scope (_) to itself, listening specifically for events matching that name.

At runtime, when any event is triggered in the workflow:

1. The node checks if the incoming event name matches its configured Name
2. If matched, it immediately fires the Fired output event
3. If not matched, the node remains idle and continues listening

The node has no default value for the Name input—it must be configured before the workflow runs. If the Name input is empty or undefined, the node will not establish any connections and will never fire.

Event Naming

Event names are case-sensitive and should be unique within your project to avoid unintended triggers. For form-specific events, consider using the Form Event node instead, which handles page and element scoping automatically.

Example

Here's how to use the Event node to trigger a workflow from a form button click:

1. Configure the Event Node: Set the Name input to submitForm (or any identifier you choose).

2. Connect to Form Elements: In your UI form, configure a Button element to trigger the event submitForm when clicked.

3. Wire the Workflow: Connect the Fired output of the Event node to the Run input of an AI Write node.

4. Execution Flow: When the user clicks the button in the UI, it triggers the submitForm event, causing the Event node to fire and start the AI generation process.

[Event Node: Name="submitForm"] → [Fired] → [AI Write Node: Run]

This pattern allows you to create interactive applications where user actions in the UI seamlessly trigger complex backend workflows.