Goal
This page explains the three trigger patterns in Sanka workflows—event, time, and manual—so you can choose the right one for each automation.Related pages
What is a trigger?
A trigger is what starts a workflow run. Choose based on how you want the workflow to begin:| Type | Best for | Example |
|---|---|---|
| Event trigger | Reacting to record changes | When an order status is confirmed, allocate inventory |
| Time trigger | Running on a schedule | Every morning at 9:00, notify about overdue tasks |
| Manual trigger | Running only when needed | Run a month-end batch once |
Event trigger
Use when you want automation to run right after a record is created or updated. Add conditions to limit runs to only the cases you care about (for example, “status = confirmed”).Time trigger
Use when you want the workflow to run on a schedule (daily/weekly/monthly). Confirm your workspace time zone and filter the target records to avoid unnecessary work.Manual trigger
Use when a person should decide when to run the workflow (spot checks, exceptions, or initial verification). Define who is allowed to run it to prevent unintended executions.Operational tips
- Start with strict conditions and expand after verifying results.
- Prevent duplicate processing by designing “run once” rules (conditions/status updates).
- After running, review workflow history and the affected records to confirm expected behavior.