Discord and Telegram channel guide

Connect community destinations, publish bot messages safely, and use Discord Inbox where available.

Discord and Telegram publish through bots. The bot's membership and destination permissions matter as much as the BlendDuck connection, so test in a low-risk channel before using a customer-facing community.

Before you start

For Discord, choose the server and text, announcement, thread, forum, or media channel.
For Telegram, create a bot with BotFather, add it to the destination, and copy the numeric chat ID or public @channel name.
Give the bot only the permissions it needs to post and attach files.
Never paste a bot token into a post, comment, ticket, or public URL.

Connect Discord

Open Dashboard → Channels and choose Discord → Connect.
Select the intended server and channel during authorization.
Confirm the bot can view the channel, read history, and send messages.
Grant Attach Files only when posts need attachments.
Send a low-risk message and confirm it appears in the intended channel.

Discord messages can contain up to 2,000 characters and 10 attachments, with a 24 MiB total safety limit in BlendDuck. A forum or media channel also requires a thread name of up to 100 characters; up to five numeric forum tag IDs can be selected. Use mention mode deliberately, because user mentions can notify people.

Connect Telegram

Add the bot to the destination group or channel before connecting it.
In Channels, choose Telegram → Connect.
Enter the bot token and the numeric chat ID or public @channel name.
For a channel, confirm the bot can publish messages.
Send a low-risk test and then store or rotate the token through BotFather as needed.

Telegram supports text up to 4,096 characters, or 1–10 public HTTPS images or videos. A media caption is limited to 1,024 characters; in a media group it is attached to the first item. Optional settings include silent delivery, content protection, link-preview suppression, and a numeric topic/thread ID.

Discord Inbox

Discord Inbox can review messages and supports replies, new messages, reactions, deletion, and attachments when permissions allow. Reading message bodies requires Discord's Message Content privileged intent. Deleting another member's message requires Manage Messages. Telegram Inbox and Analytics are not available; Discord Analytics is not available.

You are done when

each connection names the exact destination, not only the server or bot;
a test message and attachment arrive with the expected notification behavior; and
Discord Inbox either loads messages or clearly identifies the missing intent or permission.

If something blocks you

Symptom	Next action
Discord channel is not selectable	Use a supported channel type and unlock a locked thread before reconnecting.
Discord attachment fails	Grant Attach Files and stay within 10 files and 24 MiB total.
A forum post is rejected	Add a thread name and any tag the forum requires.
Discord Inbox has no message bodies	Enable the Message Content privileged intent for the bot application.
Telegram cannot connect	Verify the BotFather token, add the bot first, and use an exact chat ID or public username.
Telegram channel post is denied	Promote the bot with permission to post in that channel.
A Telegram link is unavailable	Private destinations have no public `t.me` release URL; confirm the message in Telegram.

For team handling rules after a message arrives, see Social Inbox.