Repository navigation
Advanced Notification Triggers: Category-based Include/Exclude Filters for Events #2063
Replies: 1 comment
Duplicate of #1952, which asks for the same control: include/exclude rules on notification events by category (and tag), so a busy webhook only fires for the categories you care about. What we confirmed in the code: a notification target stores an event-type list and nothing else, and dispatch only checks whether the target subscribes to the event type. There is no category scoping today, so the request is valid and unimplemented. Closing this one so the request lives in a single thread. Your extra detail is worth keeping, so please add it to #1952: per-event rules rather than one rule for the whole agent, categories read from the connected instance, no rule meaning fire for every category, and the point that one agent per category does not scale. |
Uh oh!
There was an error while loading. Please reload this page.
Summary:
Right now, notification agents in Settings > Notifications let you pick which events to subscribe to (e.g. torrent_created, torrent_completed). That's great, but there's no way to scope those events to specific categories. The result: a single busy Discord channel receiving noise from every category, cross-seeds, auto-managed torrents, manual grabs, all mixed together.
Problem:
I have a Discord webhook subscribed to torrent_created and torrent_completed. My qBittorrent setup uses multiple categories (e.g. sonarr, radarr, cross-seed, manual). Some categories are high-volume or low-priority and I don't want a Discord ping for every single one , but I also can't just disable the events entirely, since I do want them for other categories.
There's currently no way to say "notify me when a torrent is completed unless it's in the cross-seed category."
Proposed Feature: Advanced Event Triggers / Category Filters:
When configuring a notification agent, add an optional Advanced Triggers section that exposes category-level include/exclude rules per event.
Categories: multi-select from existing qBittorrent categories (dynamically populated from the connected instance)
If no rule is defined for an event, the event fires for all categories (existing behavior, fully backwards-compatible)
Why "Advanced Triggers" over a separate agent per category?
The workaround of creating one notification agent per category quickly becomes unmanageable. If I have 8 categories and 3 events, that's potentially 24 agents to maintain. A single agent with category filter rules is far cleaner and easier to audit.
All reactions