# Webhook Configuration

*Applies to: Patch My PC Publisher*

## Overview

The **Notification Webhook Configuration** dialog is shown when creating a new webhook, editing an existing webhook, or copying a webhook.

<figure><img src="https://3773699522-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MX7dvS0r_4fc0AikgJS%2Fuploads%2FYDgBCjnb8UN1bFzjC4XC%2Fimage.png?alt=media&#x26;token=e3267deb-cbe8-4370-8aaa-a2be0c482783" alt="Webhook Configuration" width="450"><figcaption></figcaption></figure>

## Name

Specifies a friendly label used to identify the webhook in the Publisher.

## Webhook Provider

Specifies the target messaging system used for webhook notifications. The selected provider determines the expected webhook payload format.

### Microsoft Teams Workflow

This is the recommended option for Microsoft Teams. It uses the modern Microsoft Teams workflow based webhook model, which supports Adaptive Cards. See [Create a Microsoft Teams Webhook URL](https://docs.patchmypc.com/patch-my-pc-publisher/administration/alerts/webhook-notifications/create-a-microsoft-teams-webhook-url) for more information.

### Microsoft Teams Legacy Webhook

This option exists only for backward compatibility with older Publisher configurations where  Microsoft Teams webhooks were created using the legacy Microsoft Teams incoming webhook model.

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

The legacy provider was used by earlier versions of the Publisher that relied on the older Teams message card format. It is retained to ensure existing customer configurations continue to function without requiring immediate changes.
{% endhint %}

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

Customers using the legacy provider should plan to migrate to Microsoft Teams Workflow. See [Update a Microsoft Teams Legacy Webhook to Use Workflows](https://docs.patchmypc.com/patch-my-pc-publisher/administration/alerts/webhook-notifications/update-a-microsoft-teams-legacy-webhook-to-use-workflows) for more information.
{% endhint %}

### Slack

This option sends webhook notifications to Slack using the Slack webhook payload format. see [Create a Slack Webhook URL](https://docs.patchmypc.com/patch-my-pc-publisher/administration/alerts/webhook-notifications/create-a-slack-webhook-url) for more information.

## Webhook URL

Specifies the destination webhook endpoint URL generated by the target messaging platform. This field is required and must be valid for notifications to be delivered.&#x20;

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

The webhook URL must start with `http://` or `https://` to be considered valid.
{% endhint %}

## Notification Level

Controls which publishing events generate notifications for this webhook. This setting determines the overall verbosity of webhook messages.

* **All**\
  Sends notifications for all publishing events, including successes and errors.
* **Error**\
  Sends notifications only when a publishing error occurs.
* **Success**\
  Sends notifications only when publishing actions complete successfully.

## Send alerts as each product is published

This option is enabled by default and is the recommended configuration.

When enabled, webhook notifications are sent after each product is processed during a publishing synchronization. Each notification represents an individual product that has been successfully processed or failed, making it easier to track progress during large publishing runs.

<figure><img src="https://3773699522-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MX7dvS0r_4fc0AikgJS%2Fuploads%2FveUv5LErTFAoiuITkukF%2Fimage.png?alt=media&#x26;token=07062e9f-08ff-4bb4-9027-5a1dea194a6b" alt="Send alerts as each product is published is enabled" width="563"><figcaption></figcaption></figure>

When this option is disabled, a single webhook notification is sent only after all products have finished processing at the end of the publishing synchronization.

<figure><img src="https://3773699522-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MX7dvS0r_4fc0AikgJS%2Fuploads%2Ffj39eZiqf16C819SX5vt%2Fimage.png?alt=media&#x26;token=67e00727-a706-4b9a-9a07-d0376921a452" alt="Send alerts as each product is published is disabled" width="563"><figcaption></figcaption></figure>

The end of synchronization notification provides a consolidated summary of all processed products but does not provide visibility into progress while the synchronization is running.

## Webhook Scope

The tabs shown in **Product Selection** reflect the same publishing areas available in the Publisher.

Each tab maps 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.

<figure><img src="https://3773699522-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MX7dvS0r_4fc0AikgJS%2Fuploads%2Fej9YxKcC2ZF9LG9tEcif%2Fimage.png?alt=media&#x26;token=e255d2d3-7178-45f1-80b8-73f26fb03665" alt="Product Selection" width="450"><figcaption></figcaption></figure>

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="warning" %}
**Important**

**E**nd of synchronization alerts cannot be filtered by specific product. If [Send alerts as each product is published](#send-alerts-as-each-product-is-published) is unchecked, product selection is disabled and all products are included automatically.
{% endhint %}

### 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&#x26;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.