Post to Telegram, Discord and Slack with an API

None of these credentials expire. A Telegram bot token, a Discord webhook and a Slack webhook all keep working until you revoke them: /revoke in @BotFather, delete the webhook in Discord, or deactivate the integration in Slack. That makes them the lowest-maintenance connections, with no reconnect flow to babysit. A webhook is also locked to the channel chosen when it was created, so one webhook means one destination.

Two behaviors are worth knowing because they are silent. Discord content is truncated at 2,000 characters rather than split or rejected, so a long post arrives cut off. Telegram media captions are truncated at 1,024 characters even though text messages allow 4,096. If you send long content to either, shorten it first.

curl -X POST https://api.socifyr.com/api/content/text \
  -H "Authorization: Bearer sk_your_key" \
  -H "X-Workspace-Id: <workspaceId>" \
  -H "Content-Type: application/json" \
  -d '{
    "connections": ["telegram-myaccount", "discord-myaccount", "slack-myaccount"],
    "text": "Release 2.4 is live. Notes: https://example.com/changelog"
  }'

socifyr post "Deploy finished: v2.4 is live" \
  --to telegram-myaccount,discord-myaccount,slack-myaccount --wait

This pattern suits release announcements, incident updates and community posts. An AI agent can do the same through the MCP server with post_text. For anything media-heavy, route Slack out of the connection list: a post with images or video sent to Slack fails with "Slack incoming webhooks cannot upload files — text posts only", while the other channels succeed independently and the post finishes as partial_failure.

• Telegram sends multiple photos as one album (up to 10). Public channels get t.me/<channel>/<id> links and private channels get t.me/c/... links in the result.
• Discord attaches up to 10 files to the message. Files over 8 MB are rejected by Discord's own API, a hard limit. Messages appear under the webhook's name and avatar.
• Slack is text only. File upload needs a full Slack app with the files:write scope, which is not supported yet.

await socifyr.uploads.photos({
  connections: ['telegram-myaccount', 'discord-myaccount'],
  medias: ['https://cdn.example.com/chart.png'],
  text: 'Weekly numbers',
})

Chat channels are where a looping agent does the most visible damage. Put a dailyPostLimit on the API key it uses, or set requireApproval so every post waits for a human. Both are covered in how to give an AI agent safe access to social accounts.

For a public channel use the handle with an at sign, such as @mychannel. For a private channel or a group use the numeric ID, which starts with -100. The bot must be in the chat, and for a channel it must be an administrator with the Post messages right, otherwise posts fail with a permission error. Keep the bot token private: anyone holding it can post as the bot until you revoke it with /revoke in @BotFather.

These channels are lower stakes than a brand account, which makes them a good place to test an automation before pointing it at Instagram or LinkedIn. The same request shape works everywhere, so moving a working flow to a public platform is a matter of adding slugs to connections.