Channel setup
Telegram, WhatsApp, Slack and Discord bridges: setup, consent, STOP and the environment variables they need.
How bridges work
Open a conversation, then Participants → Connected channels. Telegram and WhatsApp bring a person who isn't on Muetext into the chat; Slack and Discord mirror the chat to a team channel.
The same rules as the SMS bridge apply: every copy goes through a durable queue (never sent inline), every send decision, STOP and START is written to an append-only consent ledger, and a chat or account is linked only when someone sends a one-time code from it. Only messages written by people reach Telegram and WhatsApp; bot posts stay in the app. Slack and Discord mirrors show everything posted in the conversation.
Not configured = off
Each bridge stays off until its credentials are set on the server. Without them the panel shows "not configured", the webhook answers 503 and nothing is sent. Discord mirrors post to a webhook URL you paste and need no server credentials.
# Telegram TELEGRAM_BOT_TOKEN=123456:ABC… # from @BotFather TELEGRAM_WEBHOOK_SECRET=<random 32+ chars> # WhatsApp Cloud API WHATSAPP_TOKEN=<permanent system-user token> WHATSAPP_PHONE_ID=<phone number id> WHATSAPP_APP_SECRET=<app secret> # signs webhooks (X-Hub-Signature-256) WHATSAPP_VERIFY_TOKEN=<random> # webhook subscription handshake WHATSAPP_TEMPLATE=muetext_new_message # optional, default shown WHATSAPP_TEMPLATE_LANG=en # optional # Slack SLACK_BOT_TOKEN=xoxb-… SLACK_SIGNING_SECRET=<signing secret> # Discord (only for the interactions endpoint) DISCORD_PUBLIC_KEY=<application public key, hex>
Telegram
Create a bot with @BotFather, set the two variables, then point Telegram at Muetext with the same secret. Telegram sends it back in X-Telegram-Bot-Api-Secret-Token on every update; anything without it gets 401.
Invite someone: choose Invite a Telegram chat and send them the link. Tapping Start sends the code and joins their chat to the conversation (that tap is their opt-in). Use the group link to bridge a whole Telegram group.
curl "https://api.telegram.org/bot$TELEGRAM_BOT_TOKEN/setWebhook" \ -d url=https://muetext.com/api/channels/telegram \ -d secret_token=$TELEGRAM_WEBHOOK_SECRET \ -d 'allowed_updates=["message"]'
In Meta's developer console add the WhatsApp product, subscribe the webhook to messages with callback https://muetext.com/api/channels/whatsapp and your WHATSAPP_VERIFY_TOKEN. Every POST is checked against X-Hub-Signature-256.
Invite someone: choose Invite a WhatsApp number and send them the wa.me link. It opens WhatsApp with JOIN and a code; sending it is their opt-in.
WhatsApp only allows free-form messages within 24 hours of the person's last message. Outside that window Muetext sends one approved template naming who wrote (never the text) and holds the messages until they reply. Create a utility template called muetext_new_message with one body variable, for example: "You have a new message from {{1}} on Muetext. Reply here to read it. Reply STOP to opt out."
Slack
Create a Slack app with the bot scopes chat:write, channels:history, groups:history, im:history, channels:read and groups:read. Turn on Event Subscriptions with the request URL https://muetext.com/api/channels/slack and subscribe to message.channels, message.groups and message.im. Turn on Interactivity with the same URL. Install it and set the two variables. Requests are checked with Slack's v0 signature and refused after five minutes.
Mirror a conversation (workspace admins): choose Mirror to a Slack channel, invite the app to the channel and post link CODE there.
Approvals: bot drafts appear as cards with Approve and Reject. A click counts only for a Slack account linked to a Muetext member of that conversation (My linked accounts → Verify, then DM the app verify CODE). The decision runs the same checks as the app and the audit log names that member. Messages from linked members are posted as them; others are ignored.
Discord
Mirror a conversation (workspace admins): in Discord open Server settings → Integrations → Webhooks, create one for the channel, copy its URL and paste it in Connected channels. The mirror is read-only and never pings @everyone or roles. The URL is stored server-side only.
For future buttons, set the application's Interactions Endpoint URL to https://muetext.com/api/channels/discord and DISCORD_PUBLIC_KEY; requests are verified with Ed25519.
STOP and consent
STOP, STOPALL, UNSUBSCRIBE, CANCEL, END, QUIT, PARA, ALTO, BAJA or CANCELAR (also /stop in Telegram) stops everything to that chat from every conversation immediately, with one confirmation. START, UNSTOP or REANUDAR resumes. Blocking the bot or deleting the webhook counts as STOP. Each change posts a system message in the conversation and lands in the consent ledger; members can read the entries for their conversations.