> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tela.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Creating a schedule

> Fill in the New schedule form: destination, frequency, time zone, visibility and the inputs of each run

Before you start, publish the Canvas, Workflow or Agent you want to run. Schedules only run published versions, as explained in the [overview](https://docs.tela.com/en/schedules/overview.md#what-runs).

## Create it

**1. Open the form**

Go to **Schedules** in the left sidebar and click **New schedule**. You can also open the `…` menu of a Canvas, Workflow or Agent and choose **Schedule**, which fills the destination for you.

**2. Name it**

Under **Name**, say what runs and when, for example *Contract routing, every Monday at 9am*. The name is what you read in the list, so make it specific.

**3. Choose what to execute**

Under **What to execute**, type the name of the destination or paste its ID. The list shows the kind (Canvas, Workflow or Agent) and the Project. Only published destinations you have access to appear. When you choose another destination after filling the inputs, the inputs are cleared.

**4. Set when to execute**

Pick a frequency, a time and a **Time zone**. The form shows the next time it will run, for example *Next: Nov 2, 2026, 9:00*, so you can check it before saving.

**5. Choose who can see it**

Under **Who can see this schedule**, keep **Entire workspace** or pick one of your teams. See [Who can see it](#who-can-see-it).

**6. Fill in the inputs**

The **Inputs** section lists the variables of the published version. Fill in the required ones, then click **Create schedule**.

![New schedule dialog with name, Contract routing as the destination, Weekly on Monday at 09:00, time zone and the Inputs section](https://mintcdn.com/meistrari/M2w7BduKZAFA1Sbx/images/schedules/new-dialog.png?fit=max\&auto=format\&n=M2w7BduKZAFA1Sbx\&q=85\&s=f5529cc570e368078729f7e5ff91d459)

## Frequencies

| Option | Runs | Details |
| - | - | - |
| **Every day** | Once a day at the time you set | |
| **Weekdays** | Monday to Friday at the time you set | |
| **Weekly** | Once a week on the day you choose | |
| **Monthly** | Once a month on the day you choose | Months without that day are skipped. Day 31 does not run in April. |
| **Every X minutes** | Every X minutes | Use a divisor of 60 (1, 2, 3, 4, 5, 6, 10, 12, 15, 20, 30) so runs stay evenly spaced. |
| **Every hour** | Once an hour at the minute you set | Minute from 0 to 59. |
| **Once** | One time on a date and time | The date must be in the future. When it has run, the schedule becomes **Ended** and read-only. |
| **Custom cron** | Whatever the expression says | Five fields: minute, hour, day of the month, month, day of the week. |

For custom cron, a few common forms:

| Expression | Meaning |
| - | - |
| `0 9 * * 1` | Every Monday at 09:00 |
| `30 8 * * 1-5` | Weekdays at 08:30 |
| `*/15 * * * *` | Every 15 minutes |
| `0 7 1 * *` | The 1st of every month at 07:00 |

## Time zone

Times are always in the time zone you pick in the **Time zone** field. A schedule at 09:00 in `America/Sao_Paulo` runs at 09:00 there, whatever the time zone of whoever created it.

Daylight saving time can make a time not exist or happen twice. The form refuses those times and asks you to choose another one.

## Inputs

Every run of a schedule uses the same input values you saved. The inputs behave like the ones in the Craft experience:

* Text variables take the text you type, and can also carry files in a Canvas or Workflow.
* File variables take the files you drop on the field. Agents take one file per variable.
* A required input must be filled before **Create schedule** is enabled.

> [!NOTE]
>
> The values are checked against the published version when you save and again when each run starts. If you publish a version that renames or removes a variable, the next run can fail to start. See [what to do when a run fails](https://docs.tela.com/en/schedules/managing-schedules.md#when-a-run-fails).

## Who can see it

* **Entire workspace**: everyone in the Workspace sees the schedule.
* **A team**: only members of that team see it.

When the destination Project is restricted to a team, the schedule keeps that restriction and you cannot widen it. If you belong to more than one team that can reach the Project, the form asks you to choose the owning team.

## API

The public API reference does not cover schedules yet, so create and manage them from the Schedules page.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.