Telegram, Discord and Slack

Besides the social networks, PostBoost publishes to Telegram channels, Discord channels and Slack channels. They connect with a bot token or a webhook URL instead of a login, so there is no app review and no token that expires. Once connected they are ordinary accounts: you schedule to them from the composer, the API (accounts on POST /posts) or MCP, and they go through the same queue, guardrails and webhooks.

Connect a channel

In the dashboard, open /app/{workspace}/connect (workspace admins only). The regular "Add account" dialog does not list these channels yet.

From code, call POST /{workspaceUuid}/accounts/connect/{provider}:

curl -X POST "https://postboost.co/app/api/$WORKSPACE/accounts/connect/telegram" \
  -H "Authorization: Bearer $POSTBOOST_TOKEN" -H "Content-Type: application/json" \
  -d '{"bot_token": "123456789:AA...", "chat": "@yourchannel"}'

PostBoost checks the credentials with the network before saving, stores them encrypted and never returns them. Connecting the same channel again updates it. Every channel counts toward your plan's social account limit.

Telegram

1. Message @BotFather in Telegram, send /newbot and copy the token.
2. Add the bot to your channel as an administrator with permission to post messages.
3. Connect with bot_token and chat: the channel's @username, or its numeric id (starts with -100) for a private channel. Groups work too.

Discord

1. Channel settings → Integrations → Webhooks → New Webhook. Its name and avatar are the author of every post.
2. Copy Webhook URL and connect with webhook_url. Only https://discord.com/api/webhooks/… URLs are accepted.

Slack

1. Create an app at api.slack.com/apps, turn on Incoming Webhooks and add a webhook to the channel.
2. Connect with webhook_url (https://hooks.slack.com/services/…) and a name you will recognise; Slack webhooks do not report the channel name.

What each channel supports

	Telegram	Discord	Slack
Text limit	4,096 characters (1,024 as a media caption; longer text follows the media as its own message)	2,000 characters	3,000 characters
Media per post	Up to 10 photos and videos (album), or one GIF	Up to 10 attachments	Up to 10 images, linked by URL (no video)
How media is sent	Uploaded	Uploaded	Your media library's public URL; it must be reachable from the internet
Delete from PostBoost	Yes, every message of the post	Yes	No (incoming webhooks cannot delete)
Link to the published post	Public channels (t.me/…)	Yes	No
Mentions	Sent as text	Disabled, so a post never pings @everyone	Sent as text
Analytics, comments, inbox	No	No	No

Posts to these channels have no preview in the composer yet; the text you write is what is sent. Daily caps for automated API clients are 50 posts per channel per day (see Agent Guardrails).

When a channel stops working

If the bot is removed from the Telegram channel, its token is revoked, or the Discord/Slack webhook is deleted, the next post fails and the account is marked as needing attention. Connect it again with fresh credentials; the existing account is updated and keeps its posts.

Switching channels off

Each channel can be disabled for a whole installation with POSTBOOST_CHANNEL_TELEGRAM, POSTBOOST_CHANNEL_DISCORD or POSTBOOST_CHANNEL_SLACK set to false. Connected accounts then stop publishing until it is switched back on.