Every flow starts at a trigger. A flow can have more than one trigger block; each is an entry point and the flow runs from the one that fired. The trigger’s output is the run’s input, which later blocks read as {{ input… }}. This page documents 8 blocks. For how flows work, see Flows and the flow editor. Values in settings can use templates such as {{ input.id }} and {{ steps.load.output.email }}; see Block reference overview.

Event

Key: trigger.event · Starts a flow Runs when a matching platform event is published. Continues to: next

HTTP request

Key: trigger.http · Starts a flow Runs when an HTTP request reaches a custom route bound to this flow. Continues to: next

Background job

Key: trigger.job · Starts a flow Runs when the flow is dispatched as a background job. Continues to: next

Manual run

Key: trigger.manual · Starts a flow Runs when started from Studio or the management API. Continues to: next This block has no settings.

Realtime message

Key: trigger.realtime · Starts a flow Runs when a client publishes to a realtime channel. Continues to: next

Resource change

Key: trigger.resource · Starts a flow Runs after a resource operation. Continues to: next

Schedule

Key: trigger.schedule · Starts a flow Runs on a schedule managed in Schedules. Continues to: next

Inbound webhook

Key: trigger.webhook · Starts a flow Runs when an inbound webhook is received and verified. Continues to: next