[GH-ISSUE #4602] [Feature Request]: Ability to set up email or webhook for standard alerts #2123

Closed
opened 2026-03-02 13:49:48 +03:00 by kerem · 2 comments
Owner

Originally created by @fenz85 on GitHub (Sep 4, 2025).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/4602

Please confirm:

  • I have searched existing feature requests (open and closed) and found no duplicates.
  • **me or my organization is currently an active sponsor of the product at the $99,- level.

Problem Statement

Currently standard alerts go out to all notification methods.

Would be good that we could define which standards alert on email and which ones on webhook. Or at the very least that they were left on email only - it seems to be creating too much webhook noise. This is at least in our case where emails go to a triaging ticket board but webhooks we like to keep for more critical alerts.

Benefits for MSPs

Reducing clutter

Value or Importance

For the reasons mentioned before.

PowerShell Commands (Optional)

No response

Originally created by @fenz85 on GitHub (Sep 4, 2025). Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/4602 ### Please confirm: - [x] **I have searched existing feature requests** (open and closed) and found no duplicates. - [x] **me or my organization is currently an active sponsor of the product at the $99,- level. ### Problem Statement Currently standard alerts go out to all notification methods. Would be good that we could define which standards alert on email and which ones on webhook. Or at the very least that they were left on email only - it seems to be creating too much webhook noise. This is at least in our case where emails go to a triaging ticket board but webhooks we like to keep for more critical alerts. ### Benefits for MSPs Reducing clutter ### Value or Importance For the reasons mentioned before. ### PowerShell Commands (Optional) _No response_
Author
Owner

@github-actions[bot] commented on GitHub (Sep 14, 2025):

This issue is stale because it has been open 10 days with no activity. We will close this issue soon. If you want this feature implemented you can contribute it. See: https://docs.cipp.app/dev-documentation/contributing-to-the-code . Please notify the team if you are working on this yourself.

<!-- gh-comment-id:3289094440 --> @github-actions[bot] commented on GitHub (Sep 14, 2025): This issue is stale because it has been open 10 days with no activity. We will close this issue soon. If you want this feature implemented you can contribute it. See: https://docs.cipp.app/dev-documentation/contributing-to-the-code . Please notify the team if you are working on this yourself.
Author
Owner

@github-actions[bot] commented on GitHub (Sep 20, 2025):

This issue was closed because it has been stalled for 14 days with no activity.

<!-- gh-comment-id:3314401904 --> @github-actions[bot] commented on GitHub (Sep 20, 2025): This issue was closed because it has been stalled for 14 days with no activity.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/CIPP#2123
No description provided.