Triggers
Manual Trigger
Run a workflow on demand without inputs
Legacy block. New workflows use the unified Start block instead. This page still applies to existing workflows using the standalone Manual trigger.
Overview
The Manual trigger adds a simple Run button to the top of your workflow. Use it when you want to execute the workflow immediately without collecting extra data.
How It Works
- Launches the workflow using the active deployment snapshot
- Sends no payload—downstream blocks only see what they already have configured
- Perfect for quick sanity checks, smoke tests, or flows that only rely on internal variables
When to Use
- Kick off a workflow after publishing a new deployment to confirm everything still works
- Run maintenance jobs that don’t require external input
- Trigger child workflows that read state or environment variables only
Compared to Input Form
Need structured values or type validation at runtime? An Input Form trigger will collect those fields before the workflow starts -- though for a new workflow, Start covers this too.
Manual trigger runs don’t override your deployment history. Update and redeploy whenever canvas changes need to go live.