feat[notifications]: Add Dokploy Backup notification type support #2907
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds support for the Dokploy Backup notification type across all relevant services, schemas, and UI components.
What is this PR about?
This PR introduces a new notification trigger called Dokploy Backup, which notifies users when a Dokploy system backup succeeds or fails.
The motivation behind this addition came after I noticed one of my VPS Dokploy backups had failed, but I wasn’t aware of it until several days later when manually checking the admin interface.
To prevent such cases and ensure continuous visibility over backup operations, this feature now provides both success and failure notifications through all supported channels (Slack, Telegram, Email, etc.).
Checklist
Before submitting this PR, please make sure that:
Manual Testing
This feature has been manually tested on a local Dokploy instance, covering all main cases:
No automated tests were added, as the notification system currently does not include test coverage and all scenarios were manually validated end-to-end.
Screenshots
Notification provider menu
Success Telegram Notification
Failed Telegram Notification