Custom template for ntfy (or any service provider?)

[epifeny]

📑 I have found these related issues/pull requests

Custom notification message templates with variable substitution

🔖 Feature description

Add support for custom notification message templates using a {{variable}} syntax, allowing users to customize notification titles and messages with dynamic values from their monitors (e.g., {{name}}, {{status}}, {{hostname}}).

This would give users more control over notification content and make messages more compact and personalized. For example, instead of the default verbose messages, users could create concise templates like "{{statusEmoji}} {{name}}" for the title.

✔️ Solution

I've created a POC for the ntfy notification provider that includes:

• Custom title and message template fields at the notification level
• A collapsible UI section that expands when templates are configured
• Variable substitution that works with any monitor field

Screenshots showing the implementation:

• Collapsed by default when empty
• Expanded view with template fields
• Sample notifications with custom templates

I'd like guidance on extending this to:

1. Make it available for other notification providers (Discord, Gotify, etc.)
2. Add per-monitor template overrides (allowing each monitor to customize its messages beyond the notification-level templates)

❓ Alternatives

For per-monitor templates, I explored adding fields to the monitor table and handling them in core files, but I'm uncertain if this is the right approach. There might be a cleaner way to implement provider-specific per-monitor settings that I'm not aware of.

Another alternative would be to keep it notification-level only, but that seems limiting for users with diverse monitoring needs.

📝 Additional Context

The button collapsed by default when empty:

The button expanded when configured:

Sample notifications with custom templates:

I'm new to contributing to Uptime Kuma, so any direction on the best architectural approach would be appreciated. This feature was requested 3-4 years ago on Reddit, so there seems to be community interest.
https://www.reddit.com/r/UptimeKuma/comments/x2p7v1/compact_notification_messages_or_modify/
https://www.reddit.com/r/UptimeKuma/comments/r9oeq0/modify_email_template/

[CommanderStorm]

From the templating arguments you are allowing, it does not look like you are using the existing message templating for this.

We can add it, if this is using the existing way of templating (-> like in telegram, smtp, ...)
I don't think that maintaining multiple notification providers is sustainable.

• Adding templating to more notification providers #646

The existing templating is also much simpler to add..

[epifeny]

Thank you for the feedback! Tell me if I'm understanding this correctly, you're saying Uptime Kuma already has a templating system used by providers like Telegram and SMTP, and I should use that existing system instead of creating my own {{variable}} approach?

If that's right, could you point me to the specific files where the existing templating is implemented so I can study how it works? I want to make sure I follow the correct pattern.

If you even think you can give me some pieces of code or a sample that i can check out, it would even be more amazing.
Thanks for your patience, I'm still learning the codebase!

[epifeny]

I don't think that maintaining multiple notification providers is sustainable.

I've already went ahead and created some POC that seems to work well. Before anything, I wanted to understand if you would allow me to issue a PR for ntfy or will you only accept if this only extends to all notification providers and all monitor types?

My current change, uses LiquidJS templating as you suggested, and I've tested it locally and it seems to be quite amazing (IMHO), for me.

This shows the monitor level template

This shows the notification service level template

This shows the ntfy custom messages arriving perfectly, just ask I wanted them (for the POC ofc!)

Hint, notice how "phones" group, got the 'Up this is my custom msg for ntfy' notification provider level message, since that group doesn't have it's own custom message, so it uses the notification provider level template instead

[CommanderStorm]

Shure, that looks good to me.
I would ask for the templating to be a toggler instead of a button but that should be a simple change.

Before anything, I wanted to understand if you would allow me to issue a PR for ntfy or will you only accept if this only extends to all notification providers and all monitor types?

Please only change one notification provider in one PR.
It is very difficult to impossible to know that everything works otherwise 😉
We don't want to break notifications for obvious reasons.