Telegram Integration
Overview
Telegram is the main transport layer in Signailist. It is used for:
- News collection from channels and chats.
- Signal delivery when a hot event is detected.
- Autopublish moderation through approval or rejection cards.
- Publishing approved content to target channels.
Connect an account
To work with Telegram, a workspace connects an account through MTProto authorization. The same Telegram account can be attached to multiple workspaces, and the sessions do not conflict.
Collection and publishing roles
A Telegram account can be used in two roles:
- Collection: reads messages from configured sources.
- Publishing: posts approved content to target channels.
The roles can be enabled independently or combined for the same account.
Premium emoji
Telegram custom emoji availability depends on the account that publishes the post. After a publishing account is connected, Signailist can sync the emoji available to that account from the Telegram page.
Once synced, editors can use the emoji button in digest templates, digest review, and autopublish moderation. Standard Unicode emoji are inserted as normal text. Telegram custom emoji are kept with their Telegram document id so they can be published as premium emoji by the selected publishing account.
Synced Telegram emoji are grouped by packs, similar to the Telegram client. Editors can switch between packs in the picker and load more emoji from the selected pack when needed. Workspace admins can also open a pack management dialog on the Telegram page to review synced packs and disable packs that should not appear in the picker for a specific publishing account.
If premium emoji are disabled for a publishing account, or if a custom emoji is no longer available to that account, Signailist publishes the regular fallback emoji instead of failing the post.
Sources
A source is a Telegram channel or chat that Signailist monitors.
- Types: channel or chat.
- Visibility: public by username or private through the connected account dialog list.
- Collection mode: automatic scheduled collection with manual runs available in the UI.
Moderation in autopublish
Autopublish moderation is handled through a Telegram bot connection. When a signal triggers a publication draft, the moderation card is sent to the assigned moderator chat so reviewers can approve or reject the draft without leaving Telegram.
Telegram across the main flows
| Flow | What Telegram does |
|---|---|
| Account connection | Authorizes the workspace session |
| Dialog loading | Lets users browse chats and channels available to the connected account |
| Message collection | Reads message history from the selected sources |
| Signal delivery | Sends alert notifications to Telegram chats |
| Autopublish moderation | Sends moderation cards and captures the moderator action |
| Channel publishing | Delivers approved content to the target channel |
Limitations
- Private channels cannot be joined automatically. The connected account must already have access.
- If Telegram API limits are hit, collection is paused and later resumed automatically.
- Bot-based signal delivery depends on
TELEGRAM_BOT_TOKEN. Without it, bot delivery is not available. - If the session encryption key is rotated, existing Telegram sessions become invalid and must be reconnected.