Tasker clobbering intent extra

90 views
Skip to first unread message

wunter8

unread,
Apr 22, 2025, 5:14:10 AM4/22/25
to Tasker
I have been using Tasker to react to messages received by ntfy (https://ntfy.sh).

The ntfy Android app is configured to broadcast an intent for each message received. The fields of the message are passed to Tasker via EXTRAS.

Most of the EXTRAS work fine, but I cannot access the `priority` field from the ntfy message because `%priority` returns the "System: Task Priority" value instead of the EXTRA called "priority".

I tried using `%priority_dup`, but it seems like only works if there are multiple EXTRAS that end up with the same name, and not if an EXTRA matches any existing variable. 

Is there some other way to access the EXTRA called "priority"? Or do I need to reach out to the ntfy dev to change the name of that EXTRA?

Thanks!

wunter8

unread,
Jan 14, 2026, 8:31:25 AM (2 days ago) Jan 14
to Tasker
Trying to bump this. I'm still having this problem. Any known workarounds?
Reply all
Reply to author
Forward
0 new messages