Triggers
Core ways to start Sim workflows
Core Triggers
Pick one trigger per workflow to define how it starts:
API
HTTP endpoint that maps JSON bodies into workflow inputs
Chat
Deployed chat interface with streaming responses
Input Form
Typed manual input used in editor runs and child workflows
Manual
On-demand runs with no additional data
Schedule
Cron or interval based execution
Webhook
Receive external webhook payloads
Quick Comparison
| Trigger | Start condition |
|---|---|
| API | Authenticated HTTP POST |
| Chat | Chat deployment message |
| Input Form | On manual submit in editor or parent workflow |
| Manual | Run button in editor |
| Schedule | Timer managed in schedule modal |
| Webhook | On inbound HTTP request |
Using Triggers
- Drop the trigger block in the start slot.
- Configure any required schema or auth.
- Connect the block to the rest of the workflow.
Deployments power every trigger. Update the workflow, redeploy, and all trigger entry points pick up the new snapshot. Learn more in Execution → Deployment Snapshots.
Legacy Starter blocks remain for existing flows but no longer appear in new builds.