starred/qBittorrent

Fork 0

mirror of https://github.com/qbittorrent/qBittorrent.git synced 2026-03-02 22:57:32 -05:00

Pushover notification #13529

New issue

Open

opened 2026-02-22 00:02:10 -05:00 by deekerman · 6 comments

deekerman commented

2026-02-22 00:02:10 -05:00

Owner

Originally created by @Nicode70 on GitHub (Jun 12, 2022).

Suggestion

Hi,

Is it possible to have a pushover integration built right into qbittorrent? It would be very very helpful to be notified once a torrent is finished download.

thank you.

Use case

No response

Extra info/examples/attachments

No response

Originally created by @Nicode70 on GitHub (Jun 12, 2022). ### Suggestion Hi, Is it possible to have a pushover integration built right into qbittorrent? It would be very very helpful to be notified once a torrent is finished download. thank you. ### Use case _No response_ ### Extra info/examples/attachments _No response_

deekerman added the

Feature request

Waiting info

labels

2026-02-22 00:02:10 -05:00

deekerman commented

2026-02-22 00:02:15 -05:00

Author

Owner

@AN1MATEK commented on GitHub (Apr 13, 2023):

I second this, great feature.

@AN1MATEK commented on GitHub (Apr 13, 2023): I second this, great feature.

deekerman commented

2026-02-22 00:02:17 -05:00

Author

Owner

@luzpaz commented on GitHub (Nov 2, 2023):

Do you mean push notifications? #16414

@luzpaz commented on GitHub (Nov 2, 2023): Do you mean **push notifications**? #16414

deekerman commented

2026-02-22 00:02:17 -05:00

Author

Owner

@epsimatic commented on GitHub (Jul 19, 2024):

OP likely meant Pushover, a commercial web service. It's often used by homelab people as multi-source, multi-destination notification hub. It's quite cheap and needs no recurring payment. I would like that to be supported, too.

There currently are two notification methods for qbittorrent: email and script.

Email is quite hard and unsafe to have configured. I suppose you're not gathering this type of stats, but I doubt many folks managed have email notifications working.
Script is good enough way to get notified. A custom script solves the problem for now.
Native browser Web Push API would be nice as well after it's stabilised. It's W3C working draft as of now, but it's implemented ahead of time in some browsers. That's probably #16414 . NB: Pushover implements Web Push API too, but it's a $5 one-time purchase.

@epsimatic commented on GitHub (Jul 19, 2024): OP likely meant [Pushover](https://pushover.net/api), a commercial web service. It's often used by homelab people as multi-source, multi-destination notification hub. It's quite cheap and needs no recurring payment. I would like that to be supported, too. There currently are two notification methods for qbittorrent: email and script. - Email is quite hard and unsafe to have configured. I suppose you're not gathering this type of stats, but I doubt many folks managed have email notifications working. - Script is good enough way to get notified. A [custom script](https://blog.rraghur.in/2017/01/30/torrent-download-notifications-with-pushover/) solves the problem for now. - Native browser [Web Push API](https://caniuse.com/push-api) would be nice as well after it's stabilised. It's W3C working draft as of now, but it's implemented ahead of time in some browsers. That's probably #16414 . NB: Pushover implements Web Push API too, but it's a $5 one-time purchase.

deekerman commented

2026-02-22 00:02:17 -05:00

Author

Owner

@AN1MATEK commented on GitHub (Jul 19, 2024):

Pushover with the script works very well. I have it setup and get tons of notifications for different events.

@AN1MATEK commented on GitHub (Jul 19, 2024): Pushover with the script works very well. I have it setup and get tons of notifications for different events.

deekerman commented

2026-02-22 00:02:17 -05:00

Author

Owner

@epsimatic commented on GitHub (Aug 9, 2024):

UPD: No need for a Pushover script either if you have curl installed (you most certainly do).

Torrent downloaded command:

curl -s --form-string "message=%N (%L)" --form-string "title=Torrent downloaded" --form-string "priority=-1" --form-string "token=APP_TOKEN" --form-string "user=USER_KEY" https://api.pushover.net/1/messages.json

Replace:

USER_KEY with your user key
APP_TOKEN — create an app and use its token

@epsimatic commented on GitHub (Aug 9, 2024): UPD: No need for a Pushover script either if you have `curl` installed (you most certainly do). Torrent downloaded command: ```bash curl -s --form-string "message=%N (%L)" --form-string "title=Torrent downloaded" --form-string "priority=-1" --form-string "token=APP_TOKEN" --form-string "user=USER_KEY" https://api.pushover.net/1/messages.json ``` Replace: - `USER_KEY` with your [user key](https://pushover.net/) - `APP_TOKEN` — [create an app](https://pushover.net/apps/build) and use its token

deekerman commented

2026-02-22 00:02:17 -05:00

Author

Owner

@xavier2k6 commented on GitHub (May 24, 2025):

ANNOUNCEMENT!

For anybody coming across this "Feature Request" & would like/love to see a potential implementation in the future!
Here are some options available to you:

Please select/click the 👍 &/or ❤ reactions in the original/opening post of this ticket.
Please feel free (If you have the "skillset") to create a "Pull Request" implementing what's being requested in this ticket.
(new/existing contributors/developers are always welcome)

DO:

Provide constructive feedback.
Display how other projects implemented same/similar etc.

DO NOT:

Add a "Bump", "me too", "2nd/3rd" etc. or "criticizing" comment(s).
(These will be disregarded/hidden as "spam/abuse/off-topic" etc. as they don't provide anything constructive.)

@xavier2k6 commented on GitHub (May 24, 2025): ## ANNOUNCEMENT! For anybody coming across this **_"Feature Request"_** & would like/love to see a potential implementation in the future! **Here are some options available to you:** 1. Please select/click the 👍 **&/or** ❤ `reactions` in the original/opening post of this ticket. 2. Please feel free _(If you have the "skillset")_ to create a **_"Pull Request"_** implementing what's being requested in this ticket. **_(new/existing contributors/developers are always welcome)_** ____ **DO:** * Provide constructive feedback. * Display how other projects implemented same/similar etc. **DO NOT:** * Add a "Bump", "me too", "2nd/3rd" etc. or "criticizing" comment(s). **(These will be disregarded/hidden as "spam/abuse/off-topic" etc. as they don't provide anything constructive.)**