Telegram member add bot, and what your code can call

By Mara Vogel Published 7 August 2026 9 min read

The first page for telegram member add bot sells software. The first page for python telegram bot add member to channel ships code. Both describe the same operation, and neither names the interface underneath it — which is the one detail that decides whether the thing being built is a bot at all.

The split is visible at the import line. python-telegram-bot and aiogram wrap the HTTP Bot API. Telethon and Pyrogram implement MTProto, the protocol the Telegram apps themselves speak. A tutorial that imports Telethon is not writing a bot whatever the filename says; it is automating somebody's account, and the difference shows up later as a limitation on a phone number.

Every figure below names the Telegram page it came from. Where Telegram documents nothing — and on how many members an account may add, it documents nothing at all — this guide says so instead of borrowing a number. The editorial standard behind that is published alongside the guides.

What is a telegram member add bot?

A telegram member add bot is software that reads a member roster out of one Telegram group and writes those accounts into another, one at a time, with a pause between each write. The name is wrong in one specific place. No bot performs the operation, because a Telegram bot has no add-member method available to it — the software signs into a user account and issues the calls from there.

Search demand arrives in every word order the phrase allows. Queries for bot add member telegram and add member bot telegram return the same page as the head term: an Apify actor, a multi-account Chrome extension, two or three desktop products, and a knowledge-base article from a vendor selling one of them. Across those results, not one number is traced to a Telegram document.

A second product ranks in the same space and works nothing like the first — the paid-membership bot that takes a payment, issues a link, and removes the member when the subscription lapses. That one really is a bot. The invite-bot guide separates the two products and covers the invite-link parameters in full; this guide stays on the code.

Can a Telegram bot add a member to a channel?

No. A telegram bot add member to channel operation has no method behind it. The Bot API reference publishes banChatMember, unbanChatMember, restrictChatMember, promoteChatMember, getChatMember and getChatMemberCount. Those methods remove, limit, promote, read and count. None of them adds. A bot holding every administrator right in the channel still cannot place an account into it.

The right that sounds like it should grant this is can_invite_users, and what it actually covers is link creation. Telegram's description of the method is exact about the scope:

Use this method to create an additional invite link for a chat. The bot must be an administrator in the chat for this to work and must have the appropriate administrator rights.Telegram Bot API, createChatInviteLink

A link is an offer. The account on the other end decides whether to take it, and that decision is the step every telegram channel add member bot listing describes itself as removing. Removing it is the part that has no API surface. Sendhaus builds Telegram bots and automation against this reference, and the absence has held through every Bot API release to date.

Can a telegram bot add member to group?

No, and the group case fails a step earlier than the channel case. A telegram bot add member to group operation needs the bot to be in the group first, and Telegram's developer introduction sets that condition plainly: "Bots can't start conversations with users. A user must either add them to a group or send them a message first." A bot cannot join on its own, cannot invite itself, and has no add-member method once someone puts it there.

The refusal on the other side is documented too, as an error rather than a setting. Telegram's error list for the client-protocol invite method includes USER_PRIVACY_RESTRICTED — "The user's privacy settings do not allow you to do this" — and USER_NOT_MUTUAL_CONTACT, "The provided user is not a mutual contact." Both fire per account, silently, in the middle of a run.

What python telegram bot add member to channel actually returns

A search for python telegram bot add member to channel returns two families of library, and only one family has the call. Bot API wrappers expose no add-member method because there is no HTTP endpoint for them to wrap. MTProto clients expose one, and it executes against whatever account the session file belongs to. The results sit next to each other with nothing marking the difference.

The absence is checkable in the library documentation rather than inferred. The Bot class in python-telegram-bot lists approve_chat_join_request, promote_chat_member, get_chat_member_count, create_chat_invite_link and a dozen neighbours, and carries no add_chat_member at all. A wrapper cannot expose an endpoint that the API it wraps does not publish.

So the tutorial that answers this query opens with an api_id, an api_hash and a phone number rather than a token from @BotFather, and it does that because it has no alternative. The request underneath is channels.inviteToChannel, which Telegram documents on its client-protocol reference with a return type carrying a missing_invitees field — the API is built expecting some of the invitations to fail. The same protocol boundary decides what can be sent and to whom on the messaging side.

What a bot auto add member telegram tool does at runtime

A bot auto add member telegram tool runs a short loop: read the roster, take the next account, issue the invite call, sleep, repeat. The sleep is the product. Every telegram auto add member bot on the market competes on how long it waits and how it randomises the wait, because the underlying call is identical across all of them and Telegram returns the same errors to each.

