Prepare the group
In the group settings, let members add people, or make your accounts admins with the right to invite. Better turn join requests off: while they are on, an account only gets in once you approve its request.
Your accounts join your group on their own, check that they are allowed to invite, and add people from a username list or a scraped audience — one at a time, with random pauses and a daily cap you set. For every person you can see how the invite ended.
Free until December 31, 2026 — the inviter and every other feature, no payment and no card
Updated 27 September 2026
From an empty campaign to an outcome for every username — six steps in the Inviter section.
In the group settings, let members add people, or make your accounts admins with the right to invite. Better turn join requests off: while they are on, an account only gets in once you approve its request.
New campaign → a name and "Invite into": a t.me/… link, an @username or an invite link t.me/+…. Accounts are picked as an account group or by hand — only active accounts with a SOCKS5 or HTTP proxy go to work.
A username list (one per line, or separated by spaces or commas; @name, name or t.me/name) or a ready audience from the scraper. Duplicates are skipped, and the import lists every unrecognised line with its number and the reason.
After the start the status is Joining: accounts enter the group spread out rather than all at once — 30 to 120 seconds apart by default. Each one immediately checks whether it may invite; if not, it gets the state No right to invite.
An account sends its first invite 10 to 20 minutes after joining. From then on each account takes the next person from a shared queue: every username goes to one account and is invited once, however many accounts you run. People already in the group are detected before the invite and cost no attempt.
The details page shows counters per outcome (a click on a tile filters the table), accounts with today's invites and the time of the next one, the limits, and the Targets table with CSV export. The page refreshes itself. Pause and Resume work at any moment; Stop is final.
A step-by-step walkthrough of every form field is in the inviter guide. No accounts yet? Start in the Accounts section: upload tdata or .session files (accounts guide) or sign in to an account with a QR code right from the dashboard (QR sign-in guide).
Without these the accounts either cannot join the group or cannot invite.
If no account managed to join, or none of them turned out to have the right to invite, the campaign gets the Failed status. Fix the group settings and press Resume — the accounts join and check their rights again. The Telegram account warmer helps get accounts ready.
You set the pace, and the dashboard makes sure no account goes past it.
Why a high cap is a bad idea. Telegram does not publish how many invites a day are acceptable, and the threshold shifts with an account's age and history. More than 50 invites per account per day means a high risk of PEER_FLOOD and bans; for most accounts 15–20 is sensible. Get speed from the number of accounts instead: ten accounts at 20 invites give you up to 200 invites a day, with none of them running at the limit. The inviter has no overnight window — the pace is set by the cap and the pauses alone.
The result for every username sits in the Targets table, with a status filter and CSV export.
Most refusals come from people's own settings. In Telegram everyone decides who may add them to groups — for example, only their contacts. That is where Privacy restricted and Mutual contact needed come from. It is a platform rule, not a service failure, and no inviter can get around it; one that claims to is simply spending your accounts' attempts.
Refusals are not wasted. Filter the Targets table by Privacy restricted and Mutual contact needed, export the CSV and send those people an invitation with a link to the group by direct message — through a DM campaign. That way each person decides for themselves whether to come in.
Your own list, a scraped audience or top-ups along the way — plus how it links to the scraper.
Paste it into the Username list field: one per line, or separated by spaces or commas, as @name, name or t.me/name. The import shows straight away how many were added, how many were duplicates and which lines were not recognised.
Under "Whom to invite" choose Audience. Members with a username are taken, the rest are skipped. The scraper builds audiences from topical chats and channels: chat members, people who posted in a chat, commenters.
The Add button in Targets puts new usernames at the end of the queue and skips duplicates. A completed campaign with new targets gets back to work on its own; a stopped one cannot be resumed — create a new campaign instead.
Deleted accounts and bots will not be invited, but looking up their usernames still eats into an account's daily allowance. Run the audience through the checker before the campaign so the allowance goes on real people.
The whole chain: proxies → accounts → warm-up → the Telegram scraper on topical chats → checker → inviter → a DM invitation for those who cannot be added. How to collect an audience and clean it is covered in the scraping guide and the audiences and checker guide.
Pauses and caps lower the risk; they do not remove it.
A softer alternative to adding people directly is an invitation link by direct message or a post in a topical chat. Both live in the Campaigns section — see the campaigns and limits guide.
What people ask most often about inviting into Telegram groups.
A tool that adds people to your group from your own accounts. In TGBLAST the accounts first join the group and check whether they are allowed to invite, then take turns inviting people from a username list or a scraped audience — with random pauses and a daily cap on every account. The outcome for each person shows up in the Targets table.
Telegram publishes no exact figure. In TGBLAST you set the daily cap per account: 20 invites by default, anything from 1 to 500, but above 50 the form warns about a high risk of PEER_FLOOD and bans. Overall pace grows with the number of accounts, because the cap applies to each one. Telegram counts refusals too, so an account makes no more than twice its cap in invite attempts per day.
The account is restricted for 24 hours and queued for a SpamBot check, and the person it was inviting goes back into the queue with no penalty for another account to pick up. Once the restriction lifts, the account returns to the campaign on its own. If PEER_FLOOD arrives while the account is still joining, it joins the group later, after the restriction is gone.
These are Telegram's rules, not a malfunction: the person has blocked being added to groups in their privacy settings, allows it only for mutual contacts, is already in the maximum number of groups, or is banned in your group. Each of these outcomes appears in the Targets table with a status and a reason. People marked Privacy restricted and Mutual contact needed can be exported to CSV and invited with a link by direct message.
Yes, if the accounts are admins with the right to invite: an ordinary channel subscriber cannot invite anyone. In a group, members can invite too when the group settings allow it. If the group has join requests switched on, the accounts will not get in until you approve their requests or turn join requests off.
Proxies are required: only active accounts with a SOCKS5 or HTTP proxy go into a campaign. Warm-up is not technically required, but a fresh account with no history that starts inviting straight away runs into restrictions faster. Warmed-up accounts carry a warmed badge in the campaign form.
Upload tdata folders or .session files in the Accounts section, or press Add via QR / phone and scan the QR code in Telegram on a phone where the account is already open. Signing in by phone number is also available, but Telegram often asks for a reCAPTCHA check there that cannot be passed from a server — then the QR code is the way in. If the account has a cloud password, the sign-in window asks for it.
Yes. The cap and the pauses can be changed in the campaign details at any time until it is completed or stopped, and they apply from the next invite. Pause gives you a break and Resume carries on from the same place. Stop ends the campaign for good.
It is not sold separately: the inviter is part of the single plan together with every other tool in the dashboard — 30 USDT for 30 days, paid in USDT on the TRC20 network, with no recurring charges. Until December 31, 2026 every feature is free — no payment and no card.
The inviter, scraper, warm-up, campaigns and conversations — one plan, every tool. Until December 31, 2026 all of it is free: no payment and no card.
The inviter, scraper, warm-up, campaigns and conversations — one plan, every tool. Signing up opens full access for 7 days — no card and no recurring charges.