Connecting Telegram to AutoPost

Contents

0. Cover & contents

1. At a glance

2. Key terms

3. Step A — Create a bot in @BotFather

4. Step B — Set up the target

   • B1 Public channel

   • B2 Private channel

   • B3 Groups and supergroups

   • B4 Topic groups

   • B5 Private chat with the bot

5. Step C — Find the chat ID

6. Step D — Connect in AutoPost

7. Step E — Send and schedule to Telegram

8. Managing Telegram accounts

9. Troubleshooting

10. Security and privacy

11. Frequently asked questions

12. One-page checklist

13. Help and contact

1. At a glance

What you'll achieve

After following this guide, AutoPost can send text, photos, and videos to Telegram through a bot that you own. The target can be a channel, a group, or a private chat with the bot. You can send right away or schedule posts.

Here's how it works:

1. You create your own bot in Telegram. The bot is free.

2. You add the bot to the target channel or group and give it permission to post.

3. You paste the bot's token and the target address into AutoPost.

4. From then on, every post you choose to send to Telegram is sent by that bot.

You don't pay Telegram anything. AutoPost uses Telegram's official route for bots (the Bot API).

Estimated time

What you need

• An active Telegram account, and the Telegram app on your phone or computer.

• A target channel or group that you own or are allowed to manage. You must be able to add admins there. If you don't have one yet, you can create it first in the Telegram app.

• An AutoPost account that can already sign in at https://app-autopost.solusikecerdasankomputasi.com.

• A safe place to keep the token for a while, for example a password manager.

2. Key terms

These words come up often. Read them once; you can come back here at any time.

3. Step A — Create a bot in @BotFather

Step by step

1. Open the Telegram app. Your phone or computer both work.

2. Search for @BotFather in the search field. Pick the one with the blue check mark. Ignore other accounts with similar names.

3. Press the Start button (or type /start and send it). BotFather replies with a list of available commands.

4. Type /newbot and send it.BotFather asks for your bot's name.

5. Send the bot's name. Example: Kabar Kampung Kita.

   • This is the name other people see, for example at the top of messages.

   • The name can contain spaces and can be changed at any time with /setname.

   BotFather then asks for the bot's username.

6. Send the bot's username. Example: kabar_kampung_bot. The rules:

   • 5 to 32 characters long.

   • Only Latin letters (A–Z, a–z), digits, and underscores _. No spaces, no hyphens.

   • Must end in bot, for example kabar_kampung_bot or KabarKampungBot.

   • Uppercase and lowercase count as the same.

   • Can't be changed after it's created. Choose carefully.

   If someone else already uses the username, BotFather asks again. Try another variation, for example kabar_kampung_kita_bot.

7. BotFather gives you the token. Its reply contains a long line like this:

   123456789:AAHfakeExampleNotARealToken_x9Qz12abc

   (The example above is fake; it only shows the shape.) The token is made of digits, a colon, then about 35 letters, digits, -, or _.

8. Copy the token. In many versions of the app, tapping the token copies it. If not, press and hold, then choose Copy. Copy all of it, from the first digit to the last letter. Don't copy any space or period at the end of the sentence.

Keeping your token safe

The token is the full key to your bot. Anyone who has it can send messages as the bot to every channel and group where the bot is an admin.

• Store it in a password manager or a locked note.

• Don't send it by chat, email, or social media, including to us. You only need to paste the token on the AutoPost Telegram page.

• Don't take a screenshot that shows the token and then share it.

• Don't keep it in shared documents or family/work groups.

• If anyone else has seen the token, change it (see 8.3).

Protecting the bot owner's Telegram account

A bot is tied to the Telegram account that created it. Whoever controls that account can open @BotFather and get the bot's token at any time. So:

• Turn on Two-Step Verification on the Telegram account that created the bot (Settings → Privacy and Security → Two-Step Verification).

• For businesses or organizations: create the bot from a Telegram account owned by the organization, not an employee's personal account. If the employee who created the bot leaves or loses the account, control of the token is lost too.

• One Telegram account can only create a limited number of bots (about 20 bots, according to @BotFather's replies; this number isn't in the official documentation). This matters if you want one bot per target.

Other useful @BotFather commands

The latest command list is always in @BotFather itself (send /help or /start).

Tip: create one bot just for AutoPost. Don't use a bot that another service already uses. That way, changing the token or deleting the bot won't affect other services.

4. Step B — Set up the target

Choose your type of target, then follow only its part.

B1 Public channel

A public channel has an @name address, for example @kabar_kampung_kita.

Adding the bot as an admin

1. Open your channel in Telegram.

2. Tap the channel name or photo at the top to open the channel info.

3. Choose Edit (the pencil icon) or Manage Channel.

4. Choose Administrators.

5. Choose Add Admin.

6. Search for your bot's username, for example kabar_kampung_bot, and select it.

7. In the list of admin rights, make sure Post Messages is on. This right only exists in channels.

8. You can turn the other rights off. AutoPost only sends new messages; it doesn't edit or delete messages.

9. Save (the check mark icon or Save/Done).

Quick way (optional). Telegram has a special link that adds a bot as a channel admin directly. Replace kabar_kampung_bot with your bot's username, then open this link on a device that has Telegram installed:

https://t.me/kabar_kampung_bot?startchannel&admin=post_messages

Telegram asks you to choose a channel, then adds the bot as an admin with the Post Messages right.

If the channel has "Sign Messages" turned on, the bot's name may appear as the author under posts sent by AutoPost. That's normal. Turn that setting off in the channel if you don't want it.

What goes in the AutoPost Target field (choose one)

• @kabar_kampung_kita — the way we recommend, or

• kabar_kampung_kita (without @; AutoPost adds it), or

• the channel link t.me/kabar_kampung_kita, with or without https:// (the telegram.me/… form and the web preview link https://t.me/s/kabar_kampung_kita are accepted too), or

• the link of one message in the channel, for example https://t.me/kabar_kampung_kita/15 (press and hold the message → Copy Link). The message number at the end is ignored.

If the channel address changes. If you change the channel's @name address one day, AutoPost keeps sending to the same channel. AutoPost stores the channel's numeric ID, not its address. Press Retest so the name shown in AutoPost is updated too.

B2 Private channel

