Where are the databases located, and which databases are used by different modules?

[emiliar]

Where to find databases after completing tasks​

Telegram Expert automatically saves all databases in the additives folder. Depending on which module was used, the structure may differ:

• additives/accounts — the database created each time accounts are scanned for blocks, restrictions, or other technical issues.
  
  
• additives/registrator_generator — the module responsible for automatically generating parameters and data for future account registrations.
  
  
• additives/registrator — stores data on the auto-registration of new accounts, which are launched directly from the panel.
  
  
• additives/registrator_dublicator — used for cloning Telegram sessions, allowing you to quickly create duplicates of existing profiles.
  
  
• invite/ — folders with this name contain databases obtained during inviting, with the method specified at the end — for example, by ID or using admin rights.
  
  
• send/ — all databases with message mailings go into folders with this name, followed by clarification of where the mailing was sent: to channels, groups, or by ID.
  
  
• parsing/ — these folders store databases collected using the parser, and the folder name indicates the source: from comments, chats, etc.
  
  
• db_clean, db_exclude, db_gender, db_union — working with databases.
  
  
• additives/check_phones — the result of mass phone number checking: you can immediately see which ones are active and which are no longer in use.
  
  
• additives/check_links — checking all links to chats and channels: helps determine whether they are accessible and whether they can be used.
  
  
• additives/create_channels — stores information about newly created channels or chats launched through the software.
  
  
• additives/reactions — data on reaction boosts: how many and to which posts they were sent.
  
  
• additives/unsubscribe — a report on mass unsubscribing from channels or chats, created after the process is completed.
  
  
• stat/ — all statistical databases go into the folder with this prefix, and the name indicates the specific purpose — for example, data calculation or generation.
  
  
• additives/subscribe — stores the results of mass subscriptions of accounts to selected chats or channels.
  
  
• additives/subscribe_bot — the database is created after users subscribe to a specific bot.
  
  
• additives/reporter — results of complaints sent about users or chats are saved in this folder.
  
  
• additives/answering_machine — automatic replies sent by the bot on behalf of an account are recorded here.

Each operation is recorded in a separate database that appears directly in the Telegram Expert interface. This is convenient for control, filtering, and analysis of how the tool worked and what exactly was done.

If you are unsure which database you are working with — just open several files in SQLite Studio to view their contents. The format will always be a table, but the columns and names may vary.

When you use Telegram Expert, the program saves databases not only in the interface but also on your computer. If you open the appropriate directory after completing a mailing or invite, you may notice that different types of files are created — they may differ in purpose and structure. Most often, you will encounter two key databases: Base/Parsing and Result/Stat. Each of them carries its own meaning and depends on how exactly you configured the task.

• Base/Parsing — this is a file with the original input data that you uploaded manually: lists of usernames, group or user IDs. If this database is missing, it means a pre-prepared database was used during the process, not a manually entered list.
  
  
• Result/Stat — a database that records how the action was performed: who received the messages or invites, as well as the result for each entry. Depending on the module, the file may be named differently — for example, Invite or Send, but it will all be part of the general Result/Stat category.

Statuses in databases​

Now let’s go through the typical statuses you may see in the Result/Stat database.

Auto-generation of accounts:

• CodeSendInApp — means that Telegram sent the code directly to the app, and if the option to reject such numbers is enabled, the program automatically stops working with this number.
  
  
• Done — registration was successful, the number was accepted, the account was created.
  
  
• PhoneNumberBannedError — the number is already banned in Telegram, and it is not possible to create an account with it; the program immediately excludes it from the process.
  
  
• PhoneCodeInvalidError — the SMS code was incorrect, which caused the registration to fail. The money for the number will still be charged, but some providers may issue a refund — it is worth contacting support.
  
  
• CodeNotSend — the program was unable to send a request for the code, and the exact reason is not determined. Such a number is immediately excluded from the process.
  
  
• CodeNotRecived — the code was not received on the number within the set time limit. This is most often related to poor proxies or a failure on the SMS service side.
  
  
• UnboundLocalError — an error related to unstable proxy operation. The most reliable solution is to replace them.
  
  
• FloodWaitError — Telegram temporarily restricted actions due to repeated use of the same parameters, numbers, or proxies. Settings should be reviewed.
  
  
• PhoneNumberWithTwoFa — the code was received, but the account is already protected by two-factor authentication. This makes registration impossible. Some SMS platforms may issue a refund for such cases.
  
  
• OperationalError — a failure in the network or proxy operation. Check the connection settings and replace the proxy server if necessary.

Invite:

• Done — the user was successfully invited to the specified chat or group.
  
  
• UserPrivacyRestrictedError — the user’s privacy settings do not allow being added to groups manually.
  
  
• UserChannelsTooMuchError — the join limit was exceeded: the user already has too many channels or chats.
  
  
• NotInGroup — the invitation was sent, but after the action, the user did not appear in the chat.
  
  
• BadRequestError — the system could not perform the invite due to incorrect data in the request.
  
  
• NotInvited — the user was not added, most often due to restrictions from Telegram or the user.
  
  
• UserIdInvalidError — ID error: it is impossible to invite the user because the identifier is invalid.
  
  
• UserBannedInChannelError — this person was previously in the chat but was removed or banned, so re-adding is not possible.
  
  
• UserNotMutualContactError — the system cannot add the user because they only allow invites from contacts or the account is restricted.
  
  
• NotFoundInGroup — the user by ID was not found in the original group from which the invite was made.

