Core concepts
Triggers
Events that start a workflow execution automatically.
Every Workflow has exactly one trigger node. The trigger is the entry point: when its event occurs, EzFlow starts a new run and passes the event payload to downstream nodes.
You add a trigger by opening the Nodes panel, expanding the Triggers section, and dragging a trigger node onto the canvas.
Available triggers
| Trigger | Description |
|---|---|
| HTTP Trigger | Fires when an inbound HTTP request arrives at the Workflow's unique webhook URL. |
| Cron Trigger | Fires on a repeating schedule defined by a cron expression. |
| Form Trigger | Fires when a visitor submits one of your published EzFlow Forms. |
| Webhook Inbound | Fires on an inbound webhook from a named webhook endpoint. |
| Slack Trigger | Fires when your connected Slack app receives a configured event — for example, an app mention or a slash command. |
| Calendar Event Created | Fires when a new event is created on a connected calendar. |
| Calendar Event Updated | Fires when an existing calendar event is modified. |
| Calendar Event Cancelled | Fires when a calendar event is cancelled. |
| Calendar Event Starting Soon | Fires a configurable number of minutes before a calendar event begins. |
| Calendar Daily Agenda | Fires once per day at a set time with that day's calendar agenda. |
Trigger output
Each trigger produces an output payload that downstream nodes can reference. For example, the HTTP Trigger exposes a body handle containing the full request body. The Slack Trigger exposes handles for text, userId, channelId, threadTs, and others. See each trigger's reference page for its complete output handle list.
Related
- Workflows — how the trigger fits into the overall graph
- Connections — how the trigger's output reaches action nodes
- Executions & Jobs — what happens after the trigger fires