How can we help?

The main difference is what causes the automation to begin. A scheduled automation runs according to a defined time or recurring interval. An event-triggered automation begins when a supported event occurs and the configured triggering conditions are satisfied. When should I use scheduled automation? Scheduled automation is appropriate when work needs to happen at predictable intervals. Examples include recurring business reviews, scheduled reporting, periodic operational checks, and regular internal workflows. When should I use event-triggered automation? Event-triggered automation is useful when the business needs to respond to something that happens rather than wait for a scheduled time. For example, a supported external system may send a webhook that initiates a configured workflow. The exact behavior depends on the available integrations, supported events, and automation configuration. Can both types use AI Employees? Yes. Both approaches can use Polyosync's automation engine and its configured AI Employee capabilities. Can both include conditions and multiple steps? Yes. Automations can contain conditional logic, AI-assisted steps, delegation, supported tools, and configured actions. The trigger determines when execution begins; the automation definition determines what happens afterward. Which approach is better for my business? Choose scheduled automation when the activity is recurring and time-based. Choose event-triggered automation when the activity should respond to a specific supported business event. Some organizations need both. Polyosync supports multiple triggering approaches so businesses can coordinate predictable recurring work alongside activities that respond to changing operational circumstances.