Forward LogoForwardMsg

Delivery and Permissions

Fix a bot that cannot post, missing attachments, or delayed delivery to Discord and Telegram.

If the source is selected and its Routing destination is saved, check the receiving bot or webhook. One destination can fail while another continues working.

Destination permissions

Discord bot

  • Make sure the bot is in the destination server.
  • In that specific channel, allow View Channel and Send Messages.
  • Allow Attach Files for media and Embed Links for embed cards.
  • Allow Read Message History when replies need an earlier message as context.
  • For threads, allow Send Messages in Threads and access to the thread.
  • For pins/unpins, allow Pin Messages. ForwardMsg's standard bot installation also includes Manage Messages; deleting the bot's own sent messages is different from managing another user's messages.
  • If Enable webhooks is on, give the bot Manage Webhooks. Delivery then has webhook limitations.

Channel overrides can deny permission even when the server role allows it. See Forward to Discord.

A verification bot hides the receiving channel

Some servers use a verification or gatekeeper bot that gives new members a role before they can see or post in certain channels. Your newly invited Discord bot may not receive that role automatically.

For example, if only members with the Verified role can write in #news, your bot also needs permission to post there. Ask the server administrator to assign the appropriate role to the bot or give it explicit access through Edit Channel β†’ Permissions. Also check any restrictions inherited from the channel's category. You do not need to turn off the server's verification system.

ForwardMsg's automatic bot configuration sets portal defaults; it does not assign server roles or override these channel restrictions. After access is fixed, save the Routing destination and send a new message through the automation. See Create a Discord Bot.

Discord webhook

Open the target channel's Integrations β†’ Webhooks and confirm the webhook still exists. Check that the saved destination points to the intended channel. If it was deleted, create a new one and update Routing.

Native replies and pin/unpin mirroring are not supported by webhooks. Adding bot permissions does not change this; use a Discord bot instead.

Telegram bot

  • Channel: add the bot as an administrator with permission to post.
  • Group: add the bot and allow it to send the selected message types. Grant administrator rights for deleting, pinning, or managing messages.
  • Topic: use the parent group Chat ID and correct Topic ID. Make sure the topic is available for posting.
  • Private chat: open your bot and press Start or send it a message first.

See Forward to Telegram and Telegram topics.

Messages are delayed

For Discord, Telegram, or WhatsApp, click the chat you copy from and open Advanced β†’ Message Delay. Check whether it inherits a delay from Global Settings. Set it to 0 to remove an intentional wait in your test setup.

For Discord or Telegram, Refetch before sending checks the latest version after the wait, before delivery. Uploading a large attachment also takes longer than sending text. Compare its size with the upload limits.

See Delays to choose the waiting time for each chat.

Media is missing

  1. Confirm plain text reaches this same destination.
  2. Open Automation Features below Start and enable Images, Videos, or Files as needed.
  3. Open Filters β†’ Forward Options for the selected original chat and select the type. Audio and Documents are separate switches, both using the Files feature.
  4. Check the destination upload limit. Buying media forwarding does not increase it.
  5. Try a small file of the same type in your private test route.

Telegram photos over 10 MB can arrive as documents instead of photo messages. Some cross-platform content changes appearance rather than preserving the source platform's original style.

Still need help?

Tell support which destination fails, whether text arrives, the file type/size if relevant, and the visible error. Never share the bot token or webhook URL.

Was this page helpful?