In Uptime Kuma, create a notification channel from account menu → Settings → Notifications → Setup Notification (or Add New Notification in some releases), select a provider, enter its credentials, use Test, save it, and then enable that channel on each monitor that should alert you. The exact provider list and field labels vary by installed release, so use the form shown by your own server.
Antihost offers Linux VPS plans with full root access, unlimited traffic on a 1 Gbps port and a 14-day free trial.
What a custom notification does
A custom notification is a saved integration between Uptime Kuma and an external destination. It tells Kuma where to send monitor events such as an outage or recovery. The destination can be a team-chat channel, an email inbox, a mobile messaging bot, or an HTTP endpoint used by an automation system.
As an Amazon Associate I earn from qualifying purchases.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsCreating the channel does not automatically attach it to every monitor. There are two separate operations:
- Notification configuration: the provider, credentials, destination, and message options are stored under Settings.
- Monitor selection: each monitor is configured to use one or more saved notification channels.
A successful test only proves that Kuma could send the configured test payload to the destination. It does not prove that a particular monitor is subscribed to that channel.
#1 Best Overall
- Upgraded Two Zipper Pockets: Forvencer server books feature two secure zipper pockets for better organization of coins, cash, and receipts, ensuring that everything you collect has a safe and secure place
- Smart Storage & Quick Access: Designed with 8 multi-functional compartments, the right side includes a guest receipt pad, while the left has a money pocket, ticket pocket, and credit card slot. Two small clear pockets store bills, receipts, and other visible items. A stitched pen loop ensures you always have your favorite pen ready
- High-quality & Easy to Clean: Crafted from high-quality PU leather with heavy-duty stitching, this server book is built to last. It resists tears, scratches, and its waterproof surface makes cleaning easy with just a damp cloth or a non-chlorine sanitizer
- Perfect Fit for Your Apron: Measuring 5” x 8”, this compact organizer is slightly smaller than other models, making it ideal for bending or sitting while carrying in your server apron. It holds everything a waitress needs—a place for everything
- What's Included: This server organizer comes with multiple open and zippered pockets to store money, receipts, tips, etc. Clear sleeves are perfect for keeping menus or special lists while serving. Available in a variety of colors, allowing you to express yourself even when in uniform
Before you open the notification form
Have the provider information ready
Prepare the value that the selected service requires before starting. Discord uses a webhook URL. Telegram uses a bot token and chat ID. SMTP needs mail-server and account information plus a recipient. A generic webhook needs an endpoint and, when applicable, authentication headers or a request body accepted by your service.
Use an account with permission to change settings
Sign in to the Uptime Kuma web interface with an account that can open Settings and create notification methods. If the Notifications page or save controls are missing, ask an administrator to make the change or verify the role assigned to your account.
Keep secrets out of shared notes
Webhook URLs, bot tokens, SMTP passwords, and access keys grant sending access. Treat them like passwords. Do not paste them into a public issue, screenshot, chat message, or monitor name. If a secret is exposed, revoke or rotate it in the external service and update Kuma immediately.
Expect release-sensitive fields
The project wiki describes support for a wide range of notification services. The official README lists Telegram, Discord, Gotify, Slack, Pushover, Email through SMTP, and more than 90 notification services. That count and the available form fields are release-sensitive; a provider shown in one installation may be absent or labeled differently in another. The installed interface is the authority for the release you are running.
The common setup path
- Sign in. Open the Uptime Kuma web UI and authenticate.
- Open the account menu. Use the menu in the top-right corner.
- Choose Settings. This opens the server-wide configuration area.
- Open Notifications. Existing channels appear here, along with the control for creating another one.
- Start a new channel. Click Setup Notification. Some versions use Add New Notification instead.
- Select a notification type. Choose the provider that matches your destination. The form changes to show that provider’s fields.
- Enter a friendly name. Use a name that identifies both the destination and its purpose, such as
On-call emailorOperations chat. This name is what you will later select on monitors. - Complete the provider fields. Supply only the values required by the selected service, and keep credentials private.
- Run the built-in test. Click Test and check the destination itself for the test message. A browser confirmation alone is not enough; verify the inbox, chat, bot conversation, or receiving endpoint.
- Save the channel. Click Save after the test succeeds.
- Attach it to monitors. Open each relevant monitor, enable or select the newly saved notification, and save the monitor. Repeat for every monitor that should use the channel.
If a provider’s form includes optional message controls, leave them at their defaults until basic delivery works. Add customization one change at a time so a failed test has a small number of possible causes.
Discord notifications
What you need
Create and copy a Discord webhook for the server and channel that should receive Uptime Kuma messages. The webhook URL is the essential credential; anyone who possesses it may be able to post to that channel.
Rank #2
- 5 Pockets & 1 Pen Hook: Keep essentials neatly organized with 5 pockets for cash, cards, receipts, and guest checks, plus a pen holder for easy access.
- Perfect Size for Aprons: Compact 5”x7” size fits comfortably in aprons without poking or bulging. Expandable design ensures easy handling, helping you stay professional and efficient.
- Durable & Easy to Clean: Made from premium, cruelty-free PU leather that’s water-resistant and scratch-proof. Easy to clean, ensuring it stays looking great through busy shifts.
- Stay Organized on the Go: Designed to keep everything securely in place, this server book helps you stay organized even during the busiest shifts, so you can focus on providing great service.
- High Quality at an Affordable Price: A well-crafted server organizer that offers premium quality at a reasonable price, trusted by waitstaff for everyday use.
How to configure it
- Follow the common path to Settings → Notifications → Setup Notification.
- Select Discord as the notification type.
- Enter a friendly name, such as
Discord - production alerts. - Paste the prepared Discord webhook URL into the webhook field.
- If the form offers them, set the bot display name and an optional prefix custom message. A prefix can identify the monitored environment or team without changing the provider credentials.
- Click Test and confirm that the message appears in the intended Discord channel.
- Click Save, then attach this saved channel to the monitors that should post there.
If the test reaches a different channel than expected, the webhook itself points to that channel; change or recreate the webhook in Discord rather than trying to compensate with a Kuma message field.
Telegram notifications
Required values
The Telegram form uses a bot token and chat ID. The bot token identifies the bot, while the chat ID identifies the conversation, group, or channel receiving messages. Keep both values confidential.
Optional delivery controls
Depending on the installed release, Telegram may also expose a message-thread ID, silent sending, and content-protection options. A thread ID targets a particular topic in a group that supports topics. Silent sending suppresses a notification sound where Telegram supports that behavior. Content protection affects forwarding or saving behavior in the destination chat. These controls are optional; they do not replace the token or chat ID.
Configuration steps
- Open Settings → Notifications → Setup Notification and select Telegram.
- Give the channel a recognizable name, for example
Telegram - mobile on call. - Enter the bot token and chat ID shown by the form.
- Set a message-thread ID, silent mode, or content protection only if your Telegram destination requires it.
- Click Test and verify the message in the exact chat or thread.
- Save the channel and select it on the monitors that need mobile-oriented alerts.
A test sent to the wrong conversation usually indicates a wrong chat ID or thread ID, not a monitor problem. Check the destination identifiers before changing other settings.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
SMTP email notifications
Fields the form can use
The SMTP integration can expose fields for SMTP username, SMTP password, sender, recipient, CC, BCC, and a custom subject. The mail server’s hostname, TLS mode, and port requirements are determined by that mail provider and are external to Uptime Kuma. Use the values required by your mail server rather than assuming a universal port or encryption setting.
Configuration steps
- Open the notification setup form and choose Email (SMTP) or the equivalent SMTP label in your release.
- Enter a friendly name, such as
Email - infrastructure team. - Fill in the SMTP account fields, sender, and primary recipient. Add CC or BCC recipients only when they are genuinely needed.
- Set a custom subject if your mail rules or inbox filters depend on one.
- Verify that the account is permitted to send from the chosen sender address. Many mail systems reject a sender that does not match the authenticated account or an approved alias.
- Click Test and confirm receipt in the target inbox, including its spam or quarantine folders.
- Save the notification and attach it to the intended monitors.
Kuma’s test cannot repair a mail server policy. If the form accepts the values but no message arrives, check the provider’s TLS, port, sender authorization, relay policy, and account security logs.
Rank #3
- Built for Heavy-Duty Shifts — Unlike Vinyl, PU Leather Won't Crack: This server books for waitress for Reinforced odorless PU leather with double-stitched seams resists tears and scratches far better than vinyl, which cracks and peels over time. The textured surface adds grip and an anti-slip effect on counters and tabletops for steadier writing. The thickened rigid writing surface stays perfectly flat for comfortable order-taking in high-traffic dining rooms and busy bars. This waitress book design works for both left- and right-handed users — built to withstand fast-paced service without warping.
- Wipes Clean in Seconds — Water-Resistant Surface, Hand Wipe Only: This black server book spill-resistant surface wipes clean with a damp cloth between tables — coffee spills and food grease come right off. Avoid alcohol-based sanitizers; for stubborn oil stains, wipe with mild soapy water, let sit 2 minutes, then wipe. This waitress book is not machine washable — hand wipe only to preserve the PU leather finish. Maintains a sharp, professional look shift after shift.
- 7 Compartments Keep Cash, Cards & Tips Organized: This serving book Secure zipper pocket (1,000+ open/close cycles) is designed for coins and small bills (For maximum security, keep coin pocket moderately filled) — use the main compartment for unfolded bills up to 6.75 inches. Clear receipt windows are made from thickened, scratch-resistant PVC for lasting clarity and durability. The waitress books for servers Clear card slots that hold multiple cards and an elastic pen loop keep everything visible and accessible. Fits standard 3.5" x 6.75" guest checks without folding, so cash, cards, and order slips stay organized during rush hours.
- Slim Apron Fit — Elastic Pen Loop Fits Standard & Jumbo Pens: This server book Compact 5" x 8" slim profile slips into any apron pocket and sits flush against your waist for unrestricted movement — whether bending, sitting, or rushing through a busy dining room. The elastic pen loop stretches to fit both standard pens and jumbo markers, so you always have your preferred writing tool ready. The waitress book Holds all shift essentials without adding weight or bulk.（Pen is not included and must be purchased separately）
- Professional Server Gear for Waitstaff, Bartenders & Cashiers: Streamline orders, tips, and payments with a server book built for waitstaff, bartenders, cashiers, and fast-food crews — not just waitresses. This server books for waitress is Ideal for fine dining, busy cafes, high-volume bars, and fast-food counters. A practical gift for new staff or a reliable upgrade for seasoned teams who demand professional appearance and secure cash handling. This waitress book built for daily professional use with durable construction that holds up shift after shift.
Generic webhook notifications
When to use one
Choose a generic webhook when your destination is an internal HTTP service, an automation pipeline, or an application that does not have a dedicated native provider entry. The receiving endpoint must understand the request that Kuma sends and any authentication you configure.
Available request controls
The API reference exposes a webhook URL, custom body, content type, and additional headers. These controls let you adapt the request to an internal API, but they also make it possible to send a payload the receiver cannot parse.
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 →- Webhook URL: the HTTPS or HTTP endpoint that accepts the request.
- Custom body: the payload format expected by the receiver, such as JSON or form data, when supported by the form.
- Content type: the media type that tells the endpoint how to interpret the body.
- Additional headers: authentication or routing headers required by the endpoint. Store tokens here only when the endpoint and Kuma’s configuration support that arrangement.
Configuration steps
- Select the generic webhook notification type and enter a friendly name.
- Paste the endpoint URL exactly, including the path required by the receiving service.
- Set the content type and body to match the endpoint’s contract.
- Add only the headers required for authentication or request routing.
- Use Test, then inspect the receiving service’s request log as well as its user-facing result.
- Save the channel and attach it to each monitor that should trigger the automation.
An HTTP success response only means the endpoint accepted the request at the transport level. Your automation may still reject a malformed body, missing field, expired token, or unsupported content type. Check application logs when the test reaches the endpoint but produces no downstream action.
Choosing a channel for the job
| Channel | Delivery destination | Setup dependency | Customization identified in the form | Best operational fit |
|---|---|---|---|---|
| Discord | Team-chat channel | Pre-configured webhook URL | Friendly name, optional bot display name, optional prefix message | Shared incident history in a team conversation |
| Telegram | Bot conversation, group, channel, or thread | Bot token and chat ID | Optional message-thread ID, silent sending, content protection | Mobile-first delivery and targeted chat notifications |
| SMTP | Email inbox | Mail-server and account settings | Sender, recipient, CC, BCC, custom subject | Universal mailbox reach, escalation lists, and archival mail flow |
| Generic webhook | HTTP endpoint | Endpoint URL and any required authentication | Custom body, content type, additional headers | Automation pipelines and internal services |
This table describes the fields documented for these integrations; other native or Apprise-backed providers can expose different fields in your release. Select based on where an operator will actually see and act on the alert, not only on the shortest setup.
Attach a notification to a monitor
After saving a notification, return to the monitor list and open the monitor that should use it. In the monitor’s notification area, enable or select the saved channel, then save the monitor. Repeat this for every monitor or group of monitors that needs the same destination.
Use distinct friendly names when several channels have similar destinations. For example, separate a production chat from a test chat rather than relying on an ambiguous name. This reduces the chance of attaching a test endpoint to a production monitor.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →If a monitor supports several notification channels, select the combination that matches your escalation plan. A team chat can provide shared visibility while SMTP reaches people who are not watching the chat. A generic webhook can trigger automation without replacing the human-facing channel.
Testing correctly
What the Test control proves
The built-in test checks whether Uptime Kuma can reach the configured destination with the supplied fields. It is a connectivity and configuration check for that channel, not a simulation of every monitor event.
What it does not prove
- The channel is selected on a particular monitor.
- The external service will accept every future alert, especially after a token expires or a rate limit is reached.
- Your mail inbox, chat client, or automation will display the message exactly as expected for a real outage.
- Network access will remain available after a firewall, proxy, DNS, or routing change.
A practical verification sequence
- Run Test from the notification form.
- Confirm the message at the final destination, not just in the browser.
- Save the channel.
- Verify that the channel is enabled in the monitor’s notification settings.
- For a non-production monitor, observe whether a real state transition produces the expected alert and recovery message.
Troubleshooting by symptom
The notification test fails immediately
Recheck the provider type and every required field. A Discord URL must be the webhook URL, not the server’s ordinary invite URL. Telegram requires both a bot token and chat ID. SMTP requires valid account details and a sender permitted by the mail service. A generic webhook must point to the endpoint path that accepts the request.
Also check whether the Kuma host can make outbound connections. DNS failure, a firewall rule, a proxy requirement, or blocked egress can prevent delivery even when the credentials are correct.
The test reports success, but no message is visible
Look at the destination’s spam, quarantine, muted, archived, or filtered areas. For chat services, confirm that you are viewing the channel or thread addressed by the webhook, chat ID, or thread ID. For webhooks, inspect the endpoint’s access and application logs.
The test works, but a monitor never alerts
Open that monitor and verify that the saved notification is selected. A channel created under Settings is not automatically enabled for monitors. Check the monitor’s event and notification options, then save the monitor again.
Best Value
- Compact Size: Measuring 4.7 x 7.6 inches, this server book is slim, lightweight, and fits effortlessly into your apron pocket. It's designed to hold a standard guest check book (not included), making it an ideal tool for busy waitstaff.
- Ample Storage and Functionality: Featuring 7 pockets and compartments, this server book provides plenty of space to keep all your essentials organized. The tiny front pocket is perfect for holding guest credit cards, while see-through pockets on both sides offer quick access to reference lists. Plus, it even holds a pen when closed without adding bulk.
- Premium Material with a Stylish Touch: Crafted from high-quality PU faux leather with classic solid black, this server book feels luxurious in your hand. It’s waterproof exterior and interior are resistant to water, scratches, punctures, and heat, ensuring durability and easy cleaning.
- Professional Appearance: The smooth, rich black finish and meticulously crafted seams and stitching give this server book a polished, professional look, making it a reliable companion for any server.
- Durable and Easy to Clean: Designed to withstand the demands of the job, this server book is built to last. The waterproof material not only protects against spills and stains but also wipes clean easily, maintaining its pristine appearance even with regular use.
Only some alerts arrive
Check the external provider’s rate limits, token validity, endpoint responses, and network logs. Email providers may defer or reject messages; chat services may throttle requests; automation endpoints may return an accepted response while discarding an invalid payload. Compare a missing event’s timestamp with the provider log before changing the Kuma configuration.
A provider or field is missing
Provider availability changes between releases. Kuma supports native notification methods and Apprise-backed integrations, but the exact list and labels depend on the installed version. Update only through your normal maintenance process, review that release’s notification form, and avoid copying field names from a different version without checking them locally.
Security and maintenance practices
- Limit webhook exposure. Treat a webhook URL as a write credential and rotate it if it appears in logs or screenshots.
- Use least-privilege accounts. An SMTP account should be allowed to send the required messages without granting unrelated mailbox administration.
- Document ownership. Record which team owns each destination and what monitors use it, without recording the secret itself.
- Review after upgrades. Confirm that saved channels still appear, their fields retain the intended values, and a test reaches the destination after an Uptime Kuma or provider update.
- Separate test and production destinations. Name them clearly and attach the test channel only to non-production monitors.
- Plan for provider failure. A second channel can provide an independent route when the primary chat service, mail relay, or automation endpoint is unavailable.
How native providers and Apprise affect your choices
Uptime Kuma combines native notification providers with additional services available through Apprise. Native entries generally expose fields tailored to that service. Apprise-backed entries can broaden the destinations available from one interface, but their field names, capabilities, and availability remain tied to the installed release and the integration’s implementation.
Do not treat the README’s “90+ notification services” wording as a permanent, version-independent catalog. Use the provider selector in your own Uptime Kuma installation, read the fields displayed there, and test the exact destination before attaching it to important monitors.
A reliable rollout pattern
Start with one low-risk monitor
Create the channel, test it, and attach it to a non-critical monitor first. This validates credentials, routing, message formatting, and monitor selection without creating a broad alert storm.
Expand deliberately
Once the first monitor behaves correctly, attach the channel to the remaining monitors in a controlled batch. Keep friendly names and monitor labels consistent so an operator can identify the source immediately.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallOutdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchRe-test after meaningful changes
Run the built-in test after rotating a token, changing a webhook, updating SMTP credentials, modifying a webhook body, or changing the receiving service. Then verify monitor selection if the notification was replaced rather than edited.
Quick Recap
Key takeaways
- Use account menu → Settings → Notifications → Setup Notification or the version-specific Add New Notification label.
- Choose the provider and supply its required destination data: webhook URL, bot token and chat ID, SMTP details, or an HTTP endpoint configuration.
- Test the destination before saving, then explicitly select the saved channel on every monitor that needs it.
- Expect provider lists and field names to change with Uptime Kuma releases and Apprise integrations.
- Protect notification secrets and verify delivery again after credential, network, or software 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.
