> For the complete documentation index, see [llms.txt](https://docs.flexy.bot/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flexy.bot/modules/core/triggers/schedule.md).

# Schedule

**Introduction**

Automate tasks on a recurring basis using the "Schedule" trigger in FlexyBot. Suitable for tasks that need to run hourly, daily, or on a custom schedule.

{% embed url="<https://youtu.be/KEBME1GlJkA>" %}
Using the "Schedule" trigger to send a message every hour
{% endembed %}

**Configuration**

* **Mode**: Determines the scheduling mode for the trigger. This parameter is required and can be set to either `Recurring` or `Delayed`.
* **Recurring**: Executes the automation repeatedly according to a specified schedule.
  * **Expression**: A CRON expression that defines the recurring schedule. This field is required. You can use our AI builder or online tools like [FreeFormatter's CRON Expression Generator](https://www.freeformatter.com/cron-expression-generator-quartz.html) to create your expression.
  * **Time Zone**: The time zone in which the CRON expression will be evaluated. This is necessary to ensure the schedule aligns with the desired time zone.
* **Delayed**: Executes the automation at a specific future date and time.
  * **Date**: The exact date and time when the automation should run. This field is required.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.flexy.bot/modules/core/triggers/schedule.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.