> For the complete documentation index, see [llms.txt](https://docs.patchmypc.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.patchmypc.com/patch-my-pc-publisher/manage/alerts-tab/webhooks-tab/send-webhook-reports.md).

# Send webhook reports in Patch My PC Publisher

*Applies to: Patch My PC Publisher V3.x*

When the **Send webhook reports** option on the **Webhooks** tab of Patch My PC (PMPC) Publisher is enabled, Publisher can send publishing alerts and reports to external messaging systems such as Microsoft Teams workflows and Slack. Webhooks provide near real-time visibility into publishing activity without relying on email notifications.

<figure><img src="https://3773699522-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MX7dvS0r_4fc0AikgJS%2Fuploads%2FTE68NWzqrtRkdwMo9s5h%2Fimage.png?alt=media&amp;token=3b3175d0-1f75-4a3a-a859-0eadcb7592c5" alt="&#x27;Send webhook reports&#x27; option" width="563"><figcaption></figcaption></figure>

Webhook notifications are commonly used to notify operations, security, or platform teams when publishing events occur.

When webhook notifications are enabled, the Publisher sends HTTP POST messages to the configured webhook endpoints based on publishing events and the selected notification level. Each configured webhook represents a single destination, such as a Teams channel or Slack workspace.

You can configure multiple webhook destinations, and you can independently enable, disable, test, or remove each webhook.


---

# 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.patchmypc.com/patch-my-pc-publisher/manage/alerts-tab/webhooks-tab/send-webhook-reports.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.