Schedule any workflow
at the right time, every time

Start with the visual builder it covers most scheduling needs through day pickers, time pickers, and frequency dropdowns anyone on the team can use. Switch to the advanced editor only when the visual builder cannot express the pattern such as every fifteen minutes during business hours, the last Friday of every quarter, or skipping specific days. Both editors stay in sync, so a schedule built in one view can be read in the other.

Every schedule has an explicit timezone you pick from a list of city or region names Berlin, New York, Tokyo, Sao Paulo. The platform respects the rules of that region, including automatic daylight saving transitions. A schedule for nine in the morning Berlin time runs at nine all year round, regardless of daylight saving. The team never has to adjust schedules twice a year.

Presets cover the patterns that make up most scheduling needs every minute, every five minutes, every fifteen minutes, hourly, daily at a specific time, weekdays only, weekly on specific days, every two weeks, monthly on a specific date, monthly on a specific weekday occurrence (first Monday, last Friday), quarterly, and yearly. Each preset is one click to apply and one adjustment to tune.

A one time schedule fires the workflow exactly once at a specific date and time in your timezone, then becomes inactive. The workflow stays in the library with its full configuration, so the next time you need a similar one off job you can duplicate, change the date, and run again. Common uses include data exports for upcoming meetings, cleanup runs before product launches, and migration jobs.

The preview shows the next five fire times in plain English with full date, day of the week, time, and timezone. For example, Monday, 12 May 2026 at 09:00 Berlin time rather than a raw timestamp. The preview updates in real time as you adjust the schedule, so you can iterate quickly and confirm before saving.

Each workflow can catch up on missed runs after downtime or skip them and continue from the next scheduled time. Catch up is right when every run matters billing reconciliations, hourly data syncs. Skip is right when stale runs are not useful a daily digest that does not need to fire at noon. The choice sits in the schedule configuration alongside timezone and frequency.