> For the complete documentation index, see [llms.txt](https://docs.lithnet.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lithnet.io/autosync-for-mim/configuration/triggers.md).

# Triggers

Triggers provide a mechanism to tell AutoSync that a run profile must be scheduled for execution. Most commonly, triggers are used to tell AutoSync that a connected system has pending changes, and that it must perform a delta import.

AutoSync knows when a management agent requires a synchronization or has a pending export, as this information is available from the MIM sync service itself. However, the MIM sync engine doesn't know if a connected system has any pending changes in it. AutoSync triggers can be used to detect these changes and schedule a delta import in the sync service.

Triggers can also be used to tell AutoSync to execute any run profile outside of the standard *import, sync, export, confirming import* cycle. For example, triggers can be setup to perform maintenance operations such as a weekly full synchronization or daily full import.

AutoSync has out-of-box support for the following trigger types

| Type                                                                                                                               | Description                                                                                                                                                                                                     |
| ---------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [Active Directory change detection trigger](/autosync-for-mim/configuration/triggers/active-directory-change-detection-trigger.md) | Automatically detects changes in AD DS or AD LDS and triggers a delta import                                                                                                                                    |
| [MIM service change detection trigger](/autosync-for-mim/configuration/triggers/mim-service-change-detection-trigger.md)           | Automatically detects changes in the MIM service and triggers a delta import                                                                                                                                    |
| [Repeating interval trigger](/autosync-for-mim/configuration/triggers/repeating-interval-trigger.md)                               | Executes a run profile at a repeating interval                                                                                                                                                                  |
| [Scheduled interval trigger](/autosync-for-mim/configuration/triggers/scheduled-interval-trigger.md)                               | Executes a run profile at a specific time                                                                                                                                                                       |
| [Powershell script trigger](/autosync-for-mim/configuration/triggers/powershell-script-trigger-gallery.md)                         | Uses a custom PowerShell script to determine a run profile to execute. See the [Powershell script trigger gallery](/autosync-for-mim/configuration/triggers/powershell-script-trigger-gallery.md) for examples. |


---

# 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://docs.lithnet.io/autosync-for-mim/configuration/triggers.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.