> 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.&#x20;

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:

<figure><img src="https://529897662-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LtPTgZOYmpJka4jqs1v-3406065915%2Fuploads%2FLJfmrGUB3kSi0hpTiryY%2Fimage.png?alt=media&amp;token=8d0ebc9a-c965-490e-ad83-bb3bd91c1df9" alt=""><figcaption></figcaption></figure>

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&#x20;

### 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.novacuraflow.com/development/integration-engine/get-started/create-an-integration/schedule-trigger.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
