Schedules

A schedule starts a run on a time you choose. It is one kind of trigger, and a workflow can have a schedule alongside webhooks.

Reading time

Pick how the schedule reads time, then fill in its fields:

• Date — once, at a moment.
• Interval — every so often, measured from the previous run.
• Cron — on calendar times, such as weekdays at nine.

Times are read in the timezone you choose, and every saved schedule records which one that was — so a schedule means the same thing wherever it runs.

Pausing and resuming

Each workflow’s Triggers view lists the schedules and webhooks you created for it, and lets you pause or resume each one. A paused schedule keeps its configuration but stops starting runs until you resume it.

Run settings

A schedule carries its own variables and input, stored on that schedule. See Triggers for how those layer over the workflow’s own.

No minimum gap

There is no cooldown between runs and no minimum interval to wait out: a schedule fires as often as you configure it. Each run costs only its own running time — see what a run costs.