Forward messages from a private channel
Forward posts from a private Telegram channel or group you belong to: connect your account, pick the chat, handle channels that forbid forwarding.
A bot cannot be added to a private channel or to someone else's group, so it cannot read them. Routify reads such chats through your own Telegram account: if the account is a member of the channel, the channel can be a source. You do not need to be an administrator of it, and nothing is added to it. Posts then go to your channel, group or private chat like any other forward.
Step 1. Connect your account
In the mini app press Connect account and sign in with a QR code (the recommended way: scan it in Telegram on another device, Settings → Devices → Link Desktop Device) or with a phone number and the code Telegram sends. If the account has a cloud password, the app asks for it. Details and error messages are in Connecting an account.
Use a spare account if you can. Reading many chats automatically is something Telegram may restrict, and the restriction lands on the account, not on Routify. See Security.
The account has to be in the channel before it is added: join or subscribe to the channel under that account first.
Step 2. Add the private channel as a source
- Add forward on the home screen.
- In the Source block switch to Your account. With several accounts pick the one that is in the channel under Connected account.
- The list shows the chats of that account the way you see them in Telegram; Channel is selected from the start. Type the name into the search field and tap the channel.
- In Destination pick where the posts go and press Next. On the second screen check Delivery mode (below) and press New forward.
Groups, chats with people and bots are chosen the same way, with the Group, User and Bot chips. A channel you cannot see in Telegram under that account is not in the list either.
Only an invite link
Send the link t.me/+… to @RoutifyBot in a private chat. The bot asks where to put the posts, then How should this source be read? — a private chat is read only through an account. Your account joins the channel by itself. If the channel accepts members by request, the account sends a request, and the link has to be sent once more after it is approved. The mini app itself does not take t.me/+… links: join the channel under the account first, and it appears in the list.
Channels that forbid forwarding
The admin of a channel can ban forwarding and saving of its content (Telegram's protected content). Telegram then refuses the native forward. Routify handles this in two ways:
- Copy (the default delivery mode) does not forward at all. The account reads the post, and the destination gets a new message with the media uploaded again. The ban does not get in the way.
- Forward with the Copy when forwarding is banned switch on: a post that Telegram refuses to forward is delivered as a copy instead of being lost.
Copy only what you are allowed to republish: the ban is the author's decision, and the source name and a link to the original are kept in the signature by default (see Message template).
What the account does
- It reads the chats you added as sources, and lists its chats so you can pick one.
- It sends nothing unless you chose delivery from the account. By default the bot publishes and the account only reads.
- It never changes account settings, never leaves chats and never reads chats you did not add. The full list is in Security.
The login code and the cloud password are not stored, the phone number is stored masked. You end the session in the mini app (bin icon next to the account) or in Telegram under Settings → Devices.
Limits
- Accounts. Pro — 1, Expert — 3, Ultra and the trial — 5, Business — no limit. At the limit the connect button is replaced by Your plan's connected-account limit is reached.
- Sources. Pro — up to 50, Expert and above — no limit; the limit counts enabled “source → destination” pairs. See Plans and the pricing page.
- The account has to stay in the channel. If it leaves or is removed, reading stops: a private channel cannot be read any other way. The bot sends Source unavailable with the number of the rule — subscribe the account again or replace the source. Only a public channel is taken over by Routify's own service session.
- If the session ends — you closed it in Devices or changed the password — the bot sends Account disconnected, and everything read through the account pauses until you connect it again.
- Past posts of a private channel are copied separately, with the same account: Copy a channel's history.
Questions
Do I have to be an administrator of the private channel?
No. The account only has to be a member of it. Admin rights are needed in the destination if the bot publishes there.
Is it safe to give Routify access to my Telegram account?
Routify signs in as a second device. Of the sign-in data it keeps only the session and a masked phone number; the code and the cloud password are never stored, and the session is shown nowhere. You can end it at any time. The risk that remains is Telegram's own: it may limit an account that reads a lot automatically, which is why a spare account is the safer choice.
Can I forward from a channel where saving is restricted?
Yes, in the Copy mode, or in Forward with Copy when forwarding is banned on: the post arrives as a copy, the media is uploaded again.
The channel is not in the list of my account's chats. What now?
Join it under that account first. The list holds only what the account has a dialog with: channels it is subscribed to, groups it is a member of, people and bots. Or send the invite link to the bot.
Will the channel owner see that I forward their posts?
Nothing is written in the channel: the account is a member already and reads it the way your Telegram client does. The one visible step is joining by an invite link, which is an ordinary join.