A private channel has no @name address. Invite links (https://t.me/+AbCd… or t.me/joinchat/…) can't be used as a target; AutoPost rejects them. Use the link of one message in that channel instead, or its numeric ID starting with -100.

1. Add the bot as an admin exactly as in B1 (steps 1–9), with the Post Messages right on. The quick way with the ?startchannel&admin=post_messages link also works for private channels.

2. In the channel, press and hold one message (on a computer: right-click), then choose Copy Link. If the channel is still empty, send any message first. The link looks like https://t.me/c/1234567890/15 (see Step C, method 1).

3. Paste that link as is into the AutoPost Target field. AutoPost turns it into the channel ID for you (-1001234567890); the message number at the end is ignored.

B3 Groups and supergroups

Must the bot be an admin? Not required, but strongly recommended. A bot can send to a group like a regular member, as long as group members are allowed to send that type of message. But a bot that is only a member is subject to all member restrictions:

• If your group doesn't let members send messages (only admins can), the bot must be made an admin.

• Media permissions for members are set separately for each type: Photos, Videos, and Files. If one of them is off, the bot can't send that type. Note: AutoPost sends photos over 10 MB as files, so large photos need the Files permission, not the Photos permission (see 7.4).

• Slow mode: when it's on, regular members (including bots) must wait a set time between messages.

• Paid messages: a group can require members who aren't admins to pay Telegram Stars for each message. AutoPost doesn't pay for paid messages, so posts from a member bot to such a group may be rejected.

Make the bot an admin so that none of the restrictions above apply. Once the bot is a group admin, it can automatically send messages and media, isn't affected by slow mode, and doesn't need to pay for paid messages. In groups there is no admin switch for "send messages" or "send media"; the Post Messages switch only exists in channels. A bot that is an admin can see all group messages, but AutoPost doesn't read your group messages; AutoPost only sends.

Adding the bot to a group

1. Open the group, then open the group info:

   • Android: tap the group name at the top → the pencil icon at the top right → Administrators.

   • iPhone: tap the group photo at the top right → Edit → Administrators.

   • Computer (Telegram Desktop): click ⋯ at the top right → Manage group → Administrators.

2. Choose Add Admin, search for the bot's username, and select it.

3. Once the bot is an admin, it can automatically send messages and media. Turn off the rights it doesn't need (delete messages, ban users, add admins, and the like). Also make sure Remain Anonymous is off; if it's on, the bot's messages appear under the group's name. Then save.

If you don't want to make the bot an admin, just add the bot as a member with the Add Members menu, then make sure the group's member permissions allow sending messages, Photos, Videos, and Files, and that slow mode and paid messages are off. When connecting, AutoPost checks that the bot is already in the group and allowed to send messages; if Photos/Videos/Files are closed to the bot, AutoPost only shows a warning note (slow mode and paid messages aren't checked).

Quick way (optional): open https://t.me/kabar_kampung_bot?startgroup (replace it with your bot's username), then choose the group.

What to type in the AutoPost Target field

You can paste a group message link directly; the message number at the end is ignored. If you type an ID, any spaces in it are removed automatically.

Important: a group can turn into a supergroup. Telegram can turn a regular group into a supergroup, and when that happens the group ID changes. One trigger for certain: turning on Topics in a regular group always turns it into a supergroup first. So finish the group settings first (turning on Topics, creating a public address, adding admins), then find the ID (Step C). Sends to the old ID fail with this message:

How to fix it is in 8.4.

B4 Topic groups (forums)

A topic group is a supergroup whose messages are grouped by topic. Set up the bot exactly as in B3.

Choosing a topic. AutoPost can send to one specific topic:

1. Open the topic you want (for example "Announcements"). If it's still empty, send any message there.

2. Press and hold one message inside that topic (on a computer: right-click), then choose Copy Link. The link contains two numbers after the group address: the topic number (in the examples below: 7), then the message number.

   • private group: https://t.me/c/1234567890/7/15

   • public group: https://t.me/groupname/7/15

3. Paste that link as is into the Target field, then press Test & connect. The green message names the topic, for example "“Diskusi Warga · topik #7” was connected after testing it with Telegram…", and the account label also ends in · topik #7 (account labels are stored in Indonesian, so they read "topik" even in the English interface).

Without choosing a topic, posts go to the default General topic. This happens if you enter @name, a numeric ID, a message link from the General topic, or just a topic link (with only one number after the group address). The account label then ends in · topik General, and the green message gets the note "This group has topics: posts go to the General topic. …".

What you need to know:

• A group can only be connected once in your AutoPost account, so one group = one topic. To change the topic, Disconnect that account, then connect again with a message link from the new topic.

• If the target topic is closed, sends are rejected with the message "Topic #7 in this group is closed…". For the General topic: hiding the General topic also closes it automatically. Reopen or unhide the topic, then press Resend failed.

• If the target topic is deleted, sends fail with the message "Topic #7 wasn't found or has been deleted…" and the account becomes needs reconnecting. Disconnect the account, then connect again with a message link from a topic that still exists.

• If the bot isn't an admin, AutoPost shows a note when connecting: if the topic is closed, the bot's posts will be rejected. Making the bot a group admin is safer.

B5 Private chat with the bot

You can also have AutoPost send to a private chat with the bot, for example to check a post before publishing it to a channel.

Telegram's rule: a bot can't start a conversation. The person who is the target must first open the bot and press Start.

1. Open https://t.me/kabar_kampung_bot (replace it with your bot's username), or search for the bot's username in Telegram.

2. Press the Start button (or send /start).

3. Find that person's user ID with Step C, method 2. A user ID is a positive number, for example 123456789.

4. Type that number in the AutoPost Target field.

If that person later blocks the bot or deletes their Telegram account, sends will fail. See section 9.

5. Step C — Find the chat ID

Skip this part if your target is a public channel or a public group. Just use @name.

For private channels and private supergroups (including topic groups), you don't need to work out the ID: just copy the link of one of their messages, then paste that link into the Target field (method 1). You only need to find a numeric ID for private regular groups and private chats (method 2).

Method 1: message link (safest)

This method doesn't need the token, so there's no risk of the token leaking.

1. Open your private channel or supergroup. If there are no messages yet, send any message.

2. Press and hold that message (phone) or right-click it (computer).

3. Choose Copy Link (or Copy Post Link — the menu name may differ).

4. Paste the link into a note. It looks like this:

   https://t.me/c/1234567890/15

5. Paste that link as is into the AutoPost Target field. Done: AutoPost turns it into the chat ID -1001234567890 for you and ignores the message number at the end.

If you want to write the ID yourself (for example to keep a record): take the number right after /c/ (in the example above: 1234567890), then put -100 in front of it. The result is -1001234567890, the same as pasting the link.

Notes:

• In a topic group, a message link inside a topic looks like https://t.me/c/1234567890/7/15: the middle number (7) is the topic number. Pasting this link makes AutoPost send to that topic (see B4). If you write the ID yourself, still take the first number after /c/, and posts go to the General topic.

• Regular groups (not supergroups) don't have t.me/c/ links. Use method 2.

• If you write the ID yourself, don't forget the minus sign in front. 1001234567890 (without the minus) will fail.

• Public channel links look like https://t.me/channelname/15, not /c/. You can paste these too, or just use @channelname.

• AutoPost works out the ID from the link with Telegram's official formula, so the result is correct for numbers of any length. Putting -100 in front yourself is only correct for 10-digit numbers after /c/, which is the form used today.

Method 2: getUpdates (for regular groups and private chats)

This method is official from Telegram, but the address contains your token. Follow the safety steps.

Prepare first:

• For a group: add the bot to the group (B3), then send the command /start@kabar_kampung_bot in the group (replace it with your bot's username). A plain message like hello is not received by a bot that isn't an admin (see "If the result is empty").

• For a channel: make sure the bot is already an admin (B1/B2), then post one new message in the channel.

• For a private chat: ask the person to press Start in the bot, then send any message, for example hello.

Steps:

1. Open an incognito/private window (Incognito/InPrivate) in your browser, so the address isn't saved in the history. This window does not protect you from browser extensions allowed to run in incognito mode, or from a work proxy that opens HTTPS traffic. The safest option is a personal device, or still change the token afterward.

2. Type the following address. Replace <TOKEN> with your bot's token (without the < > signs):

   https://api.telegram.org/bot<TOKEN>/getUpdates

   Note the word bot stuck directly in front of the token. This word bot is only for this address. When you paste the token into AutoPost, don't add bot.

3. The browser shows a long text. Look for the part "chat":{"id":…. Example (simplified):

   "chat":{"id":-1001234567890,"title":"Kabar Kampung Kita","type":"supergroup"}

   or, for a private chat:

   "chat":{"id":123456789,"first_name":"Rina","type":"private"}

4. Copy the number after "id": inside the "chat" part, including the minus sign (if there is one). Make sure the "title" or "first_name" matches the target you mean.

5. Close the incognito window.

{"ok":true,"result":[{"update_id":…,
 "message":{"message_id":…,
  "from":{"id":…,"is_bot":false,"first_name":"Rina"},
  "chat":{"id":-1001234567890,"title":"Kabar Kampung Kita","type":"supergroup"},
  "date":…,"text":"/start@kabar_kampung_bot"}}]}

If the result is empty ("result":[]):

• In a group: a bot that isn't an admin doesn't receive plain messages (Telegram's privacy mode is on from the start). Send a command /start@username_bot (not a plain message), or remove the bot from the group and add it back (the bot joining is recorded as a service message), or make the bot an admin. Then reload the page.

• In a channel or private chat: send another message, then reload the page.

• Telegram only keeps recent updates for up to 24 hours. Send a new message, then try again.

• This method doesn't work if the bot is already used by another service that set a "webhook". Create a new bot just for AutoPost.

• This method can also come back empty or show a Conflict error if the bot is being used by another program that also fetches updates (polling). Again: use a bot just for AutoPost.

Token safety (strongly recommended):

• If you're on a shared computer, or forgot to use an incognito window, clear the browser history for that address.

• For maximum safety: after you get the ID, request a new token in @BotFather (see 8.3), then use that new token in Step D. Make sure the token really changed: compare the last 4 characters of the new token with the old one. If they're the same, the token has not changed yet; use /mybots → choose the bot → API Token → Revoke current token (or /revoke). Once it's revoked, the old token that may have been recorded in the browser no longer works.

Method 3: unofficial methods (not recommended)

• The number in the Telegram Web address. Telegram doesn't guarantee the format, and it may change. If you use it anyway, always double-check the result with the Test & connect button.

• "Show Peer IDs in Profile" in Telegram Desktop (Settings → Advanced → Experimental settings). This method needs no token and no third-party bot, but the number shown for channels/supergroups has no -100 (for example it shows 1771275406, while the correct ID is -1001771275406), and in some versions it's copied with thousands separators (1,771,275,406). AutoPost removes commas automatically, but you still have to add -100 in front for channels/supergroups yourself. Easier: use method 1 (paste a message link).

• Third-party bots ("ID" bots, "info" bots, and the like). Telegram itself advises treating every bot as a stranger. Such bots can read group messages if you add them. Don't add third-party bots to channels or groups that contain sensitive content.

6. Step D — Connect in AutoPost

6.1 Opening the Telegram page

1. Sign in to AutoPost at https://app-autopost.solusikecerdasankomputasi.com.

2. Open the Social accounts menu.

3. On the Telegram card ("Your channel or group, through a bot you create yourself."), press Connect. If you've connected before, the button is called Manage.

You can also type "telegram" in the search box in the top bar, then choose Connect Telegram.

What the marks on the Telegram card mean:

6.2 Filling in the form

Fill in these two fields:

Below the Target field there's a short hint about the entries above, including for private chats: the person presses Start (or sends /start) in your bot first, then you enter that chat's numeric ID (see B5).

Small things worth knowing:

• The token field hides what you type (it shows dots), just like a password field. That's normal. AutoPost doesn't have a button to show the token; some browsers (for example Edge) have their own eye icon.

• Spaces at the start and end of an entry are removed automatically. Inside a numeric ID, spaces and comma separators are removed too.

• If the token has the wrong shape, the browser stops you before sending. Its bubble shows the browser's own message (in Chrome, for example, "Please match the requested format.") followed by "Token format: digits, a colon, then about 35 letters/digits — e.g. 123456789:AAH…".

• An empty field is also stopped by the browser with its own message (for example "Please fill out this field.").

• At the top of the form there are the pills Sender active, Telegram, and N/3 accounts. The All platforms link at the very top of the page takes you back to the Social accounts page.

Fake example — not a real token.

6.3 Pressing "Test & connect"

Press the Test & connect button. AutoPost then checks, in order:

1. The entry format. The token and target aren't empty, the token looks right, the target is no longer than 200 characters, and the target format is recognized. Invite links, phone number links, and other links that aren't a channel/group are rejected right here.

2. The attempt limit. At most 5 attempts every 10 minutes. Typos stopped at step 1 don't count. Every attempt that passes the entry format check counts, whatever the result, including ones rejected because the target is "already connected", because there are already 3 Telegram accounts, or because of server problems.

3. The token, with Telegram. AutoPost asks Telegram whether this token belongs to a valid bot (a check called getMe).

4. The target, with Telegram. AutoPost asks whether the bot can find that target (a check called getChat). From this, AutoPost gets the channel/group/person name to use as the account label, and learns whether the group has topics.

5. The bot's send rights. AutoPost asks Telegram what role the bot has in that target (a check called getChatMember). In a channel, the bot must be an admin with the Post Messages right. In a group, the bot must already be in the group and allowed to send messages (as an admin, or as a member in a group that lets members send). If not, the connection is rejected and the account is not saved. For private chats, this check is skipped: a target that was found means the person has already pressed Start.

6. The 3-account limit. You don't have 3 Telegram accounts yet.

7. No duplicates. The same target hasn't been connected in your AutoPost account before (even with another bot).

8. Saving. The token is encrypted (AES-256-GCM) and then saved, together with the topic number if you chose a topic.

Each call to Telegram waits at most 20 seconds.

If the server warning box is shown (see 9.7), the form and the Retest button are disabled.

6.4 Signs of success

If everything passes, a green message appears:

For a topic group, the name in that message ends with its topic, for example “Diskusi Warga · topik #7” or “Diskusi Warga · topik General” (see B4).

Sometimes there's a note under the green message. The account is still saved; the note just tells you something to watch out for. Notes you may see:

• "Posts will go to topic #7 in this topic group." — the topic from your message link was saved.

• "This group has topics: posts go to the General topic. For another topic, connect with the link of a message inside that topic (long-press the message → Copy link)." — no topic was chosen.

• "The topic number was ignored because this target isn't a topic group." — the pasted link contained a topic number, but the target is a channel or a group without topics.

• "The bot isn't an admin and isn't allowed to send photos, videos, and files (including photos over 10 MB) in this group yet, so posts with … will fail. Make the bot a group admin to be safe." — the list of media types varies; posts without media still go through.

• "The bot isn't an admin: if topic #7 is closed, the bot's posts there will be rejected. Make the bot a group admin to be safer." (or "…if the General topic is closed or hidden…") — a warning for topic groups.

• "The bot's 'Remain anonymous' admin right is on, so its messages will appear under the group's name. Turn that right off if you want the bot's name to show."

• "The bot's send permission couldn't be confirmed (Telegram: …). Send one test post to make sure." — Telegram answered unexpectedly when asked about the bot's rights.

The new account appears in the right-hand card, Connected accounts:

What's on the account card:

• Account label — taken automatically from Telegram; you don't need to type it. For channels/groups, the label is the channel/group name. For private chats, the label is that person's username (without @) if they have one; their first name is only used if they have no username. If there's neither, it says Tanpa nama (stored in Indonesian; it means "no name"). If the channel name changes, press Retest so the label is updated too. For topic groups, the label ends in · topik #N or · topik General.

• Telegram · @username — the target's public address (if any).

• Masked token — only the first 4 and last 4 characters, for example 1234••••••••x9Qz. The full token is never shown again. If this spot says token can't be opened, the server can't open the stored token: Disconnect the account and connect it again.

• connected … — the date and time (WIB) when the account was connected, without the year and without the word "WIB", for example connected Sep 27, 02:05 PM.

• Status pill — connected, needs reconnecting, or has a problem (see 8.1).

• The Retest and Disconnect buttons.

The account also appears on the Social accounts page, in the "Connected accounts" list.

6.5 What "N/3 accounts" means

The Telegram page has an N/3 accounts pill. It means you've connected N of at most 3 Telegram targets in your AutoPost account. This limit applies per platform: 3 for Telegram, separate from other platforms.

• The three targets can use the same bot or different bots.

• Once you have 3, the form is disabled and you see the text "Full: disconnect an account first to add another."

7. Step E — Send and schedule to Telegram

7.1 Choosing a Telegram account as a target

1. Open the New post menu (on phones: Write).

2. Write the post in the Text field. If needed, fill in Link (optional) and add media under Media (optional).

3. In the Send to section, look at the account buttons. Checked accounts (blue, with a ✓) will receive the post.

If there are no accounts yet, that section shows "No accounts connected yet" and a Connect account link. A post without accounts can only be saved as a draft.

7.2 Character limits

Telegram has two different limits:

Important things:

• The counter in the Limits per platform card adjusts itself: without media the row is Telegram …/4096; as soon as media is added, the row becomes Telegram · photo/video caption …/1024. The number already includes the Link entry. If you go over, the number turns red and below it you see how many characters will be cut when sent — this is a warning, not a rejection: the post can still be saved and sent.

• Some emoji count as 2 characters. Cutting doesn't split a single emoji or a flag, but combined emoji (for example family emoji or emoji with a skin tone) that fall exactly at the cut point may appear split. If your text is close to the limit, check its end in the preview.

• The Link field is added at the end of the text (after one blank line), if the link isn't already in the text. The link is counted by the Telegram counter in the composer, and counted when cutting. If text + link go over 4,096 characters (without media) or 1,024 characters (with media), it's the text that is cut at a word boundary, while the link from the Link field stays whole at the end (as long as the text still keeps at least 40 characters). A link you type yourself inside the text won't be split in two: if the cut point falls in the middle of the address, the whole address is dropped. A link at the end of the text may be dropped too. Tip: put important links in the Link field or at the start of the text, or keep the text short.

• The Link to post feature already counts the 1,024/4,096 limit including the link.

• AutoPost's general limit for all platforms: 10,000 characters per post.

7.3 Text format, links, and previews

• Text is sent as plain text. Marks such as *bold*, _italic_, or <b> appear as is, and don't turn into bold or italic text.

• Buttons under the message (inline buttons) aren't supported yet.

• For posts without media, Telegram shows a link preview card automatically. Telegram uses the first link in the text for the preview card. The Link field is placed at the end, so if the text already contains another link, the preview shows that first link, not the Link field. The preview also only appears if the target site provides a title and an image.

• For posts with media, the text becomes the photo/video caption and there's no link preview card.

• Messages are sent with the normal notification sound (there's no silent send option yet).

7.4 Photos and videos

One post can carry several media. Two to ten photos/videos are sent as a Telegram album; the caption (text) appears on the first media and is at most 1,024 characters. In an album, photos must be 10 MB or less (larger photos fail instead of being sent as files) and all uploaded files together at most 100 MB. GIFs can't go in an album: they're left out with a note — send a GIF as a separate post.

How to add media:

• Upload from gallery: JPG, PNG, WebP, GIF photos, or MP4, MOV videos, up to 50 MB.

  • For Telegram, JPG or PNG is safest. AutoPost accepts WebP, but Telegram may reject it as a photo.

  • iPhone photos in HEIC format are rejected by the composer ("…: choose a JPG/PNG/WebP/GIF photo or an MP4/MOV video."). Convert the file to JPG first, or set the iPhone camera to Most Compatible (Settings → Camera → Formats).

  • Once uploaded, you see media attached ✓ (with several media: N media items attached ✓ — the cover shows first) and a Remove media (Remove all media) button. Each media card also has its own remove button.

• Add from a URL: paste an http:// or https:// link directly to the image/video file on the internet, not a web page, then press Add (for example a YouTube link or an article page will fail). AutoPost guesses the media type from the end of the address: a video is only recognized if the address ends in .mp4 or .mov (also .m4v, .webm); anything else is treated as a photo, so a video with another address will fail. Safest: Upload from gallery.

• The Image studio or a design card made by AutoPost. The image is added to the media list with the message "Image saved & ready to send with this post." (or "Image added as media item N & ready to send with this post." if there's already media).

How AutoPost sends media to Telegram:

Other photo requirements from Telegram: width + height at most 10,000 pixels, and the ratio of the long side to the short side at most 20:1. The Photo check panel in the composer warns you if a photo goes over these limits.

Telegram reprocesses photos sent as photos, so their quality and resolution may drop. Full quality is only kept when sent as a file, and AutoPost doesn't offer that option yet (except automatically for photos over 10 MB).

Alt text. Each media card has an Alt text button (an image description for screen readers; the button only appears when an Instagram, Threads, Pinterest, or X account is checked). Its content isn't sent to Telegram; only Instagram, Threads, Pinterest, and X use it. But its 1,000-character limit still applies: alt text filled in earlier still blocks saving, even if you later leave only Telegram selected. Clear it or shorten it.

AI photo check. If you press Check with AI in the Photo check panel (an AI key is needed), the result also applies to Telegram posts:

• If the verdict is on hold, the save, schedule, and send buttons are locked, with the note "Save, Schedule, and Send now are disabled: …". Replace or remove the photo first.

• If there are serious findings, the dialog This photo has serious findings appears when you send or schedule. Check I have the rights/permission for this photo. then press Continue sending / Continue scheduling, or press Cancel.

7.5 Three ways to save: draft, schedule, send now

The composer has three options. It takes two steps: choose the mode first, then press the big button below it.

While it works, the big button changes to Saving… or Sending…. After it succeeds, the Text and Link fields and the media are cleared, ready for the next post. If Send now fails for every account, the fields are kept so you can fix them — but the post is already on the Posts page; use Resend failed there instead of pressing Send now again.

Scheduling

1. Choose Schedule.

2. Fill in Date & time (WIB, UTC+7). This time is always read as WIB, whatever your device's time zone. If you're in WITA (UTC+8) or WIT (UTC+9), subtract 1 or 2 hours.

3. Press Schedule post.

Schedule rules:

• It can't be in the past, and at most 1 year from now.

• AutoPost checks schedules every minute. A post is usually published at most about 1 minute after the scheduled time, and may take a little longer if the queue is busy.

• Schedules are managed by AutoPost, not by Telegram's own "scheduled messages" feature. So scheduled posts aren't visible in the Telegram app before they're published.

• You can see scheduled posts in Posts → All posts (the Scheduled tab) and in the Schedule calendar menu.

Changing or canceling a schedule. AutoPost can't edit scheduled posts yet (only drafts can be reopened with Open in composer). Instead: on the Posts page, press the X button (Delete post) on that post, choose Delete (or Cancel), then create a new post with the right content/time. While it works, the button reads Deleting…. Deleting a post in AutoPost does not delete a message that's already published in Telegram.

Send now

The post is saved first, then sent right away. The messages you see:

1. "Saved — sending to the selected accounts…"

2. Then a summary of the result, for example "Sent to 1 account."

Drafts and scheduled posts can also be sent early with the Send now button on the Posts page.

7.6 Tracking status on the Posts page

Open the Posts → All posts menu (on phones: Posts). It has the tabs All, Drafts, Scheduled, Sent, Partial, Failed, and Canceled. (The Posts → Pin approval menu is only for Pinterest.)

Extra pills on each post:

• N accounts — the number of target accounts.

• N media — the post is an album (cover = first media).

• N sent / N failed — the breakdown when the status is partial or failed.

• N retrying automatically ± 02:15 PM — some accounts are waiting for a retry, with the estimated time.

• The time: scheduled … WIB, sent … WIB, or created … WIB.

• Details per account (N) — the list of accounts with the reason they failed or are being retried, or a note about a send that succeeded (for example a caption cut at 1,024 characters). If anything failed, these details open right away; if they only contain notes, press the heading to open them.

Each post also has an X button to delete it (see Scheduling).

Other messages that may appear on this page:

• No posts here yet — that tab is empty.

• Posts couldn't be loaded. Reload this page in a moment. — a temporary problem while reading the list.

7.7 Send result summary

After you press Send now or Resend failed, one of these messages appears:

7.8 Automatic retries and resending

Automatic retries. If a failure is temporary (for example Telegram is rate-limiting, Telegram's servers are having trouble, or the connection dropped before the message was sent), AutoPost tries again by itself:

If Telegram asks for a longer wait, AutoPost follows Telegram's request. If it still fails after 4 attempts, the status becomes failed. While it waits, the post card on the Posts page shows the pill "N retrying automatically ± 02:15 PM".

Permanent failures (for example the token was rejected, the bot isn't an admin, the file is too large) are not retried automatically. Fix the cause first. The details for each message are in the "Retried automatically?" column in 9.2 and 9.4.

If a sending process stops partway (for more than 15 minutes), AutoPost recovers it by itself and tries again. Because of this, in rare cases a message may be published twice (if the message had actually been published before the process stopped). Delete one of them in Telegram.

Resend failed. On the Posts page, posts with the partial or failed status have a Resend failed button. This button:

• only resends to accounts that failed (accounts that already received it are not sent to again);

• starts accounts that failed again from the first attempt;

• tries accounts that are waiting for a retry right away, without resetting their attempt count.

7.9 Where to see why a send failed

Main place: the Posts page → Details per account. Every post card that has a reason or a note shows a Details per account (N) section:

• One row per account: the platform logo, the account name, its state (failed, retrying, skipped, or sent · note), then the reason in a full sentence (the same message as in the 9.4 table). Rows for accounts that are retrying end with "(retrying automatically, attempt N of 4)".

• Accounts that failed are listed at the top, and their details open right away. If they only contain notes about sends that succeeded (for example that the caption was cut at 1,024 characters, or that a photo was sent as a file), the details are collapsed; press the heading to open them.

• Accounts that have been disconnected still appear, with the name Disconnected account.

• Drafts don't show details.

Second place: red text under the account name in Social accounts → Telegram → Manage. It shows the latest failure reason for that account (not per post). If another send fails after that, the text is replaced; if a send succeeds after that, the text is removed. Not every reason appears here (see the Where is it shown? column in 9.4) — the details on the Posts page are always more complete.

Other places that give hints, but not reasons:

• The inline message after you press a send button only contains a summary of the numbers (see 7.7).

• Notifications on the bell icon (see 7.10) only tell you the result.

If the number of failures goes up but the details are empty, reload the Posts page. If they're still empty, check that the media is still in storage and the account hasn't been disconnected, then press Resend failed. If it still fails, contact us (section 13).

7.10 Notifications

AutoPost tells you the results of sends through the bell icon in the top bar and the Notifications page:

• A notification appears when the result is final (nothing is waiting for a retry anymore).

• "Open the Posts page to see why.": the reason is in Details per account on that post (see 7.9).

• You can choose the types on the Notifications page: Successful sends, Failed sends (both are on from the start), and Feature news & tips.

• Notifications appear inside AutoPost, and — if you press Turn on for this device under Notifications on this device — also as device notifications for failed sends. There are no alerts through Telegram or email.

7.11 Auto post

The Auto post feature creates posts automatically and sends them through the same queue.

• Auto posts are sent in the next round (about 1 minute).

• On the auto post's edit page, check the Telegram accounts you want to send to.

• Telegram accounts whose status isn't "connected" are skipped without notice. Keep your accounts healthy.

• If no connected account is checked, you see the message: "No connected target account yet. Check accounts on the auto post's edit page."

• An auto post design card (4:5, 1080 × 1350 pixels) is only created when there's no image and (a) the auto post's image mode is set to card, or (b) Instagram/Pinterest is also selected. If it's created, that card is also sent to Telegram.

• The name written on the card (or in the image branding) is taken from the label of the first checked account in the auto post, whatever its platform, so it may not be your Telegram channel name.

7.12 What you can't do for Telegram yet

So there are no surprises, here's what isn't supported yet:

• Sending to several topics of one topic group (one group = one topic per AutoPost account; see B4).

• Bold/italic text (Markdown/HTML) and buttons under messages.

• Silent sends, content protection (no forwarding/saving), polls, stickers, audio, and animations.

• Editing or deleting messages already published from AutoPost. Do it directly in Telegram.

• Changing a post that's already scheduled or sent. Delete it and create it again (see Scheduling); drafts can be edited with Open in composer.

• Sending photos as full-quality files by your choice (only automatic for photos over 10 MB).

• Telegram channel view statistics.

• Changing the token without disconnecting the account (see 8.3).

• Finding the ID of regular groups and private chats from inside AutoPost (for channels/supergroups, just paste a message link; see Step C).

• Per-Pin approval only applies to Pinterest, not Telegram.

8. Managing Telegram accounts

Everything is managed in Social accounts → Telegram → Manage.

8.1 What account statuses mean

An account's status can change from two sources: sending and Retest. Each judges it differently.

If an account isn't "connected", the Social accounts page shows a red banner:

The status goes back to connected automatically when Retest passes or a send to that account succeeds.

8.2 Retest

The Retest button checks the account again without sending any message:

1. It opens the stored token.

2. It asks Telegram whether the token is still valid (getMe).

3. It asks whether the target can still be found (getChat).

4. It checks the bot's send rights in that target (getChatMember), the same as when connecting (see 6.3). The stored topic is used too.

5. If it passes: the status becomes connected, the red text is removed, and the label (including the topic suffix) and the @username are updated from Telegram.

If it passes, you see this message:

Below it there may be the same notes as when connecting (see 6.4).

If it fails, a red message "Failed: …" appears at the top of the page, and the reason is also written in red under the account name. The status changes according to the 8.1 table: the token check fails → needs reconnecting; the target check fails → has a problem. If the cause is a temporary problem ("Telegram didn't answer within 20 seconds", "Telegram's servers are having trouble…", "Couldn't reach Telegram from the server", or rate limiting), just press Retest again a little later.

• Retest is not limited in number.

• Retest now also checks the bot's send rights (channel: admin with the Post Messages right; group: allowed to send messages). Media permissions, slow mode, paid messages, and closed topics aren't checked yet, so the sure way is still Resend failed or a test post.

When to use Retest:

• After you add the bot back to the channel/group, or fix its permissions.

• After renaming the channel, so the label in AutoPost changes too.

• After unblocking the bot in a private chat.

8.3 Changing the token

You need to change the token if it leaked, was lost, or you deliberately created a new one.

In Telegram:

1. Open @BotFather.

2. Send /token, then choose your bot. Or send /mybots → choose the bot → API Token → the option to revoke the current token (for example Revoke current token). Menu names may differ.

3. Copy the new token.

4. Make sure the token really changed. Compare the last 4 characters of the new token with the old one (AutoPost shows the old token masked on the account card, for example 1234••••••••x9Qz). If they're the same, the token has NOT changed yet: use /mybots → choose the bot → API Token → Revoke current token (or /revoke). Once it's really revoked, the old token stops working.

In AutoPost (there's no "change token" button yet, so you disconnect and connect again):

1. First note down the scheduled posts going to this account (see Posts → All posts, the Scheduled tab, or the Schedule calendar menu). Disconnecting the account also deletes the schedules to that account.

2. Press Disconnect on the old account, then Yes, disconnect.

3. Connect again with the new token and the same target (Step D).

4. Recreate the scheduled posts you noted, and check this account again in auto posts if needed.

Until the new token is entered, every send to this account fails with the message "Telegram doesn't recognize the bot token…" and the account becomes needs reconnecting.

Also make sure the Telegram account that owns the bot uses Two-Step Verification (see Protecting the bot owner's Telegram account).

8.4 Group became a supergroup

If you see the message "This group has become a supergroup, so its address changed — reconnect this account.":

1. First finish any group settings changes still left (for example turning on Topics), then copy the link of one message in that group (Step C, method 1). A supergroup already has a t.me/c/… link. For a public group, @groupname is enough.

2. Note down the schedules going to this account, then Disconnect the old account.

3. Connect again with the same token and that message link (or the new ID starting with -100).

4. Recreate the schedules you noted.

AutoPost doesn't move to the new ID automatically.

8.5 Disconnecting an account

1. Press Disconnect on the account card.

2. The question "Disconnect this account? Its token is deleted too." appears, with the buttons Yes, disconnect and Cancel. The Cancel button (or the Esc key on the keyboard) cancels.

3. Press Yes, disconnect (while it works, the button reads Processing…). You see the message: "Account disconnected — its row and token are gone from the database." This message also appears if the account had already been disconnected in another tab.

What gets deleted from AutoPost too:

• The account and its token.

• All post targets for that account, including the send result history and schedules that haven't run yet.

• That account's selection in auto posts.

Scheduled posts whose only target was that account become failed when their time comes (a Sending failed notification, and a post card without an account pill). If you press send on such a post, you see the message "No target accounts yet — choose target accounts when composing the post."

Once disconnected, the token and account data are removed from the running system right away. Copies in database backups made regularly are only removed when those backups are rotated according to our backup schedule.

What does NOT get deleted:

• Messages already published in the Telegram channel/group. Delete them directly in Telegram if needed.

• Your bot in Telegram. The bot still exists and is still an admin. Remove the bot from the channel/group, change its token (/token), or delete the bot (/deletebot) in @BotFather if you no longer use it.

8.6 Adding a 2nd and 3rd account

Repeat Step B and Step D for another target. You can:

• use the same bot for several channels/groups (the bot must be an admin in each), or

• use a different bot for each target.

You can't connect the same target twice (even with a different bot): you see the message The target "X" is already connected. For topic groups, the message adds a tip about changing the topic (disconnect, then connect again with a message link from the new topic); one topic group can only be sent to one topic per AutoPost account.

The limit is 3 Telegram targets per AutoPost account. To add a fourth, disconnect one first.

9. Troubleshooting

Look for the message you see in the tables below. Messages are written exactly as they appear in AutoPost. The letters N, X, or Y stand for real numbers or names.

On the Telegram page, failure messages start with the word "Failed:" in red.

9.1 When filling in the form (browser messages)

9.2 When pressing "Test & connect", "Retest", or "Disconnect"

Many messages in this table can also appear when sending, as red text under the account name. The last two columns explain what happens if the message appears when sending:

• Retried automatically? — whether AutoPost tries again by itself (see 7.8).

• Status becomes needs reconnecting? — whether the account status changes to needs reconnecting.

• A — means the message doesn't appear when sending (only when connecting, on Retest, or on Disconnect).

Status changes caused by Retest are explained in 8.1.

9.3 When composing a post

The Photo check panel (appears when Telegram is selected):

9.4 When sending

Besides the messages in 9.2 (which can also appear when sending), here are the messages specific to sending.

• The Retried automatically? column shows whether AutoPost will try again by itself.

• The Where is it shown? column shows where you can read the message. Details = in Details per account on the post card on the Posts page — every message in this table appears there. Red text = also shown under the account name in Social accounts → Telegram → Manage (see 7.9).

The note "The … MB photo exceeds Telegram's photo limit (10 MB), so it was sent as a file (document)." isn't an error; see 9.8. The same goes for the text-cutting note ("The text exceeded Telegram's limit for … characters, so N characters at the end were cut at a word boundary and replaced with "…".): the send still succeeds, and both appear as sent · note in Details per account on the Posts page.

9.5 Messages after pressing a send button

Other send result summaries are in 7.7.

When deleting a post (the X button on the Posts page):

9.6 Original messages from Telegram

If Telegram sends a reason that AutoPost hasn't translated yet, AutoPost shows Telegram's original text (in English, up to 160 characters). The ones you're most likely to see:

Messages starting with Forbidden usually give the account the needs reconnecting status. Once the cause is fixed, press Retest.

Other original messages not in this table aren't retried automatically. Copy the text if you contact us.

9.7 Server warning box

If a warning box titled "The server encryption key isn't set up yet" or "A database migration hasn't been run" appears on the Telegram page, or you see a technical message that mentions the encryption key, a server configuration file, or a database migration…

…it's a problem on our server, not your mistake. The form and the Retest button are temporarily disabled. Don't keep trying; contact us (section 13) and copy the message shown.

9.8 Problems that show no message

10. Security and privacy

10.1 Protecting the token

• Token = full control of the bot. Treat it like a password.

• Paste the token only on the AutoPost Social accounts → Telegram page, at the address https://app-autopost.solusikecerdasankomputasi.com. Check the address in your browser before pasting.

• Don't send the token by chat or email to anyone, including us.

• Don't keep the token in screenshots, shared documents, or unlocked notes.

• Make the bot an admin only in the channels/groups you actually want to post to, with only the rights it needs: in a channel, Post Messages is enough; in a group, just make it an admin and turn off the other rights (delete messages, ban users, add admins, and the like).

• If you use getUpdates, follow the safety steps in Step C, method 2.

• Protect the Telegram account that created the bot with Two-Step Verification, and for organizations, create the bot from an account owned by the organization (see Protecting the bot owner's Telegram account).

10.2 If the token leaks

Do this right away, in order:

1. Change the token in @BotFather: /token (or /mybots → bot → API Token → Revoke current token). Make sure the token really changed: the last 4 characters of the new token must differ from the old token (see 8.3). Once revoked, Telegram rejects the old token.

2. Reconnect in AutoPost with the new token (8.3).

3. Check the channels and groups where the bot is an admin. Delete messages you didn't send. Remove the bot from channels/groups you no longer use.

4. If the bot has already been misused, consider deleting the bot (/deletebot, can't be undone), then create a new bot.

5. If you suspect the Telegram account that created the bot was broken into (not just the token), secure that account first and turn on Two-Step Verification; otherwise, the attacker can get a new token again through @BotFather.

10.3 What AutoPost stores and how it's protected

• The token is never shown in full again. The page only shows the first 4 and last 4 characters.

• AutoPost doesn't read messages in your channels or groups. AutoPost only sends.

• AutoPost uses Telegram's official route. No Telegram passwords or sign-in cookies are stored.

• The AutoPost sending server runs in Singapore, and your data (including the encrypted token, posts, and uploaded media) is also stored in Singapore. Telegram may process post content on servers outside Indonesia.

• Media you upload is shared with Telegram through signed links that are valid for a limited time (1 hour), not permanent public links. Large media is uploaded directly by the AutoPost server to Telegram.

• Media from Add from a URL (outside links) is fetched directly by Telegram from that site; that site may record the requests from Telegram.

Full details are on the AutoPost Privacy Policy (/privasi) and Terms of Use (/ketentuan) pages.

10.4 Your data rights

• Deleting one Telegram account: press Disconnect. The token and data of that account are removed right away from the running system (8.5).

• Deleting your whole AutoPost account: the Settings → Delete account menu. To confirm, type HAPUS (all capital letters) and your password. All social accounts with their encrypted tokens, posts, schedules, send results, and the media you uploaded are removed immediately from the running system.

  • Copies in database backups made regularly are only removed when those backups are rotated or destroyed according to our backup schedule. Until then, backups are only used for recovery after an outage.

  • Not removed: messages already published in Telegram, and the bot you created yourself. Delete or revoke them directly in Telegram.

• Other rights (access, getting a copy of your data, correcting it, withdrawing consent, objecting) are explained in Privacy Policy → Your rights. Send your request from your account's email address; we respond within 3 × 24 hours after the request is received and your identity is verified.

• Can't sign in? Send a deletion request from your registered email address (see section 13).

11. Frequently asked questions

1. Does connecting Telegram cost anything?There's no charge from Telegram. The bot is created for free through @BotFather, and AutoPost uses the official Bot API route.

2. Why do I have to create my own bot? Can't I use my personal Telegram account?Telegram's official route for apps like AutoPost is through a bot. With a bot, AutoPost doesn't need your Telegram account's password or sign-in code.

3. I pasted the token, but it says "Telegram doesn't recognize the bot token". Why?Usually the token is cut off, has a space, or has been changed in @BotFather. Copy the latest token from @BotFather (/mybots → bot → API Token), then try again.

4. Can one bot be used for several channels?Yes. Make the bot an admin in each channel, then connect each channel as a separate account (up to 3 Telegram accounts).

5. My channel is private. What goes in the Target field?The easiest way: copy the link of one message in the channel (https://t.me/c/1234567890/15) and paste that link as is. AutoPost turns it into the ID -1001234567890 for you. You can also type that ID yourself. See Step C.

6. Can I use an invite link (t.me/+…) as the target?No. AutoPost rejects it with the message "A bot can't use an invite link as a target — …". Copy the link of one message in that channel/group (press and hold the message → Copy Link), then paste that message link.

7. Does the bot have to be an admin in a group?Not required, but strongly recommended. A bot that's a regular member is subject to all member restrictions: message permissions, the separate Photos/Videos/Files permissions, slow mode, and paid messages (Stars). A bot that is a group admin can automatically send messages and media without those restrictions (see B3).

8. AutoPost said it connected, so why did the first send fail?When connecting, AutoPost checks the token, the target, and the bot's right to send messages. What isn't checked yet: permission to send photos/videos/files in groups, slow mode, paid messages, and closed topics. The bot's rights can also change after connecting. Read the red text under the account name, fix the cause (channel: Post Messages; group: make it an admin), press Retest, then Resend failed.

9. Why was my text cut off in Telegram?If the post has a photo or video, Telegram limits the caption to 1,024 characters. AutoPost cuts the rest at a word boundary, adds …, keeps the Link field whole, and saves a note of how many characters were cut. Without media, the limit is 4,096 characters.

10. Can I choose a topic in a topic group?Yes. Copy the link of one message inside that topic (press and hold the message → Copy Link), then paste it into the Target field when connecting. Without that, posts go to the General topic. See B4.

11. Can I send several photos at once (an album)?Yes. Add 2 to 10 photos/videos in New post; AutoPost sends them as one album. GIFs can't be part of an album, and albums can't have buttons under the message.

12. Can AutoPost edit or delete messages already published?Not yet. Edit or delete them directly in the Telegram app.

13. Which time zone do scheduled times follow?Always WIB, whatever your device's time zone.

14. How punctual are scheduled posts?They're usually published at most about 1 minute after the scheduled time.

15. If Telegram has an outage, are my posts lost?No. For temporary problems, AutoPost tries again automatically after 1, 5, and 30 minutes (4 attempts in total). If it still fails, you can press Resend failed.

16. Are channel messages deleted too if I disconnect the account or delete my AutoPost account?No. Messages already published stay in Telegram. But schedules to that account that haven't run yet are deleted from AutoPost.

17. Can AutoPost read the messages in my group?No. AutoPost only sends; it doesn't read channel or group messages.

18. How do I change the token without losing my settings?There's no change-token button yet. Note down the schedules to that account, Disconnect the account, connect again with the new token, then recreate the schedules. See 8.3.

19. Does "Pin approval" apply to Telegram?No. Per-Pin approval is only for Pinterest. Telegram posts are sent directly on schedule or when you press Send now.

20. My account says "needs reconnecting". Is that different from what the Social accounts page shows?No. Both pages use the same label, and it means the account needs fixing. Read the red text under the account name, fix the cause, then press Retest.

21. Why am I asked to wait when I try to connect?For security, AutoPost allows 5 connection attempts every 10 minutes. Wait for the time given.

22. Can AutoPost send to other people's private chats?Only if that person has opened your bot and pressed Start, and you know their numeric ID. Only send to people who have agreed to receive messages.

23. How do I change or cancel a scheduled post?Scheduled posts can't be edited yet (only drafts can be reopened with Open in composer). Delete that post with the X button on the Posts page, then create a new post. See Scheduling.

24. Where can I see why a send failed?On the Posts page: open Details per account on that post's card. The latest failure reason for each account is also shown as red text in Social accounts → Telegram → Manage. See 7.9.

25. Can I put my bot's username in the Target field?No. The target is the channel, group, or person who receives the messages. Telegram doesn't let bots send messages to bots, and AutoPost rejects your own bot's ID on Test & connect.

12. One-page checklist

Print or save this page, then check the items one by one.

Preparation

• The Telegram app is installed and the account is active.

• The target channel/group exists, and I'm authorized to manage it.

• I can sign in to AutoPost.

Step A — Bot

• Opened @BotFather (blue check mark) and pressed Start.

• Sent /newbot and entered the bot's name.

• Entered the bot's username (5–32 characters, uppercase/lowercase Latin letters, digits, _, ending in bot).

• Copied the token in full and stored it in a safe place.

• Two-Step Verification is on for the Telegram account that created the bot (for organizations: the bot was created from the organization's account).

Step B — Target (choose what applies)

• The channel/group settings are final (Topics, public address, admins) before finding the ID.

• Channel: the bot is an admin with the Post Messages right.

• Group: the bot is made an admin (just make it an admin; other rights off, Remain Anonymous off). If it stays a regular member: message, Photos, Videos, and Files permissions open, slow mode and paid messages off.

• Topic group: the target topic (or General if no topic is chosen) is open and not hidden.

• Private chat: the target person has pressed Start in the bot.

Step C — ID (private targets only)

• Private channel/supergroup: copied the link of one message (t.me/c/…); this link can be pasted into AutoPost directly.

• Topic group: copied the link of one message inside the target topic.

• Regular group/private chat: ID from getUpdates in an incognito window, taken from the "chat" part (not "from"), then the window was closed.

• (Recommended) The token was changed after using getUpdates, and its last 4 characters differ from the old token.

Step D — AutoPost

• Opened Social accounts → Telegram → Connect/Manage.

• Pasted the token (without the word bot in front, without spaces).

• Entered the target: @name, t.me/name, the link of one message, or a numeric ID (not an invite link, not a bot username).

• Pressed Test & connect; the green message "… was connected …" appeared (read the note below it, if any).

• The account shows the connected status (the bot is proven to be in the target and allowed to send messages).

Step E — First post

• In New post, only the accounts I want are checked.

• Text + link ≤ 4,096 characters (without media) or ≤ 1,024 characters (with media).

• JPG/PNG photos ≤ 10 MB; MP4 videos ≤ 50 MB.

• The Alt text field is empty or ≤ 1,000 characters.

• Sent one short test post with Send now; "Sent to 1 account." appeared.

• The test post is visible in the Telegram channel/group.

• For schedules: the time is entered in WIB.

Security

• The token isn't shared with anyone and isn't in any screenshot.

• The bot is only an admin in the channels/groups it needs.

• The Failed sends notification is on in the Notifications page.

• I know where to see why a send failed: Details per account on the Posts page (and the red text under the account).

13. Help and contact

If your problem isn't answered in section 9 or section 11:

• Email: halo@autopost.solusikecerdasankomputasi.com. Send it from the email address registered to your AutoPost account.

• Include: the message shown (copied exactly, or a screenshot without the token), the type of target (public/private channel, group, topic group, or private chat), and roughly when it happened (WIB).

• Never include your bot token in an email. We don't need it to help you.

Related pages in AutoPost:

• Privacy Policy — /privasi

• Terms of Use — /ketentuan

• Deleting your account — /hapus-akun

Telegram's official guide to bots: https://core.telegram.org/bots/features#botfather

AutoPost isn't affiliated with Telegram. Telegram is a trademark of its owner.

© 2026 PT Solusi Kecerdasan Komputasi. This guide was updated on 3 October 2026. The Telegram and AutoPost apps may change at any time.