What the loop collects is a mix. Some accounts return USER_PRIVACY_RESTRICTED. Some return USER_NOT_MUTUAL_CONTACT. Some return USER_CHANNELS_TOO_MUCH, which Telegram describes as "One of the users is already in too many channels/supergroups." Then the account issuing the calls starts collecting FLOOD_WAIT_X under error class 420, and the run stops being about the roster.

The consequence lands on the credential that issued the calls, and on MTProto that credential is a phone number belonging to a person. Telegram's Terms of Service prohibit using the service to send spam, and the API Terms of Service bind the developer of a client to the same conditions. A bot token can be revoked and reissued in a minute; a limited phone number is a different kind of problem, and the account that carries it is rarely the account that bought the tool.

The calls that do exist, and what they need

The supported path replaces the add with a join. A telegram add member bot built on the Bot API creates an invite link that requires approval, receives an update when somebody uses it, and approves or declines. Telegram shipped all three pieces in Bot API 5.4 on 5 November 2021. The member still joins by their own action, which is exactly the step the adder software exists to skip.

1. Create a link that asks for approval

   Call createChatInviteLink with creates_join_request set to true. Telegram's parameter note states the trade-off directly: "If True, member_limit can't be specified." An approval link is unmetered by design, because the approval is the meter.

2. Subscribe to the right updates

   The chat_join_request update arrives by default. The chat_member update, which reports every status change in the chat and is how a bot knows who actually joined or left, does not — an empty allowed_updates list receives all types except chat_member, message_reaction and message_reaction_count. A handler written for it fires never, and the bug reads like Telegram not sending anything.

3. Approve or decline, and record why

   Call approveChatJoinRequest or declineChatJoinRequest. This is the point where a real screening rule can run — a question answered, a payment matched, an allowlist checked — and where the join gets attributed to whichever link produced it.

4. Charge for the membership, if it is worth charging for

   Bot API 7.9, in August 2024, added createChatSubscriptionInviteLink. The subscription_period "must always be 2592000 (30 days)" and subscription_price runs from 1 to 10000 Telegram Stars. A price is a filter that no adder can imitate.

None of this produces members faster than an adder claims to. It produces members whose join is recorded, attributable and reversible, on a bot token that can be rotated. That is the trade being made, and it is worth stating rather than dressing up: the supported path is slower, and it is the one that survives. Audience growth work here is scoped on that basis.

When a telegram member add bot is the wrong tool

A telegram member add bot is the wrong tool whenever the goal is an audience rather than a number. Accounts written into a chat without being asked behave the way that description predicts — they mute, they never open, and they leave when the chat first reaches them. A member count and a reachable audience are two different assets, and only one of them responds to a broadcast.

Three more cases are worth naming before anyone budgets for one.

• The roster is not yours. No method turns a list collected from someone else's group into a permission. The consent rules that govern unsolicited commercial messaging sit above Telegram's terms, apply on their own schedule, and are unaffected by whichever API the message went through. Our own handling is set out in the privacy policy and the terms of service.
• The audience is not on Telegram. Telegram's share varies enormously by market. In several of them the answer to a growth brief is a different channel entirely, and no amount of adding fixes a platform mismatch.
• The membership is regulated. Financial promotion, health claims and gambling carry disclosure duties that a gated join can satisfy and a silent add cannot, because the record of consent is the thing being asked for.

Where an approval-gated channel does fit, the build is small and the running cost is mostly hosting. Broadcast work is quoted separately from it, and how the two are scoped is written down.

Frequently asked questions

Sources

• Telegram Bot Platform introduction — bots cannot start conversations; a user must add them to a group or message them first.
• Telegram Bot API reference — the membership method list, createChatInviteLink, approveChatJoinRequest, createChatSubscriptionInviteLink, and the allowed_updates default.
• Bot API changelog — Bot API 5.4 of 5 November 2021 for join requests; Bot API 7.9 of August 2024 for subscription invite links.
• Telegram API, channels.inviteToChannel — the published error table and the missing_invitees return field.
• Telegram API error reference — error class 420 and FLOOD_WAIT_X.
• python-telegram-bot, Bot class reference — the method list, and the absence of add_chat_member.
• Telegram API Terms of Service — the conditions binding a client developer.
• Telegram Terms of Service — the prohibition on sending spam.

Related guides

• Telegram invite member bot — the two products sold under one name, the documented invite-link parameters, and the daily figures Telegram never printed.
• Telegram scraper — where an adder's roster comes from, and the errors that end the collection.
• Telegram mass DM — every published send limit in its original wording, and the four things Telegram documents nowhere.
• Telegram shill bot — why no bot can join a group on its own, and the disclosure rules above Telegram's.
• Telegram mass report bot — reporting as a user-only method, and what the panels actually sell.
• All three service lines — broadcast, growth and automation, each with its declined-work list attached.
• Sendhaus — Telegram broadcast, growth and automation built on the platform's published limits.