Timer Trigger

Use the Timer Trigger as a process starter when creating flows designed to be activated without external input. It is useful when you want your flow to run at certain time intervals. You can also configure the Timer Trigger to activate the flow multiple times at a specified interval or to set a Cron Job.

Trigger Settings

Field Description
Handler Settings
Scheduler Options
  • Timer: Runs the flow at the specified time or interval
  • Cron Job: Provides more customization options for scheduling the runs
Additional information about fields available when you select the scheduler option as Timer
Start Time

Use the calendar to set start date and time. When configuring an app property for the Start Time, use the RFC 3339 date and time formats.

Format with UTC offset:

YYYY-MM-DDTHH:MM:SS+00:00

OR

Format without UTC offset:

YYYY-MM-DDTHH:MM:SSZ

Here,

T is used as a separator between date (YYYY-MM-DD) and time (HH:MM:SS). Replace it with a space, if needed.

  • 2021-04-12T23:20:50.52+00:00

  • 2021-11-22T09:16:47Z

  • 1996-12-19T16:39:57-08:00

  • 1990-12-31 23:59:60+05:00
Note: Start Time by Default is Blank. If there is no date and time mentioned, the flow runs as soon as you push the changes or app binary.
  Use these fields in combination to define the schedule for recurring runs.
Repeating When Repeating is enabled, the flow is triggered at the same time as the first run at the specified time interval. (Default: False)

Delayed Start

Delayed Start delays only the first execution. The successive runs are triggered at the specified time interval. (Default: False)
Time Interval This is a period between two successive runs.

Interval Unit

This is a unit specified for Time Interval.
Additional information about fields available when you select the scheduler option as Cron Job
Cron Expression

You can enter any Cron Expression manually in this field.

The standard cron expression should be CRON_TZ=IANA TimeZone * * * * *

Here,

CRON_TZ=IANA TimeZone is used to set the specific time zone in which the cron job is run.

* * * * *
Minutes Hours Day of Month Months Day of Week

Here are some examples for you.

Cron expression Schedule
* * * * * Every minute
0 * * * * Every hour
0 0 * * * Every day at 12:00 AM
0 0 * * 4

At 12:00 AM, only on Friday

Here, number 0-6 stands for the days of the week starting with Sunday as 0.
0 0 1 * * At 12:00 AM, on day 1 of the month
Note:

  • Standard cron expressions can be built manually, however, the cron expression does not support (L) and hash (#)

  • After building the cron expression manually, switching to cron expression builder resets the cron expression values to default.
Cron Expression Builder

If you use the Cron Expression Builder, this field is auto-populated as you build the expression.

Simple cron expressions can be built using the Cron Expression Builder. You can use the different tabs to define the frequency: Minutes, Hours, Day of Week, Day of Month, Months.

Note:
  • Expressions built using Cron Expression Builder can be modified manually.
  • If there is no time zone mentioned while building a cron expression through app property, by default the time zone of the system is considered and there might be no logs generated for the executed flow.
  • UI validation for the built cron expression is not supported.

Map to Flow Inputs

Use this tab to map the trigger output to the flow input.