mirror of
https://github.com/binwiederhier/ntfy.git
synced 2026-05-09 08:26:00 +02:00
[GH-ISSUE #1426] Allow templating in the Priority field #1003
Labels
No labels
ai-generated
android-app
android-app
android-app
🪲 bug
build
build
dependencies
docs
enhancement
enhancement
🔥 HOT
in-progress 🏃
ios
prio:low
prio:low
pull-request
question
🔒 security
server
server
unified-push
web-app
website
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/ntfy#1003
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @seantomburke on GitHub (Aug 18, 2025).
Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/1426
💡 Idea
I can use inline templating in with the GET method in the
messagequery param and thetitlequery param. I would also like to use the inline templating to set the priority field. For example, if my payload has an error field or status field, I would like to use that to set the priority of the message. Currently when I do this with the priority field, I get a 400 error, and the docs specify inline templating is only available for the message field.💻 Target components
Should be added to
ntfy serverGET request method in the Query Params for Priority. Example:
https://ntfy.com/topic?priority={{if eq .status "Error"}}5{{else}}3{{end}}@binwiederhier commented on GitHub (Feb 4, 2026):
Done in
github.com/binwiederhier/ntfy@570b188a88