[GH-ISSUE #1221] To send attachement and subscribe/un-subscribe using Android intent (enhancement) #859

New issue

Open

opened 2026-05-07 00:28:14 +02:00 by BreizhHardware · 0 comments

BreizhHardware commented

2026-05-07 00:28:14 +02:00

Owner

Originally created by @osering on GitHub (Nov 12, 2024).
Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/1221

On the one hand there is documentation how to attach/send files (https://docs.ntfy.sh/publish/#attach-local-file) and OS Android shown as supported.
On the other hand, there is Android intent description under heading Action buttons (https://docs.ntfy.sh/publish/#action-buttons) and https://docs.ntfy.sh/publish/#send-android-broadcast, but only for sending messages.

Nevertheless, when receiving attachments - Android intent works perfectly and has decent description in this github (for both, Tasker and Macrodroid), but when sending attachments - there is a total lack of documentation (settings suggestions), although it shouldn't be much different from message sending & message/attachment receiving with Android intents.
So there is a (knowledge) gap and inconsistency in this great software.
The enabled usage of Android intents for subscription and un-subscription would be useful as well (especially for automation workflows).

💡 Idea
Enhancement: documentation shall provide guidelines/settings/screenshots - how to set up Macrodroid (probably, Tasker as well, but have not used it) with ntfy.sh to enable to use Android intents to send attachments. Would be great if documentation includes information - which mode - broadcast or other shall be used, what is the syntax to indicate local file and which fields shall be filled. For Macrodroid relevant could be screenshots with these sections: 1) Actions -> Connectivity -> Send Intent & 2) Actions -> Camera/Photo -> Take screenshot -> Share via intent.
Otherwise right now bash/jJS scripts shall be used instead.
No clue how to circumvent subscription and un-subscribtion though.

P.S. For instance, when using Macrodroids' manual screenshot attaching function, using Android intent, it works (and sends picture attachment trough ntfy) smoothly, so it looks like more documentation problem and not software problem.

Originally created by @osering on GitHub (Nov 12, 2024). Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/1221 On the one hand there is documentation how to attach/send files (https://docs.ntfy.sh/publish/#attach-local-file) and OS Android shown as supported. On the other hand, there is Android intent description under heading Action buttons (https://docs.ntfy.sh/publish/#action-buttons) and https://docs.ntfy.sh/publish/#send-android-broadcast, but only for sending messages. Nevertheless, when receiving attachments - Android intent works perfectly and has decent description in this github (for both, Tasker and Macrodroid), but when sending attachments - there is a total lack of documentation (settings suggestions), although it shouldn't be much different from message sending & message/attachment receiving with Android intents. So there is a (knowledge) gap and inconsistency in this great software. The enabled usage of Android intents for subscription and un-subscription would be useful as well (especially for automation workflows). :bulb: **Idea** Enhancement: documentation shall provide guidelines/settings/screenshots - how to set up Macrodroid (probably, Tasker as well, but have not used it) with ntfy.sh to enable to use Android intents to send attachments. Would be great if documentation includes information - which mode - broadcast or other shall be used, what is the syntax to indicate local file and which fields shall be filled. For Macrodroid relevant could be screenshots with these sections: 1) Actions -> Connectivity -> Send Intent & 2) Actions -> Camera/Photo -> Take screenshot -> Share via intent. Otherwise right now bash/jJS scripts shall be used instead. No clue how to circumvent subscription and un-subscribtion though. P.S. For instance, when using Macrodroids' manual screenshot attaching function, using Android intent, it works (and sends picture attachment trough ntfy) smoothly, so it looks like more documentation problem and not software problem.