Create and manage time-based service triggers for workflow automation.

Schedules are used to automate services and run them at set times. Common use cases are running batch and recurring jobs such as synchronizing data with an external system, polling for changes, and sending notifications.

When triggered, the schedule will send a request to the specified service endpoint. The result of the request (success or failure) is recorded in the schedule logs.


Any task that needs to be run on a regular schedule is a candidate for a schedule.

  • Fetch data from an external API every 15 minutes to populate a dashboard.

  • Synchronize customer data with your CRM nightly at 2am.

  • Refresh an OAuth access token used for integrations every 3 hours.

  • Send an email every morning with a summary of all orders from the previous day.


  • Ensure that the selected service account has permission to run the selected service and the necessary object class permissions. If you are updating a secret within the service, that permission must be granted.

  • After you have enabled a service you will need to disable it to make changes. Don't forget to enable it again when you're done!





A longer description of the schedule. It may be useful to specify what happens in the service being triggered and when the schedule runs.



Service account

Cron expression

Time Zone

The time zone used by the schedule when evaluating the cron expression.

Override Service Time Zone

If this is enabled, the time zone specified above will override the time zone specified on the service.

Restrict to Selected Environments


Activate the schedule. This must be checked for the schedule to run.

Cron expression

A cron expression typically consists of five values separated by spaces, in this order, within the stated ranges.

  • Minute (0–59)

  • Hour (0–23)

  • Day of month (1–31)

  • Month (1–12)

  • Day of week (0–6, where 0 = Sunday)

The following example would be run every 3rd hour, on the hour: 0 */3 * * *.

Schedules also support second granularity (0–59). This can be added as the first value in the expression if required.

Available patterns



any value



list of values



range of values





Good to know

  • Hover over the blue dot to see a written description of the current cron expression.

  • Use crontab guru to help you generate a valid expression and to find common examples.

Last updated