Seerr

Process webhook notifications from Seerr with contextual priority, media details, and action links.

Input Handling

For JSON object inputs, the full parsing pipeline is used. For string inputs, the interpreter attempts JSON parsing — if it fails, a fallback notification is created with title [Seerr] Notification, the raw string as the body, priority 3, and tags seerr and movie_camera.

Binary inputs are decoded as UTF-8 and parsed as JSON (no fallback on parse failure).

Supported Events

Unrecognized event types are handled at priority 3 (default).

Payload Fields

The interpreter extracts:

• notification_type — Determines priority and notification style.
• event, subject, message — Used for title and body.
• image — Used as the notification icon if present.
• media.media_type, media.tmdbId, media.status — Used for media details and TMDB action link.
• request.requestedBy_username — Shows who made the request.
• issue.issue_type, issue.reportedBy_username — Shows issue details.
• comment.comment_message, comment.commentedBy_username — Shows comment details.

Notification Output

• Title: [Seerr] {event} (e.g., [Seerr] Media Available).
• Body: Markdown-formatted with subject, message, requester/reporter, and comment if applicable.
• Priority: Based on notification type (see table above).
• Tags: Includes seerr and an emoji tag.
• Actions: Links to TMDB page and Seerr dashboard (if ntfy-reverse-proxy.url is provided).

Custom Fields

Add an ntfy-reverse-proxy object with a url field pointing to your Seerr instance for a dashboard action link:

{
  "notification_type": "MEDIA_AVAILABLE",
  "event": "Media Available",
  "subject": "The Matrix (1999)",
  "ntfy-reverse-proxy": {
    "url": "https://seerr.example.com"
  }
}