- An auto inviter adds members to your own Telegram group from a sourced audience. It is not a magic "add 10k overnight" button — Telegram won't let it be.
- Three hard limits gate every invite: daily caps per account, PeerFlood rate limiting, and privacy settings that let users block being added entirely.
- The value is doing it under the limits: a steady trickle per account, across warmed, rotated accounts on proxies — not one reckless mass-add that bricks the account.
- TG:ON sources the audience from a built-in Vault of 2.9M+ chats and channels, so no separate scraper subscription. Remember: real users live in chats and groups, not broadcast channels.
- It's a local-first desktop app for Windows and macOS. Sessions, lead DB and LLM keys stay on your machine.
- Free trial: 3 days / 100 messages, no card. Plans: Starter $49, Pro $89, Agency $169 per month.
If you searched for "telegram auto inviter" or "telegram add members software," you already have the goal: take an audience you've sourced from relevant chats and drop them into your own group, automatically. The fantasy version of this is a slider that says "10,000" and a green Start button. That version doesn't exist — and anyone selling it is quietly selling you a banned account.
The honest version is more useful and a lot more durable. Telegram caps how many users one account can invite per day, rate-limits how fast you can invite even under that cap, and lets every user decide whether strangers can add them at all. An auto inviter that wins is one that respects those three walls and squeezes consistent throughput out of warmed, rotated accounts — week after week. Let's break down how it actually works, where it breaks, and how to do it without torching your accounts.
How auto-invite actually works
Auto-invite is a four-step pipeline, and only the last step is the "invite" everyone imagines. Skip the first three and you're inviting the wrong people, from the wrong accounts, too fast.
Source the audience. Before you can add anyone, you need a list of real users. In TG:ON that comes from the built-in Vault — 2.9M+ chats and channels, searchable by keyword, so you don't buy a separate scraper. You point it at active chats in your niche and collect members. Critical detail: you can only pull and add real users from chats and groups, not from broadcast channels — channels only have admins posting, not a member list you message as a user. How to build a clean source list from public chats without breaking ToS is covered in our technical parsing guide.
Warm the accounts. A fresh or bought account that starts inviting on day one looks like a bot and gets flagged. Warmup ramps activity gradually first. We're honest about what warmup does and doesn't do in "The warmup myth" and on the account warmer page.
Rotate. Telegram's daily invite cap is per account, so the only way to scale is to spread the load across several accounts — each doing a small, safe number. One account hitting a restriction shouldn't stall the campaign.
Invite under limits. The actual add happens as a randomized trickle, with the engine watching for PeerFlood and backing off automatically rather than hammering through the error.
Local-first, by design. TG:ON is a desktop app, not a cloud panel. Your account sessions, the lead database and your LLM API keys live in a local SQLite file on your own machine. You're not handing logins or your scraped audience to a third-party vendor, and your campaign doesn't stall because someone else's server had a bad night.
The limits and risks nobody advertises
This is the part the "add 10k members" ads skip. Telegram has spent years tuning anti-abuse, and inviting strangers into a group is one of the most heavily watched actions on the platform. Three walls gate every campaign:
Daily invite caps. Each account can only add a limited number of users per day before Telegram stops the action. The number isn't published and it shrinks for new or low-trust accounts. Pretending the cap isn't there is how people brick accounts in an afternoon.
PeerFlood / "Too many requests." Even under the daily cap, inviting too fast trips a rate limit. You'll see PEER_FLOOD or a flood-wait, and the right response is to slow down and rotate — not to retry in a loop, which only deepens the restriction.
Privacy settings. A large share of Telegram users set "who can add me to groups" to My Contacts. Those people literally cannot be invited by a stranger — the API rejects it. No tool overrides this; it's a hard user-side block, and a chunk of any sourced list will simply be unaddable.
Read the errors correctly. If you start seeing USER_BANNED_IN_CHANNEL across many chats at once, that's almost always not a per-group ban — it's an account-level @SpamBot restriction showing up everywhere that account operates. A hundred such errors usually means one restricted account, not a hundred bans. What actually trips @SpamBot is broken down by signal in our reverse-engineering piece and in the risk-arbitrage guide.
None of this means auto-invite is hopeless. It means the goal isn't "fast," it's "consistent and survivable." An engine that respects caps, backs off on PeerFlood, skips privacy-blocked users without retrying, and rotates accounts will quietly outperform a reckless mass-adder over any real time horizon — because its accounts are still alive in week four.
Reckless mass-add vs. limit-aware auto-invite
Two tools can both "auto-invite." What separates them is everything that happens around the invite call. Here's the difference you feel by the second week, not in the demo:
| Behavior | Reckless mass-add | TG:ON limit-aware invite |
|---|---|---|
| Daily cap | Ignored — push until it stops | Respected, per account, per day |
| PeerFlood | Retries in a loop, deepens restriction | Detected, backs off, rotates account |
| Privacy-blocked users | Hammers them, wastes quota | Skipped, no wasted attempts |
| Accounts | One account, blasts everything | Warmed + rotated pool, on proxies |
| Audience source | Random scraped CSV | Vault: 2.9M+ chats and channels |
| Week-4 outcome | Accounts in @SpamBot jail | Accounts alive, steady throughput |
The reckless approach optimizes for a screenshot on day one. The limit-aware approach optimizes for accounts that are still inviting in a month. Because TG:ON ships the source, the warmup, the rotation and the invite engine as one app instead of five, the audience never has to leave the tool — no CSV bouncing between a scraper, an inviter and a proxy manager.
This isn't a Bot API wrapper bolting invites onto a bot. It's a native MTProto client that handles FLOOD_WAIT, PEER_FLOOD and entity caching the way the protocol expects — the reasoning is in "Telegram software: native client, not adapter".
What it costs and how to start
You can start for free. The trial is 3 days or 100 messages, no card required, which is enough to run a real micro-campaign: source 20-30 target chats, warm an account, and run a small, paced invite to see the limits in action for yourself. After that, three plans:
How to start safely. Install for Windows or macOS, connect one account and let it warm up first. Then find 20-30 active chats (not channels) in your niche via the Vault, pull a small member list, and run a slow, default-paced invite into your group. Watch how quickly you hit the daily cap on a single account — that's the lesson that makes the case for rotation. Once you've felt the limits, scale across a warmed pool, not by cranking one account harder.
TG:ON for Windows and macOS
Local-first desktop app. Sessions and keys stay on your machine. 3-day trial, 100 messages, no card.
Download freeSource, warm, rotate, invite —
all in one app.
Trial 3 days / 100 messages, no card. Vault of 2.9M+ chats and channels built in. Questions go to support at @tgon_support_bot.
Start the trialFrequently asked questions
Can a Telegram auto inviter add 10,000 members overnight?
No, and any tool that promises it is setting your accounts up for a ban. Telegram enforces daily invite caps per account, throws PeerFlood ("Too many requests") when you push too fast, and lets users block being added entirely through privacy settings. Realistic auto-invite means a steady trickle per account, per day, across several warmed and rotated accounts. The win is consistent throughput over weeks, not a single overnight dump.
What limits does Telegram put on inviting members?
Three big ones. First, a daily cap on how many users one account can add before Telegram stops it. Second, PeerFlood, a rate limit that triggers when you invite too fast even if you are under the daily cap. Third, user privacy: many people set "who can add me to groups" to contacts only, so they simply cannot be invited and the attempt is wasted. A good auto inviter respects all three instead of brute-forcing through them.
Why do warmup and account rotation matter for auto-invite?
A fresh or freshly bought account that starts mass-inviting on day one looks exactly like a bot and gets flagged by @SpamBot fast. Warmup ramps activity gradually so the account looks lived-in, which lowers but never eliminates the flag risk. Rotation spreads the daily invite quota across many accounts, so a single restriction never kills the whole campaign. TG:ON has both built in.
Where does the audience to invite come from?
From the built-in Vault, a database of 2.9M+ chats and channels searchable by keyword, so you do not need a separate scraper subscription. You source members from relevant chats and groups in your niche, then auto-invite them into your own group under safe limits. Remember you can only add real users from chats and groups, not from broadcast channels.
How much does it cost and is there a free trial?
There is a free trial of 3 days or 100 messages with no credit card. After that: Starter $49/mo, Pro $89/mo, Agency $169/mo. TG:ON runs as a local-first desktop app for Windows and macOS, so your sessions, lead database and LLM keys stay on your own machine. Download from tg-on.com.