-
Notifications
You must be signed in to change notification settings - Fork 1
Notifications
VaultRequestrr DMs the requester when their request becomes available or is declined, and DMs the reporter when their issue is marked resolved. Each can be toggled with NOTIFY_ON_AVAILABLE, NOTIFY_ON_DECLINED, and NOTIFY_ON_ISSUE_RESOLVED (all default on) — see Configuration.
Requests made straight in the Seerr web UI are covered too: the bot matches the Seerr requester back to their linked Discord account and DMs them the same availability/decline notifications.
- Only works for users who have linked (i.e. made at least one request through the bot); unlinked users' web requests are silently skipped.
- Adopted web requests also show up in
/myrequestsand the dashboard Activity page. - Toggle with
TRACK_EXTERNAL_REQUESTSor on the dashboard (Settings → General → Bot behaviour); on by default. - When first enabled, requests that are already available or declined are recorded without sending catch-up DMs.
Delivery is driven by a Seerr webhook for near-instant DMs.
-
Set a webhook secret — either the
WEBHOOK_SECRETenv var or, more conveniently, the Seerr webhook card on the dashboard Settings page (which also shows the exact URL to paste). -
In Seerr, enable Settings → Notifications → Webhook and point it at:
http://<vaultrequestrr-host>:<WEB_PORT>/webhook/seerr?token=<WEBHOOK_SECRET>
The default JSON payload works as-is — no template needed.
A background poller also runs and adapts to whether a webhook is configured:
- No webhook: polls every ~2 minutes, so polling-only setups stay near-real-time.
-
Webhook set: relaxes to the
POLL_INTERVAL_SECONDSbackstop (default600), since the webhook now carries delivery. Notifications are never lost if a webhook is missed.
Set POLL_INTERVAL_SECONDS=0 to disable polling entirely.
VaultRequestrr · Report a bug · MIT licensed