> For the complete documentation index, see [llms.txt](https://help.novacuraflow.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.novacuraflow.com/development/integration-engine/get-started/create-an-integration/schedule-trigger.md).
# Schedule trigger
Use schedule trigger type for integrations that should be triggered to run on a repeating interval, say once a day, or hourly etc.
Example use case:
* data synchronizations between data sources
* polling for data in some data source
When setting up a webhook trigger for your integration you start with the following page:
You can specify
Active From: the date and point in time from when the schedule should be active. This will also configure the time of day and minute of hour the integration will be triggered.
Interval: any combination of days, hours, minutes and seconds by which interval the integration will be triggered.
Some common example patterns are:
Active From 1/1/2024 1:00 AM
Days: 1, Hours: 0, Minutes: 0, Seconds: 0 - to run something daily at 1:00 AM
Active From 1/1/2024 1:00 AM
Days: 0, Hours: 1, Minutes: 0, Seconds: 0 - to run something hourly - on the hour
### Ordered Delivery
Now select whether you want the webhook trigger to have so called Ordered Delivery or not. Ordered delivery for scheduled integrations means that no new trigger will occur as long as the previous one is still executing.
Workflow Input
Specify the message that the machine workflow of the integration expects on start, if any.
---
# 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://help.novacuraflow.com/development/integration-engine/get-started/create-an-integration/schedule-trigger.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.