Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemsUptime Kuma notifications are configured as reusable channels, then selected on the monitors that should use them. The normal path is account menu → Settings → Notifications → Setup Notification (shown as Add New Notification in some releases). Choose a provider, enter its credentials or endpoint, send a test, save the channel, and enable it on each relevant monitor.
Antihost offers Linux VPS plans with full root access, unlimited traffic on a 1 Gbps port and a 14-day free trial.
Uptime Kuma includes native notification providers and additional Apprise-backed services. Because the provider list and form fields change between releases, use the options displayed by your installed version rather than relying on an old list of providers.
As an Amazon Associate I earn from qualifying purchases.
What a custom notification is in Uptime Kuma
A custom notification is an integration record in Uptime Kuma. It tells the monitoring server where to send an outage, recovery, or other monitor event and which provider-specific settings to use. It is not a separate hardware product and does not require a special physical device.
You create the channel once, give it a recognizable name, and attach it to one or more monitors. A single channel can therefore serve several monitors, while different channels can route different services to different destinations.
#1 Best Overall
- [Ultra-Lightweight Ear Buds Designed for Small Ears] Each earbud weighs only 3.7g and features a compact, ergonomic in-ear design made especially for small ears. Secure, low-profile, and comfortable for workouts, all-day wear or overnight sleeping.The ultra-slim profile sits flush in your ear with no hard edges poking or rubbing, so you can even sleep on your side without discomfort.
- [Immersive Stereo Sound with TOZO OrigX Technology] TOZO OrigX tuning delivers clear vocals, balanced mids, and natural stereo sound for music, podcasts, and videos.
- [Long Battery Life for Daily Use] Get up to 7 hours of playtime on a single charge, with up to 32 hours total using the charging case—ideal for workdays, commuting, and extended listening sessions.
- [Bluetooth 5.3 & Stable Connection] Bluetooth 5.3 provides fast pairing, stable wireless performance, and reduced dropouts as you move around home or office.
- [Deep Bass with Clear Vocals] High-performance drivers produce punchy bass while keeping vocals clean and detailed for everyday listening.
The project wiki describes Uptime Kuma as supporting a wide range of notification services. Its README names Telegram, Discord, Gotify, Slack, Pushover, Email through SMTP, and more than 90 services. The exact count, provider list, and available fields are release-sensitive, so the installed interface is the authority for your deployment.
Before you begin
- Make sure you can sign in to the Uptime Kuma web interface with an account allowed to change settings.
- Decide which destination should receive alerts: a team chat, an email inbox, a mobile messaging bot, or an HTTP endpoint used by an automation system.
- Prepare the provider information before opening the form. Depending on the provider, this may be a webhook URL, bot token and chat ID, SMTP account details, or an authenticated endpoint.
- Keep tokens, webhook URLs, passwords, and access keys private. Anyone who obtains a webhook or bot credential may be able to send messages or access the associated service.
- Confirm that the Uptime Kuma host can make outbound connections to the provider. A correctly filled form cannot deliver messages if firewall, DNS, proxy, or routing rules block egress.
Universal setup procedure
- Sign in. Open the Uptime Kuma web UI and authenticate.
- Open the account menu. Use the menu in the top-right corner.
- Go to Settings. Select Settings, then open the Notifications section.
- Start a channel. Click Setup Notification. Some versions label the same action Add New Notification.
- Choose a type. Select the provider that matches your destination. The form changes immediately to show that provider’s fields.
- Name the channel. Enter a friendly name such as “Operations Discord” or “Critical-email”. Use a name that remains understandable when it appears in a monitor’s notification selector.
- Complete the provider fields. Enter only the values required by the selected form. Do not paste credentials into a field intended for a display name or message prefix.
- Test before saving. Click Test and check the destination for the test message. If the provider offers a thread, silent, or formatting option, verify the result in the intended location.
- Save the channel. After the test succeeds, click Save.
- Attach it to monitors. Open each monitor that should use the channel and enable or select the saved notification in that monitor’s notification settings. Saving a channel alone does not subscribe every monitor to it.
The test checks whether Uptime Kuma can reach the configured destination with the supplied fields. It does not prove that every monitor is enabled for that channel, nor does it guarantee that a provider will accept every future request.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Discord notifications
What Discord requires
Discord setup starts outside Uptime Kuma: create and configure a Discord webhook for the server channel where alerts should appear. Copy the resulting webhook URL and treat it as a secret.
Configure the channel
- Follow the universal path to Settings → Notifications → Setup Notification.
- Select Discord from the notification type list.
- Enter a friendly name and paste the Discord webhook URL.
- If your release shows them, set the bot display name and an optional prefix custom message. A prefix can identify the monitored environment or add a short context before Uptime Kuma’s event text.
- Click Test and confirm that the message appears in the intended Discord server and channel.
- Click Save, then select this notification on the monitors that should post there.
If a test fails, recreate or recopy the webhook in Discord, check for an accidental space or truncated URL, and verify that the webhook still belongs to a channel where it is allowed to post. A successful test followed by missing outage messages usually means the channel was not enabled on the affected monitor.
Rank #2
- 【IP68 Waterproof Multifunctinal Smart Watch】Torjalph fitness activity tracker smart watch is IP68 waterproof technology ,you can wear it when swimming,handwashing,it's rain-proof which means that you perform multiple exercise modes outside without worrying about sweat or rain corroding your fitness smart watch,and this watch equipped with a 230 mAh large capacity battery magnetic charging ,and this sports activity tracker watch can be used 5-7 days If fully charged.
- 【Larger 1.83'' Full Screen Watch & Multi-dial Selection】1.83 inch full HD color touch screen smart watch for men / women provides excellent 240*284 resolution image quality ,This Bluetooth smart watch offers a better touch experience and remarkable immersion and ,more than 200 watch faces for you to choose from App"Da Fit ", you can change the dial style according to your mood to wear keeping the world on your wrist
- 【Accurate Activity Tracker Smart Watch 】sports watch activity tracker uses sweat and dust resistant breathable silicone strap, our Fitness Tracker Smart Watch for Android iOS Phones supports 12 sports modes,walking,running,bicycle,swimming,badminton,basketball,football,rope skipping. This bluetooth calls smart watch for men women is lightweight and stylish, bringing more convenient and relaxing sports experience while also providing more protection.
- 【Your 24 Hour Personal Daily Health Monitor】Fitness watch for women men full touch screen IP67 waterproof bluetooth smartwatch for Android iOS Phones with heart rate blood pressure monitor multifunction Andriod smart watch with steps counter sleep monitor sports fitness watch, monitoring blood oxygen saturation allows you to understand your physical condition in real time to track fitness progress ,to know your health status in time.
- 【More Functions Bluetooth Call Smart Watch】This fitness activity smart watch full screen for iPhone and Android phones includes a bunch of new features including:The bluetooth smart watch can hang up the phone, receive and display WhatsAPP /Text /Facebook /Twitter /Messenger reminder.Support sedentary reminder, alarm clock, stopwatch, timer,weather information,music control, remote camera control compatible with Android 5.0 and above or iOS 9.0 and above smartphones.
Telegram notifications
Credentials and destination
Telegram uses a bot token and a chat ID. The bot must be able to send messages to the target chat. A group, private conversation, or channel can have a different chat ID, so use the ID for the exact destination you intend to monitor.
Configure Telegram
- Open the notification setup form and choose Telegram.
- Enter a friendly name, the bot token, and the chat ID shown by the form.
- If available in your release, provide a message-thread ID to route messages to a particular topic in a forum-style group.
- Choose whether to send silently if the form offers a silent-sending option. Silent delivery changes notification behavior on the Telegram side; it does not disable Uptime Kuma events.
- Review the content-protection option if present. This affects how Telegram handles message forwarding or saving and should match your organization’s policy.
- Use Test, confirm receipt in the correct chat or thread, then save and attach the notification to monitors.
A valid bot token with an incorrect chat ID can produce a failed test or deliver to an unintended destination. If the token is ever exposed, revoke or replace it through the bot-management process and update Uptime Kuma.
Recommended Free Tools
SMTP email notifications
Information the form may request
The SMTP form can include a username, password, sender address, recipient address, CC, BCC, and custom subject. These fields describe both authentication and the envelope of the outgoing message. The mail server’s hostname, port, encryption mode, relay policy, and certificate requirements are external SMTP settings; use the values required by your mail provider or internal mail server.
Configure email
- Select Email (SMTP) or the equivalent SMTP notification type displayed by your release.
- Enter a friendly name for the channel.
- Provide the SMTP account username and password if the server requires authentication.
- Set the sender and at least one recipient. Add CC or BCC only when those copies are intentional and permitted by your alert policy.
- Enter a custom subject if you need a routing prefix or environment label. Keep the subject recognizable to people and mail rules.
- Apply the SMTP server’s required host, port, and TLS-related values wherever the form exposes them. If a value is not present in Uptime Kuma’s form, configure it in the mail service or consult that service’s current requirements.
- Click Test. Check the recipient mailbox, junk folder, and server-side mail logs if the message does not appear.
- Save the channel and enable it on the relevant monitors.
A passed Uptime Kuma test means the configured request reached the mail handoff as far as Uptime Kuma could verify. It does not override a provider’s later spam filtering, relay rejection, quota limit, or rate limit.
Rank #3
- [Low Noise High Fidelity] New bee guitar cord with 22AWG oxygen-free-copper center conductors provides enhanced signal transfer, the PVC insulation material and the high-density stranded copper double shield provide noise rejection for quiet operation
- [Ideal for Choice] New bee 1/4 straight and right angle metal connectors, ensures a secure connection in any instrument, pedal, or amp jack. L shape great fro on stage guitar stands
- [Wide Compatible] Suitable for mixer, power amplifier, microphone, effector, decoder, equalizer, electoronic organ, electric guitar, electric bass and other electronic equipments. Widely used in the installation of smart home, karaoke speaker, professional stage audio, etc
- [Easy Disassemble] Making incidental repairs quick and easy! Very nice, flexible cable
- [Dont Hesite to Order] 24 hours customer services and professional technology team are standing by
Generic webhook notifications
When to use a webhook
Choose a generic webhook when an internal HTTP service, incident pipeline, serverless function, or automation platform accepts an HTTP request instead of a native Uptime Kuma provider. The receiving endpoint must understand the method and payload that Uptime Kuma sends and must authenticate the request in the way you configure.
Fields and payload decisions
The webhook API exposes a webhook URL, custom body, content type, and additional headers. Use the URL for the endpoint, select a content type that the endpoint parses, and provide a body in the syntax expected by that endpoint. Add authentication headers only when the receiving service requires them, and avoid putting long-lived secrets into a body that may be logged.
- Select the generic webhook notification type.
- Enter a descriptive name and the endpoint URL.
- Set the content type and custom body according to the endpoint’s contract.
- Add only the required headers, including authentication or an idempotency value if the receiving service documents one.
- Click Test and inspect both the destination and its server logs. A successful HTTP response does not necessarily mean that downstream automation completed.
- Save the channel and select it on each monitor that should trigger the workflow.
For an internal endpoint, test with a non-destructive action first. Make sure the endpoint can distinguish a test event from a real outage if triggering an automated remediation would be unsafe.
Choosing the right notification type
| Option | Delivery destination | Setup dependency | Customization shown by the form | Best operational fit |
|---|---|---|---|---|
| Discord | Team chat channel | Pre-configured Discord webhook URL | Friendly name, webhook URL, optional bot display name and prefix message | Shared team history and collaborative outage response |
| Telegram | Bot conversation, group, or channel | Bot token and chat ID | Optional message-thread ID, silent sending, and content-protection settings where available | Mobile-first delivery and targeted conversations |
| SMTP email | Mailbox | Mail-server and account details, plus sender and recipient information | Username, password, sender, recipient, CC/BCC, and custom subject fields | Broad reach, archiving, and existing mail rules |
| Generic webhook | HTTP endpoint or automation service | Endpoint URL and whatever authentication the endpoint requires | Custom body, content type, and additional headers | Incident pipelines, internal tools, and custom automation |
| Other native or Apprise-backed service | Provider-specific destination | Fields defined by the installed release and provider | Varies by provider and release | Use when a native integration or Apprise service matches your existing workflow |
Native integrations generally expose fields designed for that service. Apprise-backed integrations broaden the available destinations, but their exact names and options can change as Uptime Kuma and Apprise versions change. Prefer the provider that minimizes credential sprawl and gives the response team a dependable delivery path.
Rank #4
- Digital Family Calendar: BSIMB digital calendar wall touch screen puts an end to your chaotic life. Designed for busy families, the digital calendar keeps you organised and in step with your family. Assign different colours and tasks to each family member to make family scheduling easier and more intuitive.
- Easy Setup and Auto-Sync: Plug in, connect to WLAN and auto-syn your electric calendar in minutes. Digital wall calendar compatible with Google calendar, iCloud calendar, Outlook calendar, Cozi calendar and Yahoo calendar. Add events directly on the device or through the ecalendar app. Electronic calendar stays current whether you're at work or traveling—no manual updates needed.
- All-In-One Home Assistant: Smart calendar builds habits and encourage independence with personalised chores. Display daily meal plan to reduce the daily ‘What's for dinner?’ stress. To-do lists keep track of everything you want. Turning chores into valuable achievements with stars and rewards, making life easier and more enjoyable.
- Manage Anytime Anywhere: BSIMB electronic calendar for family stay connected with the powerful ecalendar app. Access and manage your digital wall calendar anytime, anywhere with free features like stars & rewards, photo screensaver, chore charts, meals plans, to-do lists etc. Electronic planner paid features like Magic Import tailor advanced tools for users with special needs.
- Stay in Touch with Loved Ones: Share photos or videos from your phone to electronic wall calendar with app, instantly update your life moment, and keep in touch with your family, especially those who are far away; you can also surprise your smart calendar digital wall by sending him a wish card; it's also great for keeping tech-illiterate elders in touch with the youngsters.
Attach notifications to monitors correctly
Notification records and monitor subscriptions are separate settings. After saving a channel, open a monitor, locate its notification controls, and enable or select the channel. Repeat this for every monitor that should use it.
- Use a clear channel name so monitor-level selectors are unambiguous.
- For critical services, select more than one independent destination only if your team can respond to both and the additional noise is acceptable.
- For low-priority checks, avoid automatically reusing a high-urgency channel if it will create unnecessary interruptions.
- After changing a monitor’s notification selection, save the monitor and verify that the selection remains enabled when you reopen it.
A notification test validates the channel configuration. To validate the complete path, test the channel, confirm its monitor subscription, and then perform a controlled monitor event only when doing so is safe for your environment.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteSecurity and maintenance
Protect secrets
- Restrict access to the Uptime Kuma administration account and the host storing its configuration.
- Do not publish webhook URLs, bot tokens, SMTP passwords, or authorization headers in screenshots, issue trackers, or chat.
- Use provider-scoped credentials where possible, with only the permission needed to send notifications.
- Rotate a credential immediately after suspected exposure and update the notification record.
Keep integrations maintainable
- Include the environment or team in the friendly name, especially when one Uptime Kuma instance monitors multiple sites.
- Document who owns each external webhook, bot, mailbox, or endpoint outside the notification message itself.
- Re-run a test after changing credentials, mail-server policy, firewall rules, proxy settings, or the receiving endpoint.
- Review channels after an Uptime Kuma upgrade. Provider availability and field labels are release-sensitive, and an Apprise-backed service may expose different options than before.
Troubleshoot a failed test
The form rejects a value immediately
Read the field label and validation message carefully. Check that you selected the intended provider, pasted the complete URL or token, removed surrounding whitespace, and supplied every required field. Do not substitute a display name for a credential or use a chat name where a numeric chat ID is required.
The test reports failure or no message arrives
- Recheck the destination value and provider credentials in Uptime Kuma.
- Confirm the external service still accepts the webhook, bot, SMTP account, or endpoint.
- Verify DNS resolution, outbound firewall rules, proxy settings, and TLS or certificate requirements from the Uptime Kuma host.
- Inspect the provider’s own delivery history or server logs where available.
- For SMTP, check spam filtering, relay permissions, sender policy, mailbox quotas, and recipient address spelling.
- For webhooks, compare the configured content type, body, and headers with the endpoint’s documented contract.
The test succeeds but monitor alerts are missing
Open the affected monitor and verify that the saved notification is selected and enabled. Then check whether the monitor actually entered the event state that generates a notification, whether the external provider rate-limited the request, and whether the destination filtered or discarded it. A successful channel test does not automatically subscribe existing monitors.
Only some destinations work
Treat each channel independently. A working Discord or Telegram channel does not prove that SMTP credentials, an HTTP endpoint, or another provider is reachable. Compare the failing provider’s fields, network requirements, and service-side logs rather than changing a channel that already passes its test.
How provider availability changes over time
Uptime Kuma’s official documentation and README describe broad notification coverage, including native services and more than 90 notification services in the project README. That figure is a project-scope statement accessed in 2026, not a promise that every release exposes the same providers or fields. Before documenting a deployment or copying instructions between servers, open the notification type selector in the installed release and verify the current form.
Free tools Windows power users keep installed
One-click scans. No signup required.
If the provider you need is absent, check whether an Apprise-backed option in that release supports it, or use the generic webhook when the service offers a compatible HTTP interface. Do not force credentials for one provider into another provider’s form; the field names and payloads are not interchangeable.
Quick Recap
Practical setup checklist
- Destination chosen for the urgency and audience of the monitor.
- Webhook URL, bot token and chat ID, SMTP details, or endpoint authentication prepared.
- Notification created through account menu → Settings → Notifications.
- Friendly name added.
- Provider fields entered in the form supplied by the installed release.
- Built-in Test completed and the destination checked.
- Channel saved.
- Channel enabled on every intended monitor.
- Secrets protected and ownership documented.
- A re-test scheduled after upgrades or external provider changes.
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.
