Poacher help
Connect and manage notifications
Choose destinations per alert and distinguish provider acceptance from actual receipt.
Email and immediate destinations
Email uses your verified account address and follows the delivery style selected for each alert. Slack and Discord use incoming channel webhooks. ntfy currently supports topics on ntfy.sh. Connect a destination in Account → Notifications, then select it for existing alerts. Connecting does not send a test message.
Who can see a notification
People with access to a Slack or Discord channel may see its alert names and results. An unprotected ntfy topic can be read by anyone who knows its name; an access token alone does not make it private. Use a hard-to-guess topic and check its access settings. Keep webhook URLs and tokens out of support messages.
Pause, disconnect and limit volume
Pause a connection to stop new delivery through it. Disconnecting removes its stored destination credentials and its routing from alerts. New alerts send the first three results in a rolling hour immediately, then group further results into hourly summaries. When activity slows, the waiting summary is sent and immediate delivery resumes. Choose immediate delivery for every result, hourly summaries, or a different grouping threshold in Notifications. Existing alerts keep their previous limits until you change them. Results remain in Poacher in every mode. Security and payment emails are separate from result notifications.
Current availability
Browser push enrollment opens only when its service configuration is ready. Messenger and Instagram connection flows are still in preparation. SMS is not part of the current launch. A message marked accepted was accepted by its provider; that does not prove inbox placement, device display or a human view.