Email (or any other) Notification upon creation of Scheduled Maintenance #3087

New issue

Closed

opened 2026-02-28 03:17:29 -05:00 by deekerman · 1 comment

deekerman commented

2026-02-28 03:17:29 -05:00

Owner

Originally created by @skeelkat on GitHub (Jan 31, 2024).

None Found

🏷️ Feature Request Type

Maintenance

🔖 Feature description

Add Notification Mechanism for Scheduled Maintenance upon add or edit.

✔️ Solution

A nice to have, would be that an email notification (or other) is sent to a specified recipient the moment after a scheduled maintenance is added and or edited.

This will provide administrators to notify certain parties of planned / scheduled maintenance all from Uptime Kuma

❓ Alternatives

No response

📝 Additional Context

No response

Originally created by @skeelkat on GitHub (Jan 31, 2024). ### 📑 I have found these related issues/pull requests None Found ### 🏷️ Feature Request Type Maintenance ### 🔖 Feature description Add Notification Mechanism for Scheduled Maintenance upon add or edit. ### ✔️ Solution A nice to have, would be that an email notification (or other) is sent to a specified recipient the moment after a scheduled maintenance is added and or edited. This will provide administrators to notify certain parties of planned / scheduled maintenance all from Uptime Kuma ### ❓ Alternatives _No response_ ### 📝 Additional Context _No response_

deekerman

2026-02-28 03:17:29 -05:00

closed this issue
added the
feature-request

A:notifications

A:maintenance
labels

deekerman commented

2026-02-28 03:17:32 -05:00

Author

Owner

@CommanderStorm commented on GitHub (Jan 31, 2024):

This issue is tracked in https://github.com/louislam/uptime-kuma/issues/2462
=> closing as a duplicate

Note that #2462 might require https://github.com/louislam/uptime-kuma/issues/508 or other creative mechanisms of managing which notification provider should be chosen first. If you have good Ideas, please comment them in #2462

Our contribution guide is here: https://github.com/louislam/uptime-kuma/blob/master/CONTRIBUTING.md

@CommanderStorm commented on GitHub (Jan 31, 2024): This issue is tracked in https://github.com/louislam/uptime-kuma/issues/2462 => closing as a duplicate Note that #2462 might require https://github.com/louislam/uptime-kuma/issues/508 or other creative mechanisms of managing which notification provider should be chosen first. If you have good Ideas, please comment them in #2462 Our contribution guide is here: https://github.com/louislam/uptime-kuma/blob/master/CONTRIBUTING.md