Classic Template

Modern Template

Screenshots captured using the Element Matrix client.

Server URL

• The server url of your jellyfin. This will be used for direct link in discord webhook.

Community Rating Decimal Places

• Configure the number of decimal places to display for community ratings in newsletters (0-4 places, default: 1)

Poster Type

• TMDB Poster - Uses image URLs from TheMovieDB (default, smallest emails).
• Local Poster Images - Embeds local poster images directly in the email/discord embed (larger messages).

Radarr / Sonarr Configuration

You can configure multiple Radarr and Sonarr instances. Each instance has its own URL, API key, and instance name. The plugin uses these to fetch upcoming media via the Radarr/Sonarr calendar APIs.

Instance Name

• A name for this Radarr/Sonarr instance. This name appears as the section header in the upcoming media portion of your newsletter.

URL

• The base URL of your Radarr/Sonarr instance (e.g., http://localhost:7878 for Radarr, http://localhost:8989 for Sonarr).

API Key

• The API key for your Radarr/Sonarr instance. Found under Settings → General → API Key in the respective application.

Test Connection

• Use the "Test" button to verify connectivity to your Radarr/Sonarr instance before saving.

Upcoming Days Ahead

• Configure how many days ahead to look for upcoming content (default: 7 days). This is a global setting shared across all Radarr/Sonarr instances.

You can configure Multiple Email Clients. Each client instance has its own SMTP settings, recipients, library selection, event triggers, template settings, and an enable/disable toggle.

To Addresses:

• Recipients of the newsletter. Add as many emails as you'd like, separated by commas.
  • All emails will be sent out via BCC

From Address

• The address recipients will see on emails as the sender
  • Defaults to JellyfinNewsletter@donotreply.com

Subject

• The subject of the email

Smtp Server Address

• The email server address you want to use.
  • Defaults to smtp.gmail.com

Smtp Port

• The port number used by the email server above
  • Defaults to gmail's port (587)

Enable SSL

• Toggle SSL/TLS encryption for the SMTP connection (default: enabled). Disable this if your SMTP server does not support or require SSL.

Smtp Username

• Your username/email to authenticate to the SMTP server above

Smtp Password

• Your password to authenticate to the SMTP server above
  • I'm not sure about other email servers, but Google requires a Dev password to be created.
    • For gmail specific instructions, you can visit https://support.google.com/mail/answer/185833?hl=en for details

Library Selection

• Choose specific libraries within each item type (Movies/Series) to include in newsletters for this email client.

Newsletter Event Settings

• Configure which library events (Add/Update/Delete/Upcoming) should trigger the newsletters for this email client:
  • Add: Enable newly added items section in the newsletter (default: enabled).
  • Update: Enable updated items section in the newsletter. Updates are detected when media files are upgraded (e.g., by tools like Radarr/Sonarr), where the old file is deleted and a new one is added with the same title/season/episode information (default: disabled).
  • Delete: Enable deleted items section in the newsletter (default: enabled).
  • Upcoming: Enable upcoming media section in the newsletter, sourced from Radarr/Sonarr (default: disabled).

Newsletter Template Category

You can select between different email templates:

• Modern: A sleek, card-based design. Fully compatible for mobile view.
• Classic: A more traditional list-based layout.

Body HTML

• Define custom HTML structure for the main email body. If left empty, the default HTML from the selected Newsletter Template Category will be used.

EntryData HTML

• Define custom HTML formatting for each individual media item (Movies/Series) in the newsletter. If left empty, the default HTML from the selected Newsletter Template Category will be used.

Header HTML

• Define custom HTML for section headers (e.g., "Added to Movies", "Removed from Series"). The template uses <template> tags with IDs to define all four event-type headers in a single file:
  • <template id="header-add"> - Header for newly added items
  • <template id="header-update"> - Header for updated items
  • <template id="header-delete"> - Header for deleted items
  • <template id="header-upcoming"> - Header for upcoming items
• Placeholder: {LibraryName} - replaced with the library name (e.g., "Movies", "TV Shows")
• If left empty, the default header template from the selected Newsletter Template Category will be used.

You can now configure Multiple Discord Clients. Each client instance can have its own Webhook URL(s), library selection, event triggers, and an enable/disable toggle.

Webhook URL

• Your discord webhook url. Supports multiple webhooks: You can enter multiple webhook URLs separated by commas , to send the same notification to multiple channels.

Webhook Name

• Name for your discord webhook, defaults to "Jellyfin Newsletter"

Library Selection

• Choose specific libraries within each item type (Movies/Series) to include in newsletters for this Discord client.

Newsletter Event Settings

• Configure which library events (Add/Update/Delete/Upcoming) should trigger Discord notifications:
  • Add: Enable newly added items section in the newsletter (default: enabled).
  • Update: Enable updated items section in the newsletter. Updates are detected when media files are upgraded (e.g., by tools like Radarr/Sonarr), where the old file is deleted and a new one is added with the same title/season/episode information (default: disabled).
  • Delete: Enable deleted items section in the newsletter (default: enabled).
  • Upcoming: Enable upcoming media section in the newsletter, sourced from Radarr/Sonarr (default: disabled).

Fields & Color selection

• Select the fields that you want as part of your embed.
• Select the embed color for each event type (Add, Update, Delete) and item type (Series, Movies).

You can now configure Multiple Telegram Clients. Each client instance can have its own Bot Token/Chat IDs, library selection, event configurations, and an enable/disable toggle.

Bot Token:

• Your Telegram bot token obtained from BotFather

Chat ID:

• The chat ID(can be a user ID, group ID, or channel ID) where you want to send the newsletters. Supports multiple Chat IDs: You can enter multiple Chat IDs separated by commas ,.

Library Selection

• Choose specific libraries within each item type (Movies/Series) to include in newsletters for this Telegram client.

Newsletter Event Settings

• Configure which library events (Add/Update/Delete/Upcoming) should trigger Telegram notifications:
  • Add: Enable newly added items section in the newsletter (default: enabled).
  • Update: Enable updated items section in the newsletter. Updates are detected when media files are upgraded (e.g., by tools like Radarr/Sonarr), where the old file is deleted and a new one is added with the same title/season/episode information (default: disabled).
  • Delete: Enable deleted items section in the newsletter (default: enabled).
  • Upcoming: Enable upcoming media section in the newsletter, sourced from Radarr/Sonarr (default: disabled).

Fields selection

• Select the fields that you want as part of your message.

You can configure Multiple Matrix Clients. Each client instance can have its own Homeserver URL, Access Token, Room ID(s), library selection, event configurations, and an enable/disable toggle.

Homeserver URL

• The URL of your Matrix homeserver (e.g., https://matrix.org or your self-hosted instance URL).

Access Token

• The access token for your Matrix bot/user account. This is used to authenticate API requests to the homeserver.

Room ID

• The Room ID where newsletters will be sent (e.g., !roomid:matrix.org). You can find this in your Matrix client's room settings. Supports multiple Room IDs: You can enter multiple Room IDs separated by commas ,.

Test Message

• Use the "Test" button to send a test message and verify your Matrix configuration before saving.

Library Selection

• Choose specific libraries within each item type (Movies/Series) to include in newsletters for this Matrix client.

Newsletter Event Settings

• Configure which library events (Add/Update/Delete/Upcoming) should trigger Matrix notifications:
  • Add: Enable newly added items section in the newsletter (default: enabled).
  • Update: Enable updated items section in the newsletter. Updates are detected when media files are upgraded (e.g., by tools like Radarr/Sonarr), where the old file is deleted and a new one is added with the same title/season/episode information (default: disabled).
  • Delete: Enable deleted items section in the newsletter (default: enabled).
  • Upcoming: Enable upcoming media section in the newsletter, sourced from Radarr/Sonarr (default: disabled).

Newsletter Template Category

• Currently, one template is available:
  • Matrix: An HTML-based template designed for Matrix clients with HTML rendering support (e.g., Element).

Body HTML

• Define custom HTML structure for the main message body. If left empty, the default HTML from the selected Newsletter Template Category will be used.

EntryData HTML

• Define custom HTML formatting for each individual media item (Movies/Series) in the newsletter. If left empty, the default HTML from the selected Newsletter Template Category will be used.

Header HTML

• Define custom HTML for section headers (e.g., "Added to Movies", "Removed from Series"). The template uses <template> tags with IDs to define all four event-type headers in a single file:
  • <template id="header-add"> - Header for newly added items
  • <template id="header-update"> - Header for updated items
  • <template id="header-delete"> - Header for deleted items
  • <template id="header-upcoming"> - Header for upcoming items
• Placeholder: {LibraryName} - replaced with the library name (e.g., "Movies", "TV Shows")
• If left empty, the default header template from the selected Newsletter Template Category will be used.

- {Date} - Auto-generated date (yyyy-MM-dd format)
- {d} - Day of the month (e.g. 9, 23)
- {dd} - Zero-padded day of the month (e.g. 09, 23)
- {day} - Full day name (e.g. Wednesday)
- {dy} - Short day name (e.g. Wed)
- {m} - Month of the year (e.g. 4, 11)
- {mm} - Zero-padded month (e.g. 04, 11)
- {month} - Full month name (e.g. April)
- {mon} - Short month name (e.g. Apr)
- {yy} - Two-digit year (e.g. 26)
- {yyyy} - Four-digit year (e.g. 2026)

- {prevDate} - Date of previous newsletter (legacy yyyy-MM-dd format)
- {prevd} - Day of the month of previous newsletter (e.g. 9, 23)
- {prevdd} - Zero-padded day of the month of previous newsletter (e.g. 09, 23)
- {prevday} - Full day name of previous newsletter (e.g. Wednesday)
- {prevdy} - Short day name of previous newsletter (e.g. Wed)
- {prevm} - Month of the year of previous newsletter (e.g. 4, 11)
- {prevmm} - Zero-padded month of previous newsletter (e.g. 04, 11)
- {prevmonth} - Full month name of previous newsletter (e.g. April)
- {prevmon} - Short month name of previous newsletter (e.g. Apr)
- {prevyy} - Two-digit year of previous newsletter (e.g. 26)
- {prevyyyy} - Four-digit year of previous newsletter (e.g. 2026)