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

# Configure a Webhook in Patch My PC Publisher

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

The **All Notifications** section on the **Webhooks** tab of Patch My PC (PMPC) Publisher allows you to perform the following actions on webhooks:

* [Test](#test-button)
* [Copy](#copy-button)
* [Advanced](#advanced-button)
* [Remove](#remove-button)

<figure><img src="https://3773699522-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MX7dvS0r_4fc0AikgJS%2Fuploads%2Fy01PL0V75uWTzkB65DoJ%2Fimage.png?alt=media&amp;token=1bf2c3ca-d837-492b-8e7a-0178b5d45844" alt="&#x27;All Notifications&#x27; section" width="528"><figcaption></figcaption></figure>

## Test button

Clicking **Test** sends a test notification for the selected webhook to the configured destination, so you know the webhook has been configured correctly and is working.

### To test a webhook

1. Load Publisher.
2. Navigate to **Alerts | Webhooks**.
3. Click the webhook you want to test, then click **Test**.

<figure><img src="https://3773699522-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MX7dvS0r_4fc0AikgJS%2Fuploads%2FtmogGzD0jtFM1AeEgCNH%2Fimage.png?alt=media&amp;token=4c06e941-bdb5-445b-8b36-807727b85524" alt="Clicking the webhook to test, then clicking &#x27;Test&#x27;." width="563"><figcaption></figcaption></figure>

Publisher sends a test HTTP POST message to the webhook URL configured for the selected webhook.

If the test is successful, the **Webhook Test** popup shows:

**A test webhook notification has been successfully sent**

<figure><img src="https://3773699522-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MX7dvS0r_4fc0AikgJS%2Fuploads%2FR2GI2OMRSpIPfcxOomSe%2Fimage.png?alt=media&amp;token=9b9c7362-e0be-47c2-99e9-d549e1628294" alt="A test webhook notification has been successfully sent" width="320"><figcaption></figcaption></figure>

The message should also appear in the target system, such as a Microsoft Teams channel or Slack workspace.

If the test fails, the **Webhook Send Error** is displayed with the resulting error, which can be copied to the Windows Clipboard to allow you to investigate the issue. The error typically indicates connectivity issues, an invalid webhook URL, or a response error from the destination service. The webhook must be configured correctly before notifications will work.

<figure><img src="https://3773699522-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MX7dvS0r_4fc0AikgJS%2Fuploads%2Fu27A8K4tqpxP9uN9fcI5%2Fimage.png?alt=media&amp;token=c217e0e2-eb89-4529-9709-a0afbca46838" alt="Failed Webhook Test" width="427"><figcaption></figcaption></figure>

## Copy button

Clicking **Copy** creates a new webhook based on the configuration of the selected webhook.

### To copy a webhook

1. Load Publisher.
2. Navigate to **Alerts | Webhooks**.
3. Click the existing webhook you want to copy, then click **Copy**.

<figure><img src="https://3773699522-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MX7dvS0r_4fc0AikgJS%2Fuploads%2FlI3zGY6W5kdgQrvcS9Ub%2Fimage.png?alt=media&amp;token=fecbb6d7-73a0-4d15-96ad-1f0b2351acab" alt="Clicking the webhook you want to copy, then clicking &#x27;Copy&#x27;." width="563"><figcaption></figcaption></figure>

The existing webhook is copied and selected. The new webhook is appended with **- Copy** at the end of the name so you know you are working on the copy, not the original.

<figure><img src="https://3773699522-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MX7dvS0r_4fc0AikgJS%2Fuploads%2FAmyWd9ho1QUwkumMAGsd%2Fimage.png?alt=media&amp;token=7325667d-22c5-4d98-a2d2-aa5b3c1002f8" alt="Copy of an existing webhook" width="563"><figcaption></figcaption></figure>

4. Update the **Name** field with a new name.
5. Update the **Webhook URL** field with the new webhook URL for this webhook.

{% hint style="info" %}
**Note**

If you attempt to save the new webhook without updating the **Webhook URL** field, the **Save Failed** dialog appears, telling you that you must update the **Webhook URL** field.

![Save failed](https://3773699522-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MX7dvS0r_4fc0AikgJS%2Fuploads%2FVhIywjVexWZ3scQnqkSA%2Fimage.png?alt=media\&token=4c997b45-8851-4997-84ab-7aee61a37c30)

All other settings are copied from the original webhook, including the message system and notification level. Webhook scope and product selection are also copied, allowing the new webhook to inherit the same filtering and targeting configuration.
{% endhint %}

6. Make any required changes to the configuration of the new webhook, then click **Apply** to save your changes.

{% hint style="success" %}
**Tip**

See [Add a Webhook](https://docs.patchmypc.com/patch-my-pc-publisher/manage/alerts-tab/webhooks-tab/add-webhook.md) for more information on the available options.
{% endhint %}

7. Once you have saved the new webhook, click [Test](#test-button) to ensure it works.

## Advanced button

Clicking **Advanced** opens the **Advanced Webhook Scope** screen that allows you to configure advanced settings for the webhook.

<figure><img src="https://3773699522-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MX7dvS0r_4fc0AikgJS%2Fuploads%2Fa7t5OExs0l4S6bKhejHI%2Fimage.png?alt=media&amp;token=59ee5a87-d112-40f2-bcdf-3e3c52f9aab7" alt="&#x27;Advanced Webhook Scope&#x27; screen" width="449"><figcaption></figcaption></figure>

The tabs under the **Product Selection** section reflect the same publishing areas available in Publisher, with each tab mapping directly to a corresponding Publisher tab:

* **Updates**
* **ConfigMgr Apps**
* **Intune Apps**
* **Intune Updates**

This alignment ensures that webhook product scoping follows the same structure and product groupings used for publishing configuration.

You can expand vendors and select individual products to include in webhook notifications. Only the selected products generate notifications for the corresponding content type.

Use the **Filter** field to quickly locate vendors or products by name.

{% hint style="danger" %}
**Important**

End-of-synchronization alerts cannot be filtered by specific product. If the **Send alerts as each product is published** option is disabled, product selection is disabled and all products are included automatically.
{% endhint %}

### To configure advanced settings for a webhook

1. Load Publisher.
2. Navigate to **Alerts | Webhooks**.
3. Click the webhook you want to configure, then click **Advanced**.

<figure><img src="https://3773699522-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MX7dvS0r_4fc0AikgJS%2Fuploads%2FJ3Uxk6pY2W6pKez1MIck%2Fimage.png?alt=media&amp;token=95362aa2-7f0e-4744-b28e-546a9939cd97" alt="Clicking &#x27;Advanced&#x27;" width="563"><figcaption></figcaption></figure>

4. On the **Advanced Webhook Scope** screen, configure the relevant products on the relevant tabs, then click **OK**.

## Remove button

Clicking **Remove** deletes the selected webhook.

### To remove a webhook

1. Load Publisher.
2. Navigate to **Alerts | Webhooks**.
3. Select the webhook you want to remove, then click **Remove**.

<figure><img src="https://3773699522-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MX7dvS0r_4fc0AikgJS%2Fuploads%2Fb1Ge84HIo7WRqs0AwPxt%2Fimage.png?alt=media&amp;token=31796501-0ce7-4ffb-8fb0-e73a413d46f2" alt="Clicking &#x27;Remove&#x27;" width="563"><figcaption></figcaption></figure>

The webhook is deleted from Publisher.

<figure><img src="https://3773699522-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MX7dvS0r_4fc0AikgJS%2Fuploads%2Fez4zeEVyTVb8PgsI7FB6%2Fimage.png?alt=media&amp;token=a68461b5-f670-4742-a8c8-824e63de9dda" alt="Webhook deleted" width="215"><figcaption></figcaption></figure>

{% hint style="danger" %}
**Important**

Removing a webhook does not display a confirmation dialog. The webhook is only permanently deleted after the Publisher settings are saved. If you close and reopen Publisher without clicking **Apply**, the removed webhook will still appear.
{% endhint %}

4. Click **Apply**.

## MSP Configuration

If you are using an MSP or MSP Plus license with multiple tenants configured, webhook notifications support tenant-level scoping.

<figure><img src="https://3773699522-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MX7dvS0r_4fc0AikgJS%2Fuploads%2FkvFWx1ZpR74yKizoVuKM%2Fimage.png?alt=media&amp;token=48de87b9-b091-4938-a0b6-c4ec010c922b" alt="Tenant Selection" width="450"><figcaption></figcaption></figure>

When creating or editing a webhook, you can select which tenant or tenants the notification applies to. If no tenants are selected, the webhook applies to all tenants. If specific tenants are selected, the webhook applies only to those tenants.


---

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