Scheduled Trigger

A scheduled trigger starts an automation on a clock — every 15 minutes, once an hour, daily at 9am, or on a cron expression — rather than in response to an external event. It's how you run recurring jobs: a nightly report, a morning digest email, a twice-daily sync between two databases, or a weekly cleanup. Why it matters: not everything is event-driven. Many workflows need to poll a source that has no webhook, or simply do something on a timetable. Practical note: scheduled triggers are the basis of polling — the platform wakes on schedule, checks "what's new since last time," and processes only new items, tracking a cursor so it doesn't reprocess old data. Be mindful of frequency versus cost and rate limits: checking every minute burns operations/tasks and can trip a downstream API's rate limit, while checking too rarely adds latency. Match the interval to how fresh the data really needs to be, and mind time zones and daylight saving when scheduling exact times.