> 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.md).

# How to use Webhooks

Webhooks can help setting up interaction to notify based on changes in PIM.

## What is a webhook?

Struct PIMs [webhook](broken://pages/WHeW9vpHXc50IdlDXSks) engine is a powerful feature that allows you to set up interactions between PIM and external endpoints based on specific events. A webhook consists of configurations and events.

* [Configurations](/reference/settings/integration/webhooks/webhook-details.md) include the title of your webhook, the URL you want the webhook to call, and options for activating the webhook, as well as custom headers. 
* [Events](/reference/settings/integration/webhooks/webhook-details.md) define when the webshook should be triggered. 

Webhooks can be found by navigating to integration under "settings" and clicking on Webhooks.

## Guides covering Webhooks

* [How to set up and edit a webhook](/tutorials/guides/how-to-use-webhooks/how-to-set-up-and-edit-a-webhook.md)
* [How to add custom request headers to a webhook](/tutorials/guides/how-to-use-webhooks/how-to-add-custom-request-headers-to-a-webhook.md)
* [How to set conditional triggering on update-webhooks](/tutorials/guides/how-to-use-webhooks/how-to-set-up-conditional-triggering-on-update-webhooks.md)
* [How to get a detailed change request on update-webhooks](/tutorials/guides/how-to-use-webhooks/how-to-get-a-detailed-change-request-on-update-webhooks.md)
* [How to view webhook request history](/tutorials/guides/how-to-use-webhooks/how-to-view-webhook-request-history.md)
* [How to digest webhook requests](/tutorials/guides/how-to-use-webhooks/how-to-digest-webhook-requests.md)


---

# 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.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.