📘A Complete Guide to Understanding the Namirasoft Telegram Sender Console

Guide Overview

This guide helps you understand and use the Namirasoft Telegram Sender Console to its full potential. From creating Telegram message providers to sending messages and analyzing delivery reports, this documentation breaks down each part of the console with practical definitions and usage insights.

Introduction to Namirasoft  Telegram Sender

Namirasoft Telegram Sender lets you integrate Telegram into your communication workflows by creating “providers” that define how and where your messages will be sent. Whether you use the built-in Namirasoft bot or connect your own, the platform allows direct delivery of messages to Telegram users, groups, or channels using their Chat ID and optional Message Thread ID.

• ID (String):This is a unique identifier automatically assigned when an item such as a Provider or a message Report is created. It is used internally by the system for referencing and cannot be changed by users.

• User ID (Namirasoft Account’s ID): This is the unique ID of the Namirasoft Account that owns the item. It links the Provider, message Report, or any related entity to a specific user for tracking and access control.

• Workspace ID (Namirasoft Workspace’s ID): This is the identifier of the Namirasoft Workspace where the item resides. It ensures that each entity is correctly associated with its project or team environment.

• Type (Enum): This is the selected type of Telegram bot used to send messages. It determines whether the built-in Namirasoft Telegram Bot or a custom user bot is used for delivery.

• API Token (String): This is the Telegram bot API token required only when using a custom bot. It allows the system to authenticate and send messages on behalf of the user’s bot.

• Chat ID (String): This is the identifier of the destination Telegram chat or channel where messages will be delivered. A Chat ID is required when creating a Provider, but optional in other areas like the Send section or automated alert features. Users can refer to the How It Works page to learn how to obtain a Chat ID.

• Message Thread ID (String): This is the identifier of a specific topic inside a Telegram group that has topics enabled. It is optional in all sections, including Provider creation and Send. Users can refer to the How It Works page to learn how to obtain a Message Thread ID.

• Verified (Yes/No): This indicates whether the Provider has been successfully verified. After creating a Provider, a verification code will be sent to the specified Chat ID. Users must enter that code in the console to complete verification. Messages cannot be sent through an unverified Provider.

• Name (string): This is the user-defined name for the Provider, used for display and identification. It helps identify and manage resources more easily but does not affect system behavior.

• Description (String): This is an optional field where users can enter notes or comments about the Provider or message configuration. It is used for internal clarity and does not affect delivery.

• Limit (Yes/ No): This indicates whether a rate limit is active for the Provider. If enabled, it restricts how frequently messages can be sent.

• Limit Count (Integer): This defines the number of messages that can be sent within a defined time window when rate limiting is enabled.

• Limit per Value (Integer): This is the numeric part of the rate limit duration. It works together with Limit Per Unit to define the time window for message sending. For example, a value of 1 combined with a unit of hour would mean the limit applies per one hour.

• Limit per Unit (Enum): This defines the unit of time used in combination with Limit Per Value to determine the message rate limit window. The available options are second, minute, hour, and day.

• Delay (Yes/ No): This specifies whether a delay should be applied before sending a message. When enabled, the system waits based on the defined delay value and unit before dispatching the message to the Telegram chat.

• Delay Value (Integer): This is the numeric duration to wait before sending a message. It works with the Delay Unit to determine the total delay time.

• Delay Unit (Enum): This is the unit of time used in combination with Delay Value to calculate the total delay before message delivery. Supported units include milliseconds, seconds, and minutes.

• Message (String): This displays the full text of the message that was sent to the Telegram destination. It allows users to review exactly what content was delivered.

• Meta (JSON): This object contains technical metadata about the destination. For Telegram, it typically includes fields like chat_id and message_thread_id, which are used to identify where the message is sent.

• Successful (Enum): This indicates whether the message was successfully delivered. If sending fails due to verification or technical issues, the status is shown as Failed.

• Result (String): This shows the result of a message-sending operation. A successful attempt will return a message like Successful. If sending fails, it may return detailed error strings.

• Session ID (String): This is the identifier for the sending session. It groups related report entries under the same execution or sending attempt.

• Provider ID (String): This is the unique identifier of the Telegram provider used for sending the message. It links the report entry to the provider configuration in the system.

• Created At (DateTime): This is the date and time when the item, such as a Provider or a message Report, was first created in the system.

• Updated At (DateTime): This is the date and time when the item was last modified. It helps track changes to configuration or settings.

• Sent At (DateTime): This is the exact timestamp when the message was sent to Telegram. It is used for logs and delivery time analysis.