-
Notifications
You must be signed in to change notification settings - Fork 0
Notification Services
Queue Pop Notifier supports three notification services:
- Pushover
- ntfy
- Telegram
Only one service can be active at a time.
Open the Windows companion client settings, configure the service you want to use, and set it as the active notification service.
After configuration, use the built-in service test to verify that notifications reach your smartphone.
Pushover is a dedicated push-notification service for Android and iPhone.
You need:
- a Pushover account
- the Pushover smartphone app
- your User Key
- an API Token
You can find your User Key in your Pushover account.
Create an application in the Pushover dashboard to obtain an API Token.
Queue Pop Notifier supports:
- Normal — standard Pushover notification behavior
- High — higher-priority notification; recommended for iPhone if you want queue alerts to be harder to miss
After entering your User Key and API Token, use Test service.
If the test notification arrives successfully, select Pushover as the active notification service.
Pushover allows custom notification sounds.
Queue Pop Notifier provides a queue-pop sound that can be uploaded to your Pushover account:
In the Pushover dashboard:
- Open Your Custom Sounds.
- Select Upload a Sound.
- Upload the downloaded sound file.
- Give it a short name, such as Queue.
- Select the sound for Queue Pop Notifier notifications in the Pushover app.
ntfy is a lightweight notification service that uses topics to deliver notifications.
You need:
- an ntfy topic
- an ntfy server
For the public ntfy service, the server is normally:
https://ntfy.sh
Choose a topic name and use the same topic in the ntfy smartphone app and in Queue Pop Notifier.
Anyone who knows a public topic name may be able to subscribe to it.
Use a topic name that is difficult to guess rather than something simple such as:
queue
wow
notifications
A longer random topic name is preferable.
Queue Pop Notifier supports ntfy notification priorities suitable for normal and high-priority queue alerts.
After entering the topic and server, use Test service.
If the notification arrives successfully, select ntfy as the active notification service.
If you operate your own ntfy server, enter its server address instead of https://ntfy.sh.
The same Queue Pop Notifier setup can then be used with your own server.
Queue Pop Notifier can send queue notifications through a Telegram bot.
You need:
- a Telegram account
- a Telegram bot
- the bot's Bot Token
- your Chat ID
In Telegram, open a conversation with BotFather.
Create a new bot and follow the instructions provided by BotFather.
After creation, BotFather provides a Bot Token.
Enter this token in the Queue Pop Notifier settings.
Open your newly created bot in Telegram and send it at least one message.
This is required before Telegram can return your Chat ID through the bot API.
After sending a message to the bot, use Telegram's bot API getUpdates method to retrieve the latest messages received by your bot.
The returned information contains your Chat ID.
Enter the Chat ID in the Queue Pop Notifier settings.
Use Test service in Queue Pop Notifier.
If the Telegram message arrives successfully, select Telegram as the active notification service.
Queue Pop Notifier can store configuration for multiple services, but only one notification service is active at a time.
To switch services:
- Open the Windows companion client settings.
- Open the service you want to use.
- Make sure its configuration is complete.
- Select it as the active/default notification service.
- Save the settings.
The other configured services remain available and can be selected again later.
Each notification service has its own built-in test.
Use the service test after:
- setting up a service for the first time
- changing credentials
- changing the ntfy server or topic
- changing the Telegram bot or Chat ID
- troubleshooting missing notifications
For a complete end-to-end test including the WoW add-on, enter:
/qpn test
inside World of Warcraft.
If a service test or /qpn test does not reach your smartphone, see: