| Trigger | How it starts | Owner dependency |
|---|---|---|
| Manual | A workspace member starts a test or run from the interface. | Queue worker for background execution. |
| Webhook | An external system posts to a flow-specific public endpoint. | HTTPS, public routing, queue worker. |
| Schedule | The configured schedule becomes due. | Minute-level Laravel scheduler and correct timezone. |
| Gmail / Outlook | Polling detects a matching email. | Scheduler, global OAuth app, valid workspace connection. |
| Calendly | A signed provider webhook is received. | Global OAuth/webhook configuration and public HTTPS callback. |
| Telegram | A Telegram bot webhook receives a message. | Workspace bot connection and public HTTPS callback. |
Only an active trigger attached to a published flow can start a production run. Use request IDs on external webhooks to trace or de-duplicate upstream events.