iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Antihost offers Linux VPS plans with full root access, unlimited traffic on a 1 Gbps port and a 14-day free trial.
Set up a custom Uptime Kuma notification from account menu → Settings → Notifications → Setup Notification (called Add New Notification in some releases). Choose a provider, enter its credentials or endpoint, use Test, save the channel, and then enable it on each monitor that should send alerts. A saved notification is not automatically attached to every monitor.
This guide covers Discord webhooks, Telegram bots, SMTP email, generic HTTP webhooks, provider selection, monitor assignment, testing, security, and the version differences that can change the fields you see.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
What a custom notification is in Uptime Kuma
Uptime Kuma separates a notification channel from a monitor. The channel stores the destination and delivery settings; the monitor decides whether that channel receives up and down events. You can create several channels—for example, a team-chat webhook, an email mailbox, and a Telegram bot—and select the appropriate ones per monitor.
Uptime Kuma supports native notification providers and additional services through Apprise. The project describes support for a wide range of notification services. Its README lists Telegram, Discord, Gotify, Slack, Pushover, Email (SMTP), and more than 90 services, but that count and the visible provider list are release-sensitive. Always use the provider list and field labels shown by your installed release rather than treating any list as permanent.
#1 Best Overall
- Includes Raspberry Pi 5 with 2.4Ghz 64-bit quad-core CPU (8GB RAM)
- Includes 128GB Micro SD Card pre-loaded with 64-bit Raspberry Pi OS, USB MicroSD Card Reader
- CanaKit Turbine Black Case for the Raspberry Pi 5
- CanaKit Low Noise Bearing System Fan
- Mega Heat Sink - Black Anodized
What you need before opening the form
Prepare the destination first. Uptime Kuma cannot create a Discord webhook, Telegram bot, mailbox, or receiving HTTP service for you.
- Uptime Kuma access: Sign in to the web interface with an account allowed to edit settings and monitors.
- A destination: Have a Discord webhook URL, Telegram bot token and chat ID, SMTP account and recipient details, or an HTTP endpoint that accepts the request Uptime Kuma will send.
- Network reachability: The Uptime Kuma host must be able to make an outbound connection to the provider or endpoint. Firewalls, DNS failures, proxies, and egress policies can prevent delivery even when the form is correct.
- A naming plan: Use a name that identifies both the destination and purpose, such as “Operations Discord” or “Critical email.” The name is what you will recognize when selecting a channel on a monitor.
- Secret handling: Treat bot tokens, webhook URLs, SMTP passwords, and endpoint credentials as secrets. Do not paste them into tickets, screenshots, public repositories, or monitor names.
Set up a notification channel
- Sign in to the Uptime Kuma web UI.
- Open the account menu in the top-right corner.
- Select Settings.
- Open Notifications.
- Click Setup Notification. Some versions label the same control Add New Notification.
- Choose the notification type from the provider list.
- Enter a friendly name. Choose a name that remains clear when several monitors and destinations are configured.
- Complete every provider field displayed by the form. Fields differ by provider and by Uptime Kuma release.
- Click Test before saving. Confirm that the destination receives the test message and that it arrives in the expected channel, mailbox, chat, or endpoint log.
- Click Save after the test succeeds.
The test checks whether Uptime Kuma can reach the destination with the supplied fields. It does not enable the channel on monitors; monitor assignment is a separate step.
Configure the main notification providers
Discord webhook
Discord is useful when a team already works from a shared channel and wants an event history visible to multiple people. Create and copy a webhook URL in the target Discord channel before starting the Uptime Kuma form.
- Choose Discord as the notification type.
- Enter a friendly name.
- Paste the pre-configured Discord webhook URL into the webhook field.
- If the form exposes them, set the bot display name and an optional prefix custom message. A prefix can identify the monitor group, environment, or severity in every notification.
- Click Test and verify that the message appears in the intended Discord server and channel.
- Click Save, then attach the saved channel to the monitors that should use it.
A webhook URL grants posting access to its Discord destination. Keep it private; if it is exposed, replace or revoke the webhook in Discord and update the Uptime Kuma notification.
Telegram bot
Telegram is suited to mobile-first alerts, but it requires bot credentials and a destination identifier. The Uptime Kuma Telegram form can include the bot token, chat ID, an optional message-thread ID, silent sending, and content-protection options.
Rank #2
- Includes Raspberry Pi 5 16GB with 2.4Ghz 64-bit quad-core CPU (16GB RAM)
- Includes 128GB Micro SD Card pre-loaded with 64-bit Raspberry Pi OS, USB MicroSD Card Reader
- CanaKit Turbine Black Case for the Raspberry Pi 5
- CanaKit Low Noise Bearing System Fan
- Mega Heat Sink - Black Anodized
- Choose Telegram.
- Enter a friendly name.
- Provide the bot token issued for the bot.
- Provide the destination chat ID. Use the ID for the conversation or group that should receive alerts, not merely a human-readable group name.
- If shown, enter a message-thread ID for a specific topic in a threaded chat.
- Choose whether to send silently and whether to enable content protection, according to how the destination should behave.
- Click Test and confirm receipt in the intended chat or thread.
- Save the notification and select it on the relevant monitors.
If a test fails, check the token, chat ID, bot permissions, and whether the bot can post to that conversation. These values are external to Uptime Kuma, so correcting them may require changing the Telegram conversation or bot configuration first.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →SMTP email
SMTP is the broadest mailbox option: it can reach recipients who do not use the same chat platform. Uptime Kuma’s SMTP fields can include username, password, sender, recipient, CC, BCC, and a custom subject.
- Choose Email (SMTP) or the equivalent SMTP provider label shown in your release.
- Enter a friendly name.
- Enter the SMTP username and password when the mail server requires authentication.
- Set the sender address and the primary recipient. Add CC or BCC recipients only when they should receive every message from this channel.
- Set a custom subject if you need a recognizable prefix for mailbox rules or on-call triage.
- Complete any server, port, or encryption fields presented by your installed version. TLS and port requirements are determined by the mail server; confirm them with that server’s administrator or documentation.
- Click Test and check the recipient inbox, spam folder, and mail-server logs if necessary.
- Save the channel and attach it to the monitors that need email delivery.
Do not assume that a successful connection means the message reached the inbox. A mail server can accept a message and later defer, reject, quarantine, or rate-limit it. For persistent delivery problems, inspect the SMTP server’s response and delivery logs.
Generic webhook
Use a generic webhook for an internal HTTP endpoint, an automation service, or an integration that is not represented by a dedicated provider. The API reference exposes fields for a webhook URL, custom body, content type, and additional headers.
- Choose the generic webhook provider.
- Enter a friendly name and the receiving endpoint URL.
- Set the custom body in the format the endpoint expects. Preserve valid JSON or other required syntax; Uptime Kuma will send what you configure.
- Choose the content type expected by the endpoint, such as the value required for JSON or form data.
- Add any additional headers needed for authentication, signatures, routing, or a tenant identifier. Keep authorization values secret.
- Click Test and inspect the receiver’s request log, response code, and parsed payload.
- Save the notification and select it on the required monitors.
The endpoint must accept both the HTTP method and payload shape used by the provider implementation. If your service expects a different schema, transform the request at an intermediary or use a provider-specific integration instead of assuming the endpoint will reinterpret it.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Rank #3
- CanaKit Raspberry Pi 5 Essentials Starter Kit
Other native and Apprise-backed services
The provider list can include native integrations and services exposed through Apprise. Select the service that matches your operational destination, then read every field in the form rather than copying settings from an older release. Native providers may expose richer, service-specific controls; Apprise-backed providers can add breadth while using different URL, credential, or formatting conventions.
Compare notification choices
| Provider type | Delivery destination | Setup dependency | Customization shown in the documented fields | Best operational fit |
|---|---|---|---|---|
| Discord | Shared team chat | Pre-configured Discord webhook URL | Friendly name, optional bot display name, optional prefix message | Team-visible incident history and channel-based triage |
| Telegram | Mobile chat or bot conversation | Bot token and chat ID | Optional message-thread ID, silent sending, and content-protection controls | Mobile-first personal or group alerts |
| SMTP email | Mailbox | Mail-server/account settings and recipient fields | Username, password, sender, recipient, CC, BCC, and custom subject; server TLS and port depend on the mail system | Universal mailbox reach, archives, and mail rules |
| Generic webhook | HTTP endpoint or automation pipeline | Endpoint URL and whatever authentication the receiver requires | Custom body, content type, and additional headers | Internal systems, automation, and custom processing |
| Other native or Apprise-backed provider | Provider-specific | Fields defined by the selected integration | Release- and provider-specific | Destinations not covered by the four common configurations |
Choose based on the destination your responders actually monitor. A channel with elaborate formatting is not useful if nobody watches it; conversely, email may be the right fallback when chat access is restricted. You can create separate channels for primary and backup delivery and assign both to a monitor.
Attach the notification to monitors
Saving a channel only stores its configuration. To generate alerts, open each monitor that should use it and enable or select the saved notification in that monitor’s notification settings.
- Open the monitor from the Uptime Kuma dashboard.
- Open the monitor’s edit view.
- Find the notification selection area.
- Enable or select the saved channel by its friendly name.
- Save the monitor.
- Repeat for every monitor that needs the channel.
Review this assignment whenever you clone, import, or create monitors. A notification can test successfully while a monitor remains unassigned, which produces no alert for that monitor.
Test the complete path
Use two checks rather than treating the provider test as the whole verification process.
Rank #4
- All-in-One Complete Kit: This SANOOV RPi 5 bundle comes with Raspberry Pi 5 4GB RAM single board, active cooler, durable ABS case and screwdriver. No extra parts needed, ready to use right out of the box for beginners and hobbyists
- Powerful Single Board Computer: Equipped with 4GB RAM and high-performance processor, delivers fast running speed for 4K playback, AI projects, programming and daily computing tasks. SANOOV for raspberry pi 5 4GB is equipped with broadcom 64 quad-core Arm Cortex A76 processor with gigabit ethernet and upgraded with IEEE 802.11ac Wi-Fi, Bluetooth 5.0 dual-band 2.4Ghz and 5Ghz and Power Over Ethernet (POE). Upgrading delivers 2-3 x speed vs Pi 4, redefining the experience
- Efficient Active Cooler: Effectively lowers operating temperature and prevents performance throttling. Runs quietly even under long-time heavy load, ensures stable operation all day long. SANOOV RPi 5 4GB kit offer an active cooler, which combines an aluminium heatsink with a high-performance PWM fan. Active cooler is fully compatible with the Pi OS, which can effectively reduce the temperature of RPi5 and ensure its good performance during long-term high load operation
- Sturdy ABS Protective Case: Well-fitted for Raspberry Pi 5 board, can be secured with 4 screws to effectively protect the Pi 5 motherboard from damage, reserves full access to all ports and buttons. SANOOV uses ABS material to produce the case, which has a softer texture and feel. Meanwhile, SANOOV case adopts a layered design for easy disassembly and installation. (Tip: The Case cannot install M.2 HAT Add on Board and Solid State Drive!)
- Wide Application & Full Compatibility: Seamlessly compatible with official OS and mainstream peripheral accessories for Raspberry Pi 5. Whether you are a beginner, student, electronics hobbyist or professional developer, this all-in-one kit meets your diverse needs. It excels in IoT projects, robotics design, retro gaming devices, home media servers and other DIY creations. Backed by a large global community, you can easily find guides, technical support and shared projects online
Check the channel
From Settings → Notifications, open the channel and use Test. Confirm the destination receives the message and that it contains the expected sender, subject, channel, thread, or payload. For a generic webhook, inspect the receiving service’s request log and response handling.
Check the monitor assignment
Open a monitor configured to use the channel and verify that the notification is enabled in its monitor-level settings. A passing channel test proves destination reachability with the stored fields; it does not prove that every monitor is configured to send through that channel.
Observe real event handling safely
Do not create an outage on a production service merely to test alerting. If your operating procedure provides a maintenance monitor or a controlled test endpoint, use that. Otherwise, verify the channel test, monitor assignment, and provider logs without intentionally disrupting a user-facing service.
Recommended Free Tools
Troubleshoot notifications that do not arrive
The Test control reports an error
- Recheck every credential, token, URL, chat ID, recipient, and required field for accidental whitespace or a truncated value.
- Confirm that the Uptime Kuma host can resolve and reach the destination over the required network path.
- For SMTP, confirm the server’s port, TLS mode, authentication policy, sender restrictions, and account status with the mail administrator.
- For a webhook, verify that the endpoint is listening, the URL path is correct, and the configured content type, body, and headers match what it accepts.
- For Discord or Telegram, verify that the webhook or bot still exists and has permission to post to the selected destination.
The Test succeeds, but a monitor sends nothing
- Open the monitor and confirm that the saved notification is selected.
- Check that you edited the intended monitor rather than another monitor with a similar name.
- Verify the monitor’s notification behavior and event state; a monitor that has not changed state may not generate the event you expect.
- Review Uptime Kuma logs and the external provider’s logs for rejected, rate-limited, or malformed requests.
Messages are delayed, rejected, or incomplete
- Check provider rate limits and temporary service failures.
- Look for mail-server deferrals, spam quarantine, or sender-policy failures when using SMTP.
- Inspect webhook responses and payload parsing when using an HTTP endpoint.
- Confirm that a Telegram thread ID points to an existing topic and that silent sending has not made an alert appear less prominently than expected.
- For Discord, verify that the webhook still targets the channel you intended and that its permissions were not changed.
A provider or field is missing
Provider availability and field names change between Uptime Kuma releases. Check the installed release’s notification list and use the current form labels. A service listed in an older guide may have moved, changed fields, or be available through Apprise rather than as a native provider.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Secure and maintain notification channels
- Protect secrets: Webhook URLs, bot tokens, SMTP passwords, and authorization headers should be handled like passwords. Redact them from screenshots and logs.
- Use least privilege: Give a webhook, bot, mailbox account, or endpoint credential only the permissions needed to deliver alerts.
- Separate destinations: Use different channels for development, staging, and production so a test cannot confuse on-call staff with a production incident.
- Review recipients: Recheck primary recipients, CC, BCC, chat membership, and webhook targets when team responsibilities change.
- Retest after changes: Run the built-in test after rotating a token, changing a mail password, moving a Discord channel, changing an endpoint, or upgrading Uptime Kuma.
- Document ownership: Record who owns each destination and when it was last verified, without recording the secret itself.
- Plan a fallback: Critical monitors can use two independently managed channels, such as team chat plus SMTP, so one provider outage does not remove every alert path.
Choose a practical setup
Small personal deployment
Start with one mobile or mailbox destination that you check consistently. Keep the friendly name specific to the deployment and attach it only to monitors whose failures require immediate attention.
Best Value
- 【What you Get】You will get 1*Pi 5 8GB Single Board,1*RasTech Case,1*Active Cooler,1*Screwdriver,1*Installation instructions,12-month free warranty, lifetime service, 24-hour prompt and friendly response.
- 【More Connectors】There are two USB 3.0 ports(5Gbps simultaneously) and two USB 2.0 ports, which triple total bandwidth ,support any combination of up to two cameras or displays. Peak SD card performance is doubled through support for the SDR104 high-speed mode. It provides a smooth desktop experience for you. Offer Gigabit Ethernet and a PCIe interface, along with dual-band Wi-Fi and Bluetooth 5.0/BLE wireless capability. The RasTech Pi 5 Kit use the new 27W 5.1V 5A USB-C power connector.
- 【 Support Dual 4Kp60 Display 】Each of the two microHDMI sockets can control a 4K display at 60 Hertz, now support HDR, offering super HD video for media streaming projects. RPi 5 is the first RPi model that comes with a PCI Express port (PCIe 2.0 x1 with 500 MB/s) to attach SSDs (requires separate M.2 HAT).
- 【 Excellent Chips And Applications】Pi 5 is a full-size Pi computer using silicon built in-house at Pi. The RP1 “southbridge” provides the bulk of the I/O capabilities for Pi 5. Pi 5 is more friendly and convenient in the development of Internet of Things, Web development, machine identification, automatic control and other electronic equipment applications and network.
- 【 Faster CPU, Better GPU 】 Pi 5 features a Broadcom BCM2712 64-bit quad-core Arm Cortex-A76 processor running at 2.4GHz, it delivers a 2–3× increase in CPU performance relative to RaspberryPi 4. The 800MHz VideoCore VII GPU is compatible to OpenGL ES 3.1 and Vulkan 1.2, substantial uplift in graphics performance. Pi 5 Offers lightning-fast CPU speed, a PCI Express interface, a Real Time Clock (RTC) and a power button and runs significantly cooler than Pi 4.
Shared operations team
Use a shared chat destination for visible incident history and add SMTP as a fallback when mailbox delivery is part of your escalation process. Create separate channels for production and non-production monitors to avoid mixing urgency levels.
Automation-heavy environment
Use a generic webhook when another service must transform, route, or enrich events. Define the expected payload, content type, and authentication contract before entering custom body and header values, then verify the receiver’s logs during the test.
Many services and changing requirements
Keep provider selection release-aware. Native integrations may expose service-specific options, while Apprise-backed choices can broaden coverage. Revisit the form after upgrades instead of assuming that an older provider list or field name still applies.
When the setup is complete
A dependable configuration has four verified parts: the provider destination exists, the Uptime Kuma channel passes its built-in test, each intended monitor has that channel enabled, and the destination owner knows how to respond to an alert. Treat those as separate checks whenever you add a monitor, rotate credentials, change providers, or upgrade Uptime Kuma.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