Mailing:

• Done — the message was delivered to the recipient without errors.
  
  
• ForbiddenError — the recipient has message protection enabled: only premium users or personal contacts are allowed.

General statuses and errors:

• ValueError — incorrect values were provided. Check the module parameters and data validity.
  
  
• TypeError — data type error, occurs when parameters do not match.
  
  
• InviteHashExpiredError — the chat invite link is invalid or expired. A new invite is needed.
  
  
• ScheduleTooMuchError — the limit of scheduled sends has been exceeded: a maximum of 100 can be planned in one chat.
  
  
• ChatAdminRequiredError — the account does not have administrator rights to perform the command.
  
  
• ChatWriteForbiddenError (mailing) — sending is not possible: messages are forbidden in the selected chat.
  
  
• ChatWriteForbiddenError (invite) — if the error occurs for all users, check the chat settings.
  
  
• UserRestrictedError — Telegram restricted the ability to display the user in the chat after being added.
  
  
• ConnectionError — connection problem. Usually related to proxies or the internet.
  
  
• Ready — a row with this status is ready to start the task.
  
  
• Taken — the record is being processed and already in use by the program.
  
  
• ChatWriteForbiddenError (repeat) — for mailings: the chat does not accept messages; for invites — the chat may be closed or have restrictions.

Username and anti-spam errors:

• UseameInvalidError — the username is incorrect or the account does not exist.
  
  
• PeerFloodError — Telegram detected suspicious activity and restricted actions. It is recommended to study anti-spam rules and reduce the load.

After completing tasks for inviting or sending messages in Telegram, the program saves the results in a folder containing ResultStat type databases. These files show how exactly the action went: whether it worked, if there were errors, and which ones. The Reports module allows you to view such results, and to edit the collected databases (for example, after parsing), you can use the built-in tools in the Audience collection section — Clean, Union, and Exclude databases.

How Telegram Expert uses databases in different modules​

Almost every module in Telegram Expert works with databases in one way or another. They are used to store account parameters, collected audiences, phone numbers, task results, and most importantly — to automate processes like registration, invites, and mailings. Below is how exactly this is implemented in each section.

Account actions module​

When you add an account, a parameter database is used — it includes information about the device type, app version, phone model, and other characteristics. This data is pre-generated and provided to the system so that the account is created under the required conditions. Also, after performing different actions with accounts, Telegram Expert automatically creates a final database with information about all steps.

Auto-registration module​

For automatic account registration, Telegram Expert uses a database created via the «Parameter generator.» The same database is used during manual registration — it supplies the needed parameters for each account. If you register accounts through SMS services or the universal registrar, the parameter database is also required — it defines all necessary fields for successful and flexible registration automation.

Audience collection module​

Here, the database is formed during parsing. You set filters — activity in chats, comments, language, etc. — and as a result, you get a database with selected users. There is also a separate Base folder, which stores the sources for parsing — links to groups, channels, usernames. You can reuse it if the collection was interrupted or if you want to update the audience later.

Telegram Expert also allows comparing databases — for example, to exclude the old one from the new one and get only fresh subscribers who appeared recently. Or to remove low-quality accounts (e.g., without a profile photo). If parsing stops, you can simply load the Base database and continue from where it left off.

Invite module​

Here, databases are generated based on the results of invites, recording all task statuses and possible errors. You can also use databases from the «Audience collection» module to invite only those users you selected in advance. If the invite process is interrupted — just load this database into Telegram Expert, and it will continue from the required point.

SMS sending module​

If you are sending messages in comments under posts, you either use a list of channels or a Base database obtained from a previous mailing. This is especially convenient if the sending was interrupted — you can go through the database again by changing the status from «Done» to «Ready.»
For SMS by usernames — you manually upload a list or connect an existing database, for example, from parsing. If you are sending by ID, the database is essential — Telegram Expert must know which group to get users from.

And if you are doing auto-posting, you can again use both lists and databases with groups. For example, if the mailing stops, you simply load a ready database and continue from the stopping point.

Phone numbers module​

For functions like invites or messaging by phone numbers, you can use either number lists or databases generated by the «Number checker.» This tool creates Result or Stat databases, which can then be used to launch operations. You can also use databases from other modules so you don’t have to start everything from scratch.

Boosting module​

A database is required in the «Mass subscriptions» block. You can insert a ready Base database with groups or create it directly inside the tool by specifying a group list. You can also connect databases from the «SMS sending» module — they are useful if you’ve already done auto-posting.

In «Bot referrals» you can also use a Base database to either continue the process or start over — just change the status of the records.

In other sections, databases are not mandatory: you simply enter links to posts or channels. Telegram Expert automatically creates result databases after the operation is completed — whether it's likes, comments, or bot redirects.

Reports module​

Here, final databases with results of previous tasks are processed.

• In the «Report generator» you can load any result database — from invites, mailings, etc. — and get a detailed summary. You can also filter records by status, leaving, for example, only unprocessed users.
• In the «Merge databases» section, you can combine up to five different databases into one — convenient if you’re analyzing multiple tasks, like only invites by ID.
• The «Calculator» allows you to assess the effectiveness of invites or mailings — just upload the required database and view the statistics.

Special modules​

In the «Duplicator» a parameter database for the account may also be needed. But this is only relevant if you did not select the «Use parameters from account» option — in this case, the data is loaded from the database manually.

The software also generates a final database when working with the «Reporter» module.