Forwarding messages

Using Junction Bot you can copy new coming messages from different sources to your channel or group. We call it forwarding.

Possible sources of messages:

  • public and private channels and groups
  • closed private channels and groups (without an invitation link)
  • other bots
  • private chats with other users

Some of these sources are available only with Direct Connection. Please check here to see which type of account you need. Views of a forwarded message are counted separately and do not change the views count of the original message.

Creating a new forward

To create a forwarding rule use the command /new. It will guide through the setup process.

After the setup is complete you can see your new list of rules with the command /forwards (former /list). Also, this command will show you buttons to control your forwarding rules (disable, delete, etc).

You can adjust different settings of all your rules or of every particular rule. Please see here for more details.

Invitation link

The bot can forward messages from private channels and groups if they have an invitation link and also if they don’t have it.

If you are using the Standard account, please remember that private telegram channels are guaranteed to work only until the invitation link is active.

If you need to work with private channels without an invitation link or you want to get messages from other bots, you need to use the direct connection.

Forwarding from one source to several destinations

Usually, when you adjust settings of your forwarding rules you use a link to a source channel. But how to identify exact rule if you have several forwarding rules to different channels from one source. How to set up different settings/filters/replacements for different destination channels?

Add the following construction to the source name: ->-1001251642436
Where -1001251642436 is the identifier of the destination channel in the Telegram system plus prefix “-100” (it’s the way how Telegram distinguishes numbers of channels from numbers of other objects). To find this number is very simple, search the Internet for instructions. For example, forward a message from the channel to the bot @junction_helper0_bot. There you will see the channel number in or

For example, the configuration command might look like this:
/settingchannel @source_channel->-1001251642436 header none

Status “Pending”

If your source channel is completely new to the system and we have a high load it can take a while for the bot to start receiving messages from it.

If using the command /forwards (or former /list) you see channels marked by PENDING, it means these channels are waiting for being connected to the bot. Please wait for 10-30 minutes’ time and messages will start coming.

Please let us know if it takes more than one day.

Reducing delays

For public channels on a Free and a Standard accounts, message delivery can take up to 1 hour. Delivery from private channels usually happens instantly, but rarely, once in a while, it can jump up to 10-20 minutes.

If your source channel is completely new to the system and we have a high load it can take a while for the bot to start receiving messages from it. Please let us know if it takes more than one day.

We are providing a service for speeding up delivery from a public channel so it will take several seconds. This service costs 100 RUB (~1.4 USD) per channel per month. You can enable/disable speeding up whenever you want with command /express.
For example, to speed up @slow-channel use /express @slow-channel
To change the channel being speed up, first, disable the express for the previous channel with the same command and then enable it for a new one. You can see the list of your express channels by the command /express without arguments.

Another way to make the delivery instant is to use the Direct Connection. All messages from direct connection come instantly.

If you are interested in one of these services please see here more about how to buy them.


Junction Bot should be an admin in the destination channel only (it can be a public or a private channel) and you need a Standard account. If your source is a private channel, you only need an active working invitation link. Junction Bot does NOT have to be an admin of this channel. The Bot will join the source channel as a common user. Administration of the source channel can’t find out that it’s a bot. If you need more control over this consider the Direct connection. It allows you to forward messages from the source channel without being noticed at all.
Please note that if you are in our support group, an admin of the source channel can find this out. So for communication in a support group, we recommend using an account other than that in the source channel.

No, it’s not possible.

Yes. First, enable the authors name display with the
/settingchannel … author …
command, and then configure the filters by the desired names.

Yes. Add the bot to the group and just use it as you do in private chat. Maybe you will need to specify the bot’s name in commands: /join@junction_bot

Yes. Add the bot to the group and use it in the same way as in private chat.

They will start to appear automatically after some time. First of all, a replied message should be in the destination channel already. Also, several replies in the source channel will enable the transferring of replies, so after some time you will start to see replies for the new messages in the destination channel.

Yes, we do not guarantee delivery if messages are published in the source channel more often than once per several seconds.

For channels just added to our system, the start of delivery can take up to one day. This is caused by Telegram’s limitations – we cannot connect to a lot of new channels in a short period of time. But usually, it’s quicker, so just wait for a little.

Messages can come with a delay, usually it will not exceed 30 minutes. Before trying everything else please ensure that the desired channel presents in the list of your subscriptions (use command /list). Also, check that your filters are not filtering all the messages (usual mistake is to add a mustNotHave filter on all links and forget to disable links in the message’s footer).

If messages are still not coming please contact us and provide:
1. a message which you’ve used to create your subscription or forwarding,
2. date-time when you subscribed,
3. the bot’s answer,
4. the bot’s answer to the /list command.

Questions without this information will be redirected back to this FAQ.


All channel to channel forwards are controlled using the /channel command. Use it in the form /channel @destination leave @source.

Once in a while we are updating Junction Bot. Usually, it takes less than a minute.

After an update the bot needs some time to connect to all its channels again. It will be marked with an UPDATING status – just wait for a little bit.

In very rare cases this status can stay for 10-30 minutes, but even in these cases messages will start coming even before status will change back to normal.

The bot will try to join this channel again, but if the admin will persist in banning it, the messages from this channel will stop coming. To work around this you need the Direct Connection. But for a direct connection to work, you will need to be a member of the source channel yourself.

Please check that you are using a Standard account and that the status of your forward is not PENDING. If not, please forward the message with your command and the message with the bot’s response to the admin, and describe your problem.

Then you should use the channel instead of the group. Then all messages will come from the name of the channel.
Also, if you want them to be delivered from your name, you should use a direct connection.

Load More