Set Up Plex Notifications: Discord, Telegram, and Webhooks
Published 2026-10-16 · PlexBeam
Plex notifications tell you what is happening on your server without opening the Plex dashboard. When a user starts streaming, new media is added, or the server goes offline, a notification appears in your Discord server, Telegram chat, or any webhook-compatible service. This turns your phone into a real-time server monitor — you know instantly when someone is watching, when a new movie arrives, or when something breaks.
Notification methods compared
There are two ways to set up Plex notifications, and they serve different needs:
- Plex webhooks (built-in): Plex Pass includes a webhook system that sends JSON payloads to a URL when events occur — playback starts, playback stops, media is added, media is played. The webhook payload includes details like the title, user, player, and media quality. You need a service to receive and format these webhooks, since raw JSON is not human-readable
- Tautulli notifications (recommended): Tautulli is a free monitoring tool for Plex that includes a powerful notification system. It supports 20+ notification services out of the box — Discord, Telegram, Slack, Pushover, email, Gotify, ntfy, and more. Tautulli formats notifications with customizable templates, so you get clean messages with poster images, user names, and playback details. For most users, Tautulli is the easier and more flexible option
- Which to use: If you already run Tautulli (and you should — it is the best Plex monitoring tool), use its built-in notification agents. If you want notifications without installing Tautulli, Plex webhooks work but require more setup to format the output into readable messages
Setting up Discord notifications with Tautulli
Discord is the most popular notification destination for Plex server owners because many Plex communities already use Discord:
- Create a Discord webhook: In your Discord server, go to Server Settings, Integrations, Webhooks, and create a new webhook. Give it a name like "Plex Notifications" and select the channel where notifications should appear. Copy the webhook URL — you need it for Tautulli
- Configure Tautulli: In Tautulli, go to Settings, Notification Agents, and add a new agent. Select Discord from the list. Paste the webhook URL in the Discord Webhook URL field. Test the connection — Tautulli sends a test message to your Discord channel
- Choose triggers: Under the Triggers tab, select which events send notifications. Common choices: Playback Start (know when someone is watching), Recently Added (know when new media arrives), Plex Server Down/Up (know when the server crashes or restarts), Buffer Warning (know when users experience buffering). Enable only the triggers you care about — too many notifications become noise
- Customize the message: Under the Text tab, customize the notification template. Tautulli uses template variables like
{title},{user},{player},{quality_profile}, and{poster_url}. A good playback notification includes the title, user, device, and whether it is direct playing or transcoding. Include the poster URL for a rich embed with the movie or show artwork - Rich embeds: Discord supports rich embeds with images, colors, and formatted fields. Tautulli's Discord agent creates embeds automatically when you include a poster URL and fill in the embed fields. The result is a clean card in your Discord channel showing the poster, title, user, and playback details
Setting up Telegram notifications
Telegram is a good alternative if you prefer personal notifications over a shared Discord channel:
- Create a Telegram bot: Message @BotFather on Telegram and send
/newbot. Follow the prompts to name your bot. BotFather gives you an API token — save this for Tautulli - Get your chat ID: Send a message to your new bot, then visit
https://api.telegram.org/bot<your-token>/getUpdatesin a browser. Find thechat.idvalue in the response — this is your personal chat ID that tells the bot where to send messages - Configure Tautulli: Add a Telegram notification agent in Tautulli. Enter the bot token and chat ID. Select triggers and customize templates the same way as Discord. Telegram supports HTML formatting in messages, so you can use bold, italic, and links in your templates
- Group notifications: To send notifications to a Telegram group instead of a personal chat, add the bot to the group and use the group chat ID (which is a negative number). This lets multiple people see Plex notifications in a shared group
Using Plex webhooks directly
If you do not want to run Tautulli, Plex webhooks send event data to any URL you specify:
- Enable webhooks: In Plex Web, go to Settings, Webhooks. Add a webhook URL. Plex sends a JSON payload to this URL for every event (playback, library, server events). Webhooks require Plex Pass
- Webhook payload: Each event includes a JSON body with the event type, user information, media metadata (title, year, rating, thumb), player information (name, IP, platform), and server details. The payload is comprehensive but needs processing to extract useful information
- Webhook relay services: Services like Zapier, Make (Integromat), or n8n can receive Plex webhooks and forward formatted messages to Discord, Slack, email, or SMS. These services provide visual workflow builders that parse the JSON and create formatted notifications without writing code
- Self-hosted receiver: Write a simple webhook receiver in Python, Node.js, or any language. The receiver accepts POST requests from Plex, extracts the relevant fields, formats a message, and sends it to Discord or Telegram via their APIs. A basic receiver is under 50 lines of code and can run as a Docker container alongside Plex
Useful notification scenarios
Beyond basic playback alerts, notifications help with server administration:
- New user device: Tautulli can notify you when a user connects from a new device or IP address for the first time. This catches unauthorized access — if a friend shared their Plex credentials with someone else, you see the new device immediately
- Transcode alerts: Get notified when a stream starts transcoding, including the reason (subtitle, resolution mismatch, codec incompatibility). This helps identify users with suboptimal client settings and media files that need re-encoding
- Concurrent stream limits: Tautulli can notify you when a user exceeds a stream count threshold. If a user is sharing their credentials and you see 5 concurrent streams from different IPs, the notification alerts you to investigate
- Disk space warnings: While not a Plex notification per se, Tautulli's custom scripts feature can run a disk space check and send an alert when storage drops below a threshold. This prevents the common failure where Plex stops working because the drive is full
- Server downtime: Tautulli's Plex Server Down/Up triggers notify you immediately when the server becomes unreachable and again when it comes back online. The notification includes the downtime duration, so you know how long users were affected
Other notification services
Tautulli supports many notification destinations beyond Discord and Telegram:
- Pushover: A dedicated push notification service for mobile devices. Clean, fast notifications with priority levels, sounds, and quiet hours. Costs $5 one-time per platform (iOS, Android)
- ntfy: A free, self-hosted push notification service. Run your own ntfy server for complete control, or use the free public instance at ntfy.sh. Great for homelab users who prefer self-hosted solutions
- Slack: Works the same as Discord — create an incoming webhook in Slack and configure Tautulli to send messages to it. Good for teams that already use Slack for communication
- Email: Tautulli can send email notifications through any SMTP server. Useful for formal notifications like weekly server reports, but email is too slow for real-time alerts — push notifications are better for time-sensitive events
- Gotify: Another self-hosted notification server, simpler than ntfy. Android app only — no iOS support. Free and open source
Reducing notification noise
Too many notifications are worse than none because you start ignoring them:
- Selective triggers: Enable only the events you will actually act on. Playback start for every stream on a busy server generates dozens of notifications per day. Consider enabling playback start only for specific users or only during off-hours when you want to know who is using the server
- Conditions: Tautulli supports conditions on each trigger. For example, only notify on playback start if the stream is transcoding, or only notify on recently added if the media type is a movie (skip TV episode additions). Conditions filter out routine events and only alert on noteworthy ones
- Separate channels: Send different notification types to different Discord channels or Telegram chats. Put playback notifications in one channel and server alerts in another. This keeps administrative alerts visible instead of buried under playback updates
- Cooldown periods: Some notification agents support cooldown — a minimum time between notifications of the same type. This prevents notification floods when multiple users start streaming simultaneously or when a library scan adds many items at once