Копирование постов Telegram-канала

Копирует текст или подпись каждого нового поста Telegram-канала в другой канал без пересылки сообщения.

• Add the bot as an administrator of the source channel so it receives new channel posts.
• Allow the bot to post in the destination channel.
• Confirm the destination channel username or numeric chat id in the destinationChannel variable.
• Publish one test post and verify the copied text or caption before relying on the automation.

• A Telegram channel-scoped MESSAGE trigger receives a new channel post
• The trigger stores user_message_text, which contains the post text or caption
• The Telegram send-message module publishes the stored content to the configured destination channel

Полезно знать

• The bot must be an administrator of the source channel to receive channel_post updates and must be allowed to post in the destination channel.
• Use a MESSAGE trigger with config.source.platform=telegram and config.source.chatTypes=[channel].
• Map trigger output user_message_text into a contact variable, then use that variable as the Telegram send-message text input.
• This recipe handles posts published after the automation is enabled. It does not import existing private-channel history.
• Generic text publishing preserves text or captions, but not every Telegram post type, entity, album, poll, or forwarding attribution.

Частые вопросы

• Should copied posts preserve Telegram forwarding attribution, or should they appear as new destination-channel posts?
• Is copying text and captions sufficient, or must media albums, polls, and formatting also be reproduced?
• Only new posts are handled; existing channel history is not backfilled.

Что важно помнить

• Do not claim this flow imports existing channel history.
• Do not claim byte-for-byte fidelity for media groups, polls, protected content, or message entities.
• Do not use a fixed message body; the destination action must consume the trigger-produced post content.
• Do not replace the Telegram module action with a MESSAGE block, because a MESSAGE block replies in the current chat rather than publishing to the configured destination channel.