Skip to content
Librariarr

Notifications

Librariarr supports Discord webhook notifications. Configure them in Settings → Notifications.

Discord Webhooks

Section titled “Discord Webhooks”

Send notifications to a Discord channel via webhook.

Setup

Section titled “Setup”
  1. In Discord, go to Channel Settings → Integrations → Webhooks
  2. Create a new webhook and copy the URL
  3. In Librariarr, go to Settings → Notifications
  4. Paste the webhook URL (once saved it is shown masked — a webhook URL lets anyone post to the channel, so the app never returns it again; paste a new one to replace it)
  5. Optionally set a custom username (default: “Librariarr”) and avatar URL
  6. Click Test Webhook to verify it works

Events

Section titled “Events”

Discord notifications are sent for:

  • Lifecycle actions: When a scheduled execution run executes actions (delete, unmonitor, etc.), one summary per rule set for its successes and one for its failures. A manual Execute from the Pending page notifies on failures only.
  • Match changes: When a scheduled detection run (or Run now in Settings → Scheduling) finds new matches or removes stale ones. A Re-evaluate from the Matches page does not notify.
  • Deletion held for review: When a run is held by the deletion limit — a scheduled run, Execute on the Pending page (or the API’s execute endpoint), or a Query page action — or a run queued through the public API is held by the API deletion limits. A scheduled run is announced every time; a hand-started run and an API-queued one at most once per 15 minutes, since they can be retried in a loop. Sent whenever a webhook is set; it has no toggle.
  • Maintenance mode: When maintenance mode is toggled on/off. Turn this on with Notify Discord in the maintenance section of Tools → Streams (off by default).
  • API keys: When a key for the public API is created or deleted. On by default whenever a webhook is set (Settings → Notifications → API keys), because a key outlives the login session that created it — a creation you did not make is the sign of a stolen session, and the notification says what to do.

Lifecycle action and match notifications are off by default and configured per rule set in the rule editor: Send Discord notification on action execution and Send Discord notification on match changes.

Message Format

Section titled “Message Format”

Notifications are sent as Discord embeds with:

  • Title: Rule set or event name
  • Description: Action details and status, with the affected titles listed
  • Color: Green for success, red for failure, blue for match changes and a created API key, amber for maintenance on and for a held deletion
  • Footer: “Librariarr Lifecycle”, “Librariarr Maintenance” or “Librariarr API Keys”
  • Timestamp: When the event occurred

Limitations

Section titled “Limitations”
  • Discord webhooks require a valid Discord channel with webhook permissions