> For the complete documentation index, see [llms.txt](https://docs.struct.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.struct.com/tutorials/guides/how-to-use-webhooks/how-to-set-up-conditional-triggering-on-update-webhooks.md). # How to set up conditional triggering on update-webhooks A guide on how to set up conditional triggers on update-webhooks ## Why use conditional triggering After having configured the webhook, you can select different events based on when you want notifications to be sent. However, for some update events—like Assets—you may see an “Advanced settings” option to the left of the slider. Inside “Advanced settings” you can set conditional triggers, which means the webhook request will only be sent if certain conditions are met. This helps you avoid unnecessary notifications and only get alerts that matter.

Webhook configurations page, events section

## **Conditional triggering disabled** When conditional triggering is disabled, all events of the selected type will trigger webhook notifications without any filtering. ## **Conditional triggering enabled** When conditional triggering is enabled, you can choose specific types of changes on the entity that will trigger the webhook event. This way only relevant updates send notifications based on the selected conditions. The available conditions will vary depending on which update-events you want to enable conditional triggering for.

--- # 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.struct.com/tutorials/guides/how-to-use-webhooks/how-to-set-up-conditional-triggering-on-update-webhooks.md?ask=&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.