Webhook
Trigger via HTTP request
What this step does
On the canvas this step appears as its own node with handles you wire to neighbours. Trigger via HTTP request Open the step sheet to change labels, descriptions, and family-specific fields. See the Triggers article for how this template sits beside related steps.
Execution tab
Triggers start a run and declare the initial payload. They do not use an Execution tab like runnable steps. Configure invoke fields, webhook mapping, or schedule timing on the trigger-specific panels instead. See Execution settings for how runnable steps use that tab.
Output tab
Triggers publish invoke fields, webhook payload slices, or schedule metadata that later hops read as {{trigger_inputs.*}} and related namespaces. Use Output only when the product exposes mapping for your trigger variant.
| Value | Description |
|---|---|
| {{trigger_inputs}} | Namespace for values captured from the trigger on early hops (shape depends on trigger type). |