Overview
Core ways to start Mandala workflows
Current Triggers
Every new workflow starts with a Start block, which unifies manual runs, API calls, and deployed chat into one entry point. Schedule and Webhook are separate, standalone triggers you add when you need them.
Start
Unified entry point for manual runs, API calls, and deployed chat -- the default for new workflows
Schedule
Cron or interval based execution
Webhook
Receive external webhook payloads, including 30+ built-in provider integrations
Legacy triggers. Earlier versions of Mandala used three separate blocks for what Start now handles in one: API, Manual, and Input Form. Those blocks still work in existing workflows, but are no longer offered when building a new one -- use Start instead. The oldest Starter block follows the same pattern.
Quick Comparison
| Trigger | Start condition |
|---|---|
| Start | Manual run, API call, or deployed chat message |
| Schedule | Timer managed in schedule modal |
| Webhook | On inbound HTTP request |
Using Triggers
- A new workflow already has a Start block -- configure custom input fields if you need structured data beyond plain text.
- Add a Schedule or Webhook trigger alongside it if the workflow also needs to run on a timer or in response to an external event -- both can coexist with Start.
- Connect trigger outputs to the rest of the workflow.
Manual runs from the editor's Run button execute your draft canvas. API calls, chat, scheduled runs, and webhooks all execute the workflow's most recently deployed snapshot instead. Redeploy after canvas changes you want those entry points to see.