Notifications

What notification bots do

They watch something outside Discord and report when it changes: a stream goes live, a video appears, a post is published, a server goes down. The value is always the same: your members stop checking five places because one place tells them.

The usual sources are Twitch and YouTube, plus RSS, Reddit, Bluesky and GitHub. Game servers add status: whether the Minecraft server is up, how many people are on it, when it restarts.

How to spot a good one

It announces once. The signature failure of this category is the double post: a stream that drops for a moment and returns produces two announcements. A good bot has a cooldown and tells you how long it is.

It lets you write the message. Ping a role or not, with a preview image or without, which channel: those are your calls. Bots with a fixed template eventually ping @everyone because that was the default.

It states its polling interval. For a stream, the gap between "instant" and "every fifteen minutes" is the difference between an announcement and a footnote. A bot that names no number usually has the larger one.

It handles several sources. A server following three streamers needs three configurations, not three copies of the same bot.

Permissions and limits

Not much: Send Messages, Embed Links for previews, Use External Emoji, and, only if it should ping a role, Mention Everyone. That last one is the sensitive part: it also allows @everyone. If you grant it, confine it to the announcement channel through channel permissions.

Administrator is not required. A bot that polls a URL and posts a message does not need to run your server.

One limit nobody mentions: these bots depend on other people's APIs. If Twitch changes its quota or YouTube closes an endpoint, the feature stops without anything being broken. So check whether the developer is reachable; here, maintenance matters more than feature count.

Where people go wrong

The first mistake is pinging everyone. @everyone on every stream is the fastest way to get the channel muted, and then you cannot reach anyone when it actually matters. Use a self-assignable role.

The second is stacking sources in one channel. Streams, videos and an RSS feed side by side means nobody reads any of them.

The third is announcing non-events. A bot that posts "still offline" every day is not a notifier, it is an alarm clock with no reason.