Workflows
Triggers
Every workflow starts with one Trigger node. Configure it to listen on a webhook, fire on a cron, watch an inbox, accept Slack commands, or run interactively from chat or a button.
What you'll learn
- The six trigger types and when to pick each
- How to configure each trigger's input contract
- How the trigger payload reaches downstream nodes
The six trigger types
- 1
Webhook
Exposes an HTTPS endpoint. Configure expected payload schema, auth header, and secret. Any POST to the URL invokes the workflow with the body as input. - 2
Schedule
Cron-based. Set a cron expression (every hour, weekdays 9am, etc.) and a timezone. Optional payload template provides static input each run. - 3
Email
Generates an inbound address. Every message to the address invokes the workflow with the parsed email (subject, body, attachments, sender) as input. - 4
Slack
Binds to a slash command or mention in a connected Slack workspace. The message text, user, and channel become the workflow input. - 5
Manual
A Run button in the UI. Useful for back-office workflows where an operator kicks off execution. Optionally prompts the operator for input parameters. - 6
Chat
Embeds the workflow into a chat session. Each user message is one invocation; conversation history is preserved across runs in the session.
Wiring the payload
The trigger emits its payload as the input of the first downstream node. Reference fields with
{{trigger.field}} inside any node's configuration form — agent prompts, condition expressions, and loop iterators all support the same syntax.Frequently asked questions
- Can one workflow have multiple triggers?
- No. Each workflow has exactly one Trigger node. To handle multiple entry points, build separate workflows or use a Sub-Workflow node to share downstream logic.
- How do I secure the Webhook trigger?
- Configure a shared secret in the trigger panel. Incoming requests must include it in the Authorization header — requests without it are rejected at the edge before any workflow runs.
- Does the Schedule trigger run if a previous execution is still going?
- By default, overlapping runs are allowed. Toggle Single-flight in the trigger panel to skip the next tick when the previous run is still active.
- What happens when an Email trigger receives spam?
- The inbound address has built-in SPF, DKIM, and DMARC checks. Messages failing authentication are dropped before invoking the workflow.