<triggers>
<triggers> contains one or more trigger definitions that can admit runs into the same root workflow steps.
Why use it
Use it when a workflow should start from manual input, HTTP, time, events, or a supported communication provider.
Common use cases
- Expose an authenticated webhook.
- Run on a schedule or interval.
- Receive provider messages.
- Support several admission sources for one workflow.
Syntax
WOML
<triggers>
<manual id="start" />
<webhook
id="newOrder"
path="/webhooks/orders"
auth="bearer"
secret="{{secrets.ORDER_WEBHOOK_TOKEN}}"
/>
</triggers>Rules and behavior
- It is optional for call-only workflows.
- When present, it must contain at least one trigger; an empty
<triggers />is invalid. - Every trigger starts the same root
<steps>. - WOML v1 does not route different triggers to different entry nodes.
- Normalized trigger input becomes
context.payload.