A scheduled trigger is the part of an automation that starts a workflow based on time. Instead of waiting for an event, it watches the clock and fires at the moments you define: every 15 minutes, every night, every first of the month. When the time arrives, the rest of the workflow runs.
It works like an alarm clock for your software. You set the time once and it goes off on its own, again and again, whether or not anything else is happening. This is what makes it different from a polling trigger, which keeps checking another system for changes; a scheduled trigger only cares about the clock. It is the most common kind of trigger for routine, predictable work.
Under the hood, a scheduled trigger often maps to a cron-style schedule, the same timing rules behind a classic cron job. You might use one to fetch fresh exchange rates each morning, send a weekly summary, or clear out stale records overnight. The work is identical each time; only the moment changes.
The thing to plan for is what happens when a run is slow or fails. If the trigger fires hourly but a run takes 70 minutes, do you skip, queue or overlap? And a fixed clock means it does not react to demand: pick an interval too long and data goes stale, too short and you waste runs on nothing new. Choosing the right cadence is most of the work. Once the timing is set, the scheduled job it starts does the rest.
At TopDevs we lean on scheduled triggers for the steady drumbeat tasks a client depends on, and we keep the timing visible so it is obvious when each one is meant to run.
