Telegram
Connecting a Telegram channel, public or private, by making ChannelForge's bot an administrator — the code that proves the channel is yours, what a post carries, its pace and when it needs you.
ChannelForge posts each episode to your Telegram channel as a video, on the channel's slots — each at a minute of its own a little after the slot, the way a person posts. It posts as ChannelForge's own bot, which you make an administrator of your channel: nothing of your own Telegram account is ever used. Telegram is in every paid plan.
Before you connect#
- A Telegram channel you run — public (it has an @name) or private. Groups are not supported: ChannelForge posts only to channels.
- You need to be able to add administrators to the channel and to edit its description.
- Connecting needs the editor role or above. Disconnecting needs an admin or owner.
Connect#
- Open Settings → Connections and press Connect on the Telegram card.
- Make the bot an administrator. The page's link opens Telegram and asks which channel to add it to, with only the right to post messages. You can also do it in the channel: Administrators → Add Admin → search for the bot's @name.
- Copy the code the page shows — it starts with
forge-— and put it anywhere in the channel's description. It proves you run the channel, because only its administrators can edit the description. The code is yours alone, for this workspace; it changes every day, and yesterday's still works. - Type the channel's @name, or its t.me address. A private channel has no @name: paste a link to one of its posts instead (in Telegram, right-click or long-press a post → Copy Post Link).
- Press Connect. ChannelForge asks Telegram that the channel exists, that it is a channel, that the bot may post there and that your code is in its description. The channel then shows on Connections with its name: link it to a channel under Which account each channel posts as.
- Take the code out of the description again whenever you like: it is only needed to connect.
| The bot may | The bot never |
|---|---|
| Post messages: the episodes' videos and their words | Reads your channel's messages, members or statistics |
| Posts anywhere it was not made an administrator | |
| Uses your own Telegram account |
A Telegram channel is connected to one workspace at a time.
What is posted#
| Part | What Telegram receives |
|---|---|
| Video | The episode's 720p copy, or its video as it is when it fits — a bot may upload 50 MB, so a bigger video goes as a 720p copy made to fit. It is sent with its width, height and length, ready to stream |
| Cover | The episode's thumbnail |
| Words | At most 1,024 characters, in one of a few shapes chosen per episode: the title, a short summary, the channel's call to action and up to three hashtags. A product channel's post carries its shop link, code and disclosure in every shape |
| Never | A label of any kind, an @mention that would tag a stranger |
The shapes vary from episode to episode, so a channel's posts never read as one template; a retry posts the very same words.
When it posts#
On the channel's slots, after the core platforms and Bluesky, before X — but never at the slot's own minute:
- each Telegram post goes at a random minute and second 3 to 45 minutes after the slot;
- never within 6 minutes of the minute that Telegram channel was posted to the day before;
- at least 30 minutes from any other post to the same Telegram channel, whichever channel of yours it is for;
- at most 6 posts a day per Telegram channel (UTC day). Past that, the slot records why and the episode keeps its tries.
Post now on the episode's Post tab sends it 20 seconds to 2 minutes after the click.
Never twice#
Telegram gives a bot no way to look at what a channel already shows. So a post whose answer was lost on the way back is never sent again by itself: the episode's Post tab shows it as may be live. Look at your channel — if the episode is not there, press Confirm it is not live, retry. A post that could not reach Telegram at all is simply sent at the next try.
When the bot loses its rights#
Before every post, ChannelForge asks Telegram whether the bot is still an administrator allowed to post. If it was removed, lost the right to post, or the channel is gone, the connection is marked for reconnecting: nothing is sent, no episode uses a try, and the workspace's owners and admins are told. Add the bot back as an administrator allowed to post messages, put your code in the description again, then press Reconnect on its row.
Good to know#
- Telegram gives bots no view counts for channel posts, so Analytics shows no numbers for Telegram posts. They are counted, never measured — and nothing is read from Telegram's pages to make up for it.
- A channel that chose no platforms under Post to posts to Telegram too, once a Telegram channel is linked to it.
- To stop: disconnect the channel on Connections, and remove the bot from the channel's administrators.
Troubleshooting#
"ChannelForge's bot is not an administrator of that channel yet". Add it under the channel's Administrators, with the right to post messages, then press Connect again.
"The code is not in the channel's description yet". Paste your code anywhere in the description, save it in Telegram, then press Connect again.
"That is an invite link". A bot cannot open invite links. For a private channel, add the bot first, then paste a link to one of the channel's posts.
"That channel is connected to another ChannelForge workspace". Disconnect it there first.
"the account has 6 Telegram posts today (UTC)". The Telegram channel reached its 6 posts for the day; the next goes tomorrow.
Related#
- Schedules and autopilot — human-like timing
- Bluesky
- Privacy at a glance
Something missing or unclear? Tell us and we will improve this page.