Skip to content

Webhook notifications

Send Patcherly alerts to Slack, Microsoft Teams, Discord, or another tool that accepts an incoming webhook URL. Workspace admins configure chat channels in Profile → Notifications; everyone on the team can still choose their own email and in-app preferences in the same tab.

Who can set this up

The Chat & webhooks section on Profile → Notifications is visible to everyone on the workspace. Workspace owners, members with full workspace access, or members granted Manage chat integrations can connect channels and save webhooks; other members see setup guidance and a link for the Slack Marketplace install path. Per-user notification toggles apply to email and in-app only. Which events post to each chat channel is controlled in the Slack, Discord, Teams, and Webhook columns in the preference table (workspace-wide).

Connect Slack, Discord, or Teams

  1. In Patcherly, open Profile from the top bar (your name or avatar).
  2. Open the Notifications tab.
  3. Under Chat & webhooks (below the preference table), click Connect Slack in the highlighted Connect from Patcherly box (or Connect for Discord or Teams) and approve the Patcherly app in the provider's consent screen.
  4. Choose a channel (and for Teams, a team first), then click Test to verify delivery.
  5. In the table above, enable the Slack, Discord, or Teams column per event you want posted, then click Save Notification Preferences.

Patcherly ships official apps for these platforms — you do not create your own Slack app or incoming webhook for Patcherly notifications.

Slack Marketplace: If you installed from the Slack Marketplace first, expand Installed from Slack Marketplace first? under the Slack section, open the install link while signed in to Patcherly, then use the Finish connecting Slack panel to link your workspace and pick a channel.

Microsoft Teams: Some organizations require an IT admin to approve the Patcherly app before Connect succeeds. If Connect fails with a consent or permissions error, ask your Teams admin to grant access or use email/in-app notifications and Other webhook instead.

Other webhook (Mattermost, Google Chat, Zapier, etc.)

Use the Other webhook section on the same tab when your tool is not Slack, Discord, or Teams:

  1. Paste your tool's incoming webhook URL.
  2. Choose Delivery mode:
  3. Simple notification — plain-text payload for standard incoming webhooks.
  4. Developer signed JSON — Patcherly event JSON with X-Patcherly-Signature HMAC verification (for custom automation).
  5. Save and enable events in the Webhook column in the preference table above, then click Save Notification Preferences.

See your vendor's documentation for creating an incoming webhook URL in that product.

Events you can send to chat

Typical choices (exact names appear as rows in Business Event Notifications; chat columns apply only where supported):

  • New error detected on a target
  • Patch applied or patch failed
  • Rollback triggered
  • Fix needs your approval (low-confidence suggestion)
  • Error digest — periodic summary of open issues (opt-in per integration)
  • Connector outdated — reminder to upgrade the connector on a target

Email, in-app, and chat together

You can mix channels. For example: Slack for new errors, email for billing reminders, and in-app for everything else. Change email/in-app toggles in Notification preferences; change chat delivery with the Slack, Discord, Teams, and Webhook columns on the same table.