Triggers
A trigger is the node that starts a workflow run. Every workflow has exactly one active trigger.
This section covers each built-in trigger type and the connector-event triggers in detail. For a quick categorised overview, see Nodes → Triggers.
Pages in this section
| Trigger | When to use |
|---|---|
| Manual & test runs | Development, ad-hoc, or API-driven runs |
| Webhook trigger | External services pushing events (Stripe, GitHub, custom) |
| Schedule trigger | Time-based recurrence, hourly syncs, daily reports, cron |
| Form trigger | User-submitted forms |
| Chat trigger | Conversational entry points |
| Connector event triggers | Events from integrated services (Slack message, Salesforce update) |
Choosing a trigger
| Question | Trigger |
|---|---|
| "An external system needs to push events to me." | Webhook (or a connector trigger if that system has one) |
| "I want this to run on a schedule." | Schedule |
| "A human starts it by filling in a form." | Form |
| "I call it from code I control." | Manual / API |
| "An LLM agent invokes it as a tool." | MCP trigger |
| "It's a chatbot turn." | Chat |
Common settings across all triggers
Every trigger has a few workflow-level controls under Workflow settings → Trigger options:
| Setting | What it controls |
|---|---|
| Concurrency | Maximum number of runs of this workflow active at once. Extra invocations queue. |
| Idempotency key | Optional expression. If set, two trigger fires with the same key within the dedupe window count as one. |
| Rate limit | Throttle the trigger itself (e.g. max 60 webhook fires per minute). |
| Active only when | Optional gate, workflow only fires when this expression is truthy at the trigger moment. |
Related
- Core concepts → Workflows
- Nodes → Triggers, short reference
Found something out of date? This page lives in the Flero docs content set.