> For the complete documentation index, see [llms.txt](https://docs.hexabot.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hexabot.ai/workflow-editor/workflow-types/scheduled-workflows-for-recurring-automation.md).
# Scheduled Workflows for Recurring Automation
A **Scheduled** workflow runs automatically on a recurring schedule. Use scheduled workflow automation for recurring background tasks, such as report generation, data synchronization, content processing, and routine maintenance.
When creating a workflow, select **Scheduled** under **Type**.
### Configure automated workflow schedules
Use the **Schedule** section to configure when and how often the workflow runs.
Hexabot supports the following scheduled workflow frequencies:
| Frequency | Configuration |
| ---------- | --------------------------------------------------------- |
| **Second** | Run every specified number of seconds. |
| **Minute** | Run every specified number of minutes. |
| **Hour** | Run every specified number of hours at a selected minute. |
| **Day** | Run every day at a selected time. |
| **Week** | Run every week on a selected day and time. |
| **Month** | Run every month on a selected day and time. |
The schedule fields change with the selected frequency.
For example:
* **Every 15 minutes**
* **Every 2 hours at minute 30**
* **Every day at 08:00**
* **Every week on Monday at 09:00**
* **Every month on day 1 at 00:00**
For second-, minute-, and hour-based schedules, select an execution interval. For example, run a workflow every 5 minutes instead of every minute.
> For monthly schedules configured on the 29th, 30th, or 31st, the workflow only runs during months that contain the selected date.
The schedule is required. After configuring it, enter the workflow **Name**, optionally provide a **Description**, and click **Submit** to create the scheduled automation.
### Scheduled workflow input schema
The Scheduled workflow input schema is system-defined and cannot be edited.
Every scheduled execution receives the following input properties:
| Property | Type | Description |
| -------------- | -------- | ---------------------------------------------------------- |
| `schedule` | `string` | The schedule expression that triggered the workflow run. |
| `triggered_at` | `string` | The date and time at which the workflow run was triggered. |
These values provide execution context that can be used by the workflow steps.
Because the schema is read-only, you cannot add, remove, or modify its properties from the workflow form.
> Only Manual workflows support user-defined input schemas. Scheduled workflows always use the system-defined `schedule` and `triggered_at` properties.
The scheduled input object does not accept arbitrary top-level fields. Use `$input.schedule` and `$input.triggered_at` when a step needs to know why or when the run started.
---
# 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.hexabot.ai/workflow-editor/workflow-types/scheduled-workflows-for-recurring-automation.md?ask=&goal=
```
`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.