Overview
Core ways to start TradingGoose workflows
Core Triggers
A workflow can have multiple trigger entry points. API, Chat, Input Form, and Manual are limited to one block of each type per workflow; this is not a one-trigger-total restriction. Choose the entry point for editor runs.
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
- Add the trigger block to the canvas.
- Configure any required schema or auth.
- Connect the block to the rest of the workflow.
Editor runs execute the current saved workflow. External API, published Chat, schedule, and webhook runs use the deployed snapshot. A child workflow inherits its parent's live/deployed target. Redeploy after changes that should reach external entry points. See Execution → Deployment Snapshots.