> 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/administration/alerts/webhook-notifications/webhook-configuration.md). # Webhook Configuration *Applies to: Patch My PC Publisher V2.x* ## Overview The **Notification Webhook Configuration** dialog is shown when creating a new webhook, editing an existing webhook, or copying a webhook.
Webhook Configuration
## 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](/patch-my-pc-publisher/administration/alerts/webhook-notifications/create-a-microsoft-teams-webhook-url.md) 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](/patch-my-pc-publisher/administration/alerts/webhook-notifications/update-a-microsoft-teams-legacy-webhook-to-use-workflows.md) for more information. {% endhint %} ### Slack This option sends webhook notifications to Slack using the Slack webhook payload format. see [Create a Slack Webhook URL](/patch-my-pc-publisher/administration/alerts/webhook-notifications/create-a-slack-webhook-url.md) 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. {% 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.
Send alerts as each product is published is enabled
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.
Send alerts as each product is published is disabled
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.
Product Selection
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.
Tenant Selection
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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.patchmypc.com/patch-my-pc-publisher/administration/alerts/webhook-notifications/webhook-configuration.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.