Muxlyve sends an automatic message when you go live AND when you finish streaming, to up to 3 Discord webhooks and 3 Telegram bots at once — your community finds out about the start and the end, without you having to write it yourself every time.

0

Discord

In Discord: Channel Settings → Integrations → Webhooks.
Copy the webhook URL.
Paste it into Muxlyve, in Preferences → Webhooks.
Tap "Test" to confirm it works before going live.

Create the bot with BotFather

Look up @BotFather on Telegram (the official bot for creating bots) and open a chat with it.
Type /newbot.
Choose a display name, then a username ending in "bot" (e.g. my_channel_alerts_bot) — BotFather warns if it's already taken.
BotFather replies with the token — a long line like 123456789:AAHqhK9DsSNGCQnQanCwHzXTVo1TVe0MYCA. That's the one that goes in Muxlyve. If you lose it: in BotFather, /mybots → pick the bot → "API Token" → "Revoke current token" generates a new one.

1

Getting the chat ID — the method depends on group vs. channel

If it's a group (or supergroup):

Add @RawDataBot (or @getidsbot) to the group like any other member.
As soon as it joins, it drops a message with all the chat data — look for "id" there (it starts with a minus sign, e.g. -1001234567890).
Copy that number, remove the bot from the group if you won't use it there anymore.

2

If it's a channel: channels work differently — a bot added as a plain member can't see or post anything there, so the group method doesn't work on a channel. Two ways to get the ID anyway:

Forward a message (the simplest, no need to add any bot to the channel): forward any message FROM the channel, privately, to @JsonDumpBot or @RawDataBot. It replies with the full JSON — look for forward_from_chat → id: -100.... That's the ID.

3

With the bot itself: in the channel → Administrators → add the bot as an administrator (not as a member — as a member it's not enough). Post something, then open https://api.telegram.org/botTOKEN/getUpdates (replacing TOKEN with the real token) and look for channel_post → chat → id: -100....

The invite link (t.me/+AbCdEfGh...) does NOT work as a chat ID — it's just a link to join, it doesn't identify the channel to the API.

Shortcut if the group/channel is public (has an @username): use @channel_username directly in Muxlyve's Chat ID field, no need to look up any number.

Group, supergroup and channel IDs always start with -100 when numeric — if the number doesn't start that way, it's probably a person's ID, not a group's or channel's.

Saving it in Muxlyve

Paste the token and the chat ID into Muxlyve.
Tap "Save" — unlike Discord, Telegram requires an explicit save because the bot needs the token and the chat ID together.

Editing the message

There's a dedicated button on the main screen (icon next to "Schedule start") to edit the alert message. It's the same text for both platforms: Discord understands bold, italics and links; Telegram shows it as plain text.

From that same modal, "Test" sends the saved message to every configured channel at once.

45

On start and on finish

The "Alert message" modal has separate tabs — On start / On finish — each with its own text and its own cooldown. The closing alert only gets sent if a stream actually happened (never a closing alert without an opening one).

6

Installation and first launch