This is an improved module for inviting through administrators, which handles all the routine: it assigns and removes admins in chats automatically using pre-created bots. The main difference in version V2 is that all work is done by bots without manual intervention. They receive admin rights, add accounts as administrators, and then mass invite is launched through them. You don’t need to assign rights manually — the system does it for you.
Limits here are also softer than in V1, but there are no universal numbers — you need to test based on your accounts.
Workflows are automated: the system rotates admin slots — assigns, adds, then removes and launches the next flow.
Configuration parameters:
1. Database — upload the list of usernames or links of those you want to invite. If there’s no database — add manually. Usually, the database is taken after audience collection.
2. Group — insert the link to the target group where users will be added. Both public (t.me/name) and private (t.me/joinchat/code) groups are supported. Without this parameter, invite is impossible.
3. Account of the owner or head administrator — specify the account that has full control over the group. The system will use this account to assign rights to others. If the account lacks rights — nothing will work.
4. Select accounts — this sets the list of users from whom invites will be sent. This is important for reducing ban risk: choose the most reliable and active ones.
5. Bot token (gold) — a bot with this token assigns and removes admin rights. The token is obtained through @BotFather and takes a minute to create: just set a name and username, and receive the key. You can automate the process via the «Bot creation» module — the token will be saved in the database.
6. Bot token (silver) — created in the same way, but from another Telegram account. This is needed to spread the load and minimize the risk of blocks. Used for the same tasks as gold.
7. Total users per account — sets the limit on the number of invites one profile can make. It’s recommended to start with small values and gradually increase, monitoring Telegram’s reaction.
8. Delay — regulates the time interval between invites. This helps simulate «real» activity and lowers the chance of getting flagged as spam.
9. Maximum timeout (FloodWait) — sets a timer for waiting in case Telegram applies FloodWait to the account. If the time is exceeded — the account is removed from the task, if not — it waits and continues.
10. Forced number of invited users — the system counts the invite only if the user actually joins the group. Invalid or inaccessible accounts are not considered.
11. Check if user is in the group before inviting — if enabled, the software checks whether the user is already in the group before sending the invite. If yes — it skips and moves on.
12. Leave the main group — after the invite is complete, accounts automatically leave the group to avoid leaving traces and overloading the participant list.
13. Proxy requests to Telegram BotApi — when a proxy is activated and added, the requests sent to the Telegram Bot API are routed through the proxy instead of a direct connection. This can help bypass restrictions and blocks in some cases and improve overall stability.
14. Remove all bots in the group before inviting — when activated, all bots that were among the group’s members or admins will be removed from it to free up unused slots.
Important notes:
– Tokens — to make everything work, you need fresh tokens from @BotFather. It’s recommended to update them regularly before each invite session.
– Admin restrictions — if Telegram says «Administrator restricted», you need to change the main admin account.
– One main admin — the software selects the first admin in the list. It’s better not to assign the group owner for this role.
– Slots — there must be at least 25 free admin slots. Telegram allows up to 50 in total, so keep a buffer, otherwise, no one will be able to send invites.
– Group must be a supergroup — regular groups won’t work.
– Repeat invite — if you restart the task for the same group, delete old admin bots in advance. Otherwise, the system will try to reassign them and cause conflict.
Limits here are also softer than in V1, but there are no universal numbers — you need to test based on your accounts.
Workflows are automated: the system rotates admin slots — assigns, adds, then removes and launches the next flow.
Configuration parameters:
1. Database — upload the list of usernames or links of those you want to invite. If there’s no database — add manually. Usually, the database is taken after audience collection.
2. Group — insert the link to the target group where users will be added. Both public (t.me/name) and private (t.me/joinchat/code) groups are supported. Without this parameter, invite is impossible.
3. Account of the owner or head administrator — specify the account that has full control over the group. The system will use this account to assign rights to others. If the account lacks rights — nothing will work.
4. Select accounts — this sets the list of users from whom invites will be sent. This is important for reducing ban risk: choose the most reliable and active ones.
5. Bot token (gold) — a bot with this token assigns and removes admin rights. The token is obtained through @BotFather and takes a minute to create: just set a name and username, and receive the key. You can automate the process via the «Bot creation» module — the token will be saved in the database.
6. Bot token (silver) — created in the same way, but from another Telegram account. This is needed to spread the load and minimize the risk of blocks. Used for the same tasks as gold.
7. Total users per account — sets the limit on the number of invites one profile can make. It’s recommended to start with small values and gradually increase, monitoring Telegram’s reaction.
8. Delay — regulates the time interval between invites. This helps simulate «real» activity and lowers the chance of getting flagged as spam.
9. Maximum timeout (FloodWait) — sets a timer for waiting in case Telegram applies FloodWait to the account. If the time is exceeded — the account is removed from the task, if not — it waits and continues.
10. Forced number of invited users — the system counts the invite only if the user actually joins the group. Invalid or inaccessible accounts are not considered.
11. Check if user is in the group before inviting — if enabled, the software checks whether the user is already in the group before sending the invite. If yes — it skips and moves on.
12. Leave the main group — after the invite is complete, accounts automatically leave the group to avoid leaving traces and overloading the participant list.
13. Proxy requests to Telegram BotApi — when a proxy is activated and added, the requests sent to the Telegram Bot API are routed through the proxy instead of a direct connection. This can help bypass restrictions and blocks in some cases and improve overall stability.
14. Remove all bots in the group before inviting — when activated, all bots that were among the group’s members or admins will be removed from it to free up unused slots.
Important notes:
– Tokens — to make everything work, you need fresh tokens from @BotFather. It’s recommended to update them regularly before each invite session.
– Admin restrictions — if Telegram says «Administrator restricted», you need to change the main admin account.
– One main admin — the software selects the first admin in the list. It’s better not to assign the group owner for this role.
– Slots — there must be at least 25 free admin slots. Telegram allows up to 50 in total, so keep a buffer, otherwise, no one will be able to send invites.
– Group must be a supergroup — regular groups won’t work.
– Repeat invite — if you restart the task for the same group, delete old admin bots in advance. Otherwise, the system will try to reassign them and cause conflict.
Последнее редактирование: