Skip to content
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Scheduled Execution

Start a workflow automatically at chosen times. Use it for recurring work that does not need a person to submit an input for each run.

Before you start

You need permission to configure and publish the workflow. Its connections and required resources must be available for unattended execution.

Schedule a workflow

  1. Add the Scheduled Execution trigger and connect it to the steps that should run.

  2. Choose Frequency, the relevant day fields, Time(s), and Timezone. Check that the workflow has the information it needs without a chat message.

  3. Publish the workflow to activate the trigger. If your organization requires release approval, complete that process.

  4. After the scheduled time, inspect run history and verify the output or destination.

Result: The active schedule starts the published workflow at the configured times.

Behavior and troubleshooting

Saving a configuration alone does not activate the schedule. Multiple times must use the same minute value. Days 29, 30, and 31 are skipped in months that lack the selected date. Check timezone and calendar behavior before scheduling time-sensitive work. See Schedules, Time Zones, and Calendar Edge Cases.

Configuration

Parameter
Type
Description

Frequency *

dropdown (string)

How often the scheduled execution should run. Choose one of: Every day, Every week, Every month, Custom. Default: every_day.

Day of the week

dropdown (string)

Day of the week when the scheduled execution should run (for weekly frequency). Choose one of: Monday, Tuesday, Wednesday, Thursday, Friday, Saturday, Sunday. Only shown when Frequency is Every week.

Days of the week

multi-select (string)

Days of the week when the scheduled execution should run (for custom frequency). Choose any of: Monday, Tuesday, Wednesday, Thursday, Friday, Saturday, Sunday. Only shown when Frequency is Custom.

Day of the month

dropdown (string)

Day of the month when the scheduled execution should run (for monthly frequency). Days 29, 30, and 31 are skipped in months that don't have those days. Choose one of: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31. Only shown when Frequency is Every month.

Time(s) *

array

Times of the day when the scheduled execution should run (format: HH:MM, e.g., 8:00, 12:00). You can add multiple times, but all times must have the same minute value (e.g., 8:00, 12:00, 15:00 - all at :00). Default: ['9:00'].

Timezone *

dropdown (string)

Timezone for the scheduled execution. Choose one of: PACIFIC TIME, MOUNTAIN TIME, CENTRAL TIME, EASTERN TIME, ATLANTIC TIME, UTC, LONDON, PARIS, BERLIN, MOSCOW, DUBAI, INDIA, SINGAPORE, TOKYO, SYDNEY, AUCKLAND. Default: UTC.

Trigger Activation and Execution Context

Was this helpful?