Ready-made scenario · channel mirror
A channel copy that keeps up with the original
You spotted a typo half an hour after publishing and fixed it — in the mirror it gets fixed by itself, no need to go in there by hand. The same goes for deleted posts, changing the pinned post and the channel's replies to its own earlier posts (and a reply in the mirror points to the mirror's own post, not the original's).
- The edit reaches the copy
- The pin moves over too
- The deleted post disappears
- The reply points to the mirror's post
What gets repeated in the mirror
CopyPost remembers which copy was made from which post of the original, and keeps an eye on the original from then on — here's what comes of it.
Sometimes an ad gets added to a post after the fact — if after such an edit the post no longer passes your filters, the copy is deleted (except for an album: it's published as one post, and an edit to one of its parts doesn't delete the copy). And the link between a post and its copy is kept for 30 days, so edits, deletions and pins of older posts no longer reach the mirror.
A backup channel that keeps up
A spare channel is set up in case the main one gets blocked or you lose access to it. The mirror holds the same posts — with the fixes, without what was deleted and with the same pinned post — so on the day the backup channel is needed, you can hand it to your subscribers straight away. As the old joke goes: nothing boosts your confidence in tomorrow quite like a regular backup.
One original can have several mirrors at once — say, a backup, a copy for another city and a feed in a partner's channel, with up to 512 recipients in a single pipeline (that's what CopyPost calls a “from where → to where” link with its settings). Your own links and sign-offs are put in by text replacements, and the formatting stays intact (replacements are shared by the whole pipeline, so copies that need different links get separate pipelines from the original).
A mirror of a mirror only gets what got into the first mirror without CopyPost (say, was written there by hand): CopyPost's copies don't travel further down the chain. So connect every mirror straight to the original — as recipients of one pipeline or with pipelines of their own — and the panel won't let you link channels in a loop anyway.
Posts straight into a forum topic
The recipient can also be a group with topics. Choose, say, “Announcements” — and the channel's posts will arrive there instead of getting lost in the general chat among the members' messages.
If there are several channels and each needs its own topic, make one pipeline for each “channel → topic” pair — pipelines are free on any plan. More in the article on forwarding to forum topics.
Why Forward mode won't do here
In Forward mode (“Пересылка”) a post arrives in the mirror with the “Forwarded from” label, and in Copy mode (“Копия”) — as the mirror's own post. Telegram doesn't let anyone change a forwarded message — not even whoever forwarded it. That's why a mirror is made in Copy mode: deletions and pins are repeated in both modes, but edits and the swapping of links to the channel's posts only in Copy.
Forward mode
We meet on Satruday at 9:00.
The typo stays: Telegram doesn't allow changing a forwarded message.
Copy mode
We meet on SatrudaySaturday at 9:00.
The edit followed the original — which is what a mirror is, really.
Three steps to a mirror
- Connect accountsOne will read the original, the other will publish to the mirror (you can make do with one); your own account connects by QR code or a code from Telegram, a bot by a token from @BotFather. It's simplest when your own account reads and a bot admin publishes.
- Create a pipelineThe source is the original, the recipients are the mirrors. There, too, add filters, link replacements and your own watermark if you need them.
- Choose CopyThis step is easy to skip, and you shouldn't: only in this mode do edits reach the mirror and links to the channel's posts lead to the copies in the mirror.
If the original is read by an ordinary account, Telegram tells it about edits and deletions, usually right away. With a reading bot it's harder: Telegram doesn't always tell it about a new pin in time (and sometimes not at all), and about deletions and unpins it doesn't tell it at all, so the bot re-checks the original itself — and all of this does reach the mirror, but not instantly (and the bot will no longer notice the deletion of a post older than two days). If accuracy matters, read the original with an ordinary account; how the two differ is covered in the article “Userbot or bot”.
Try it on your own channel
Three accounts free, as many pipelines as you like, and all of them free. Connect a channel, publish a post in it, and once the copy shows up in the mirror, edit the original — and watch the edit reach the copy by itself.