Skip to main content
  • Triggers are available for Workflow applications only.
  • Each workflow can have at most one schedule trigger.
Schedule triggers enable your workflow to run at specified times or intervals. They are ideal for recurring tasks like generating daily reports or sending scheduled notifications.

Add a Schedule Trigger

On the workflow canvas, right-click and select Add Node > Start > Schedule Trigger.

Configure a Schedule Trigger

You can configure the schedule using either the default visual picker or a cron expression. After configuration, you can see the next 5 scheduled execution times.
Schedule triggers do not produce output variables, but they update the system variable sys.timestamp (the start time of each workflow execution) each time they initiate the workflow.

With the Visual Picker

Use this for simple hourly, daily, weekly, or monthly schedules. For weekly and monthly frequencies, you can select multiple days or dates.

With a Cron Expression

Use this for more complex and precise timing patterns, such as every 15 minutes from 9 AM to 5 PM on weekdays.
You can use LLMs to generate cron expressions.

Standard Format

A cron expression is a string that defines the schedule for executing your workflow. It consists of five fields separated by spaces, each representing a different time unit.
Ensure that there is a single space between each field.
When both the day-of-month and day-of-week fields are specified, the trigger activates on dates that match either field.For example, 1 2 3 4 4 will trigger your workflow on the 3rd of April and every Thursday in April, not just on Thursdays that fall on the 3rd.

Special Characters

Predefined Expressions

  • @yearly: Run once a year at 12 AM on January 1.
  • @monthly: Run once a month at 12 AM on the first day of the month.
  • @weekly: Run once a week at 12 AM on Sunday.
  • @daily: Run once a day at 12 AM.
  • @hourly: Run at the beginning of every hour.

Examples

Test a Schedule Trigger

  • Run this step: The schedule trigger runs immediately, ignoring the configured schedule.
  • Test Run: The schedule trigger waits for its next scheduled execution time.
Last modified on July 14, 2026