# Schedule

> Run an automation on a recurring clock with the Schedule trigger: every 5 to 30 minutes, hourly, daily, weekly, or monthly, in the time zone you choose.

- Source: https://www.taskade.com/learn/automation/schedule
- Section: Automation
- Updated: 2026-11-09
- Index of all pages: https://www.taskade.com/learn/llms.txt

## Overview

The **Schedule** trigger runs an automation on a clock you set: every 5 to 30 minutes, hourly, daily, weekly, monthly, or on a custom schedule that you write. Use it for daily reminders, weekly reports, and monthly maintenance. Pair Schedule with [Find Tasks](https://www.taskade.com/learn/automation/find-tasks) and an [Ask an agent](https://www.taskade.com/learn/automation/agent-action) step to build recurring digests, weekly status reports, or daily AI standups.

> **TL;DR:** The Schedule trigger starts an automation on a recurring clock, with no button to press. Pick every 5 to 30 minutes, hourly, daily, weekly, monthly, or a custom schedule. Each run can start up to 30 minutes after the set time. Build [recurring digests, reports, and maintenance runs](https://www.taskade.com/learn/automation/find-tasks) from it.

```mermaid
flowchart LR
  A[Clock hits<br/>set time] --> B[Schedule<br/>trigger fires]
  B --> C[Automation<br/>runs steps]
  C --> D[Actions<br/>execute]
  style A fill:#0d1b2a,color:#7dd3fc,stroke:#38bdf8,stroke-width:1.5px
  style B fill:#2a1225,color:#ff8fa3,stroke:#ff2d60,stroke-width:2px
  style C fill:#2a1225,color:#ff8fa3,stroke:#ff2d60,stroke-width:2px
  style D fill:#0d1a0e,color:#86efac,stroke:#22c55e,stroke-width:1.5px
```
## Pick Your Interval

Choose one of six schedule triggers when you add the trigger.

| Interval | What you set | Notes |
| --- | --- | --- |
| **Every X Minutes** | 5, 10, 15, or 30 minutes | For time-sensitive checks. Needs a paid plan. |
| **Every Hour** | Nothing to set. It runs on the hour | Runs once an hour, around the clock. |
| **Every Day** | Time and time zone | The everyday choice for morning digests. |
| **Every Week** | One or more days, plus time and time zone | Pick Monday and Thursday, or only Friday. Use **Repeat** to run every week, or every 2, 3, or 4 weeks. |
| **Every Month** | Day of the month, plus time and time zone | For billing cycles and monthly reports. |
| **Custom schedule** | A **Cron Expression** with five fields (minute, hour, day of the month, month, day of the week), plus time zone | For a pattern that the other options cannot set, for example `30 8 * * 1-5` for weekdays at 8:30. A schedule that runs more than once an hour needs a paid plan. The shortest gap is 5 minutes. |

A **Repeat** cycle of 2, 3, or 4 weeks counts weeks from a fixed calendar week, so the first run can be up to that many weeks away. Leave **Repeat** empty to run every week.

**Every Day**, **Every Week**, **Every Month**, and **Custom schedule** each let you pick a time zone, so a 9:00 AM digest lands at 9:00 AM where your team is. **Every Hour** and **Every X Minutes** repeat on a fixed cycle instead, so a time zone does not change anything.

## Know What to Expect Once It Runs

Taskade spreads scheduled runs across a window after the time you set, so that thousands of automations do not all start in the same second. Each run can start at any moment inside that window, so do not count on the exact second.

| Interval | Each run can start up to |
| --- | --- |
| **Every Hour**, **Every Day**, **Every Week**, **Every Month** | 30 minutes after the time you set |
| **Every 30 Minutes** | 10 minutes after |
| **Every 15 Minutes** | 7 minutes after |
| **Every 10 Minutes** | 5 minutes after |
| **Every 5 Minutes** | 2 minutes after |
| **Custom schedule** | 30 minutes after, if it runs once an hour or less often. Half the gap between runs, up to 10 minutes, if it runs more often. |

For a daily 9:00 AM report, that means the run can start at any moment from 9:00 to 9:30.

Plan around that in two places. Do not chain a scheduled automation to something that must happen at an exact clock time, such as a live event start. And when two automations must run in order, have the first one trigger the second rather than scheduling them a minute apart.

The window applies from the moment you turn a schedule on, so it also settles after you pause and re-enable an automation.

## Use Cases

Not sure how to use the Schedule trigger? Start with the ideas below.

---

### Send Reminders

- **Scenario**: A manager wants to send the entire team a collective summary of all tasks for the day from their private tracker project every morning.
- **Steps**:

  - **Schedule Trigger**: Set the automation to run daily at 9:00 AM.
  - **Find Task(s)**: Search for and retrieve all tasks added by the manager to their private tracker project (for example, "Daily Priorities").
  - **Transform Array into String**: Format the list of tasks for further processing.
  - **Run an agent command**: Use a **Content Summarization Agent** to structure the tasks into a professional email format with clear headings and bullet points.
  - **Send Email**: Send the structured summary to all team members, including stakeholders (via CC) if necessary.
  - **Send Channel Message**: Post the task summary to a shared Slack channel.

---

### Distribute Reports

- **Scenario**: A manager wants to generate and distribute a report summarizing project progress every Friday afternoon.
- **Steps**:

  - **Schedule Trigger:** Set the automation to run weekly on Fridays at 4:00 PM.
  - **Run an agent command**: Use a **Progress Report Agent** trained on a team-wide tracker project to compile a weekly summary of tasks.
  - **Send Email**: Distribute the report to stakeholders by email.

---

### Automate Maintenance

- **Scenario**: An IT department needs to schedule recurring system checks and assign tasks to team members for server maintenance.
- **Steps**:

  - **Schedule Trigger**: Set the automation to run monthly on a specific day.
  - **Create Project From Template**: Automatically create a new project from a predefined maintenance checklist template.
  - **Send Email**: Notify responsible team members with details.
  - **Send Channel Message**: Post a notification in the team's Slack channel.

## Related guides

- [Run Once or Recurring](https://www.taskade.com/learn/automation/run-once-or-recurring). Decide between a one-off run and a standing schedule.
- [Delay Action](https://www.taskade.com/learn/automation/delay-action). Pause mid-run instead of adding a second schedule.
- [Manual Trigger](https://www.taskade.com/learn/automation/manual-trigger). Run on demand instead of on a schedule.
- [Find Tasks](https://www.taskade.com/learn/automation/find-tasks). Collect items for scheduled digests.
- [Agent Action](https://www.taskade.com/learn/automation/agent-action). Run an agent on a schedule.
- [Loop Action](https://www.taskade.com/learn/automation/loop-action). Process each item in a scheduled batch.
- [Automation Triggers](https://www.taskade.com/learn/automation/triggers). Compare Schedule with every other way to start an automation.
