Provider Console Guide

This page provides a complete guide to using the Provider section of the Namirasoft Telegram Sender Console. It walks you through how to either use the built-in Namirasoft Telegram Bot or register your custom Telegram bot using its token. This configuration enables safe, flexible, and scalable message delivery through the Namirasoft Telegram Sender.

What Is a Telegram Provider?

A Telegram Provider is a connection to a Telegram bot that can send messages using Namirasoft Telegram Sender. Telegram bots are managed via BotFather and are identified by a unique token. You can either use the Namirasoft Telegram bot or connect your custom bot by adding its API token to the console. Once configured, Namirasoft Telegram Sender allows users to manually send messages or it receives messages from Namirasoft Notification Sender to deliver them to the pre-defined Telegram chat.

Why Telegram Integration Matters

Using Telegram bots for automated messaging requires secure integration. Manually managing tokens, chat IDs, and message structures is error-prone. Namirasoft Telegram Sender simplifies this process by centralizing bot token management and controlling all messaging operations with safe, app-level access.

How Namirasoft Telegram Sender Handles Provider Authentication

Namirasoft lets you register each Telegram bot as a unique provider. Tokens are stored securely, and every message sent through the platform is tagged to the appropriate provider. This design ensures transparency, auditability, and easy support for multiple bots.

 

Overview of Provider Fields and Options

The sections below explain each field involved in registering a provider, including Chat and Message Thread ID, API Token, Name, and other fields. Understanding these ensures that the bot is integrated correctly and ready to deliver messages either manually or on behalf of your applications.

• ID (String):This is a unique identifier automatically assigned when a Provider 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 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): The Type field sets which bot delivers your messages. Select NamirasoftBot to send through the ready made @namirasoft_telegram_sender_bot with no setup. Select CustomBot to send through your own bot. You create a custom bot with BotFather and connect it with its API Token. Choose NamirasoftBot if you are not sure.

• API Token (String): The API Token authenticates your own Telegram bot. BotFather gives you this token when you create a bot. Namirasoft uses the token to send messages as your bot. You need it only when Type is CustomBot.
  
  How to create a bot and get its API Token? ▶

  • Open @BotFather in Telegram.
  • If you already have a bot, reuse its token or send /token for a new one.
  • If you need a new bot, send /newbot and follow the prompts.
  • Copy the API Token BotFather returns and paste it in the API Token field.

  See the full guide

• Chat ID (String): The Chat ID identifies the Telegram destination that receives your messages. The destination can be a person, group, supergroup, or channel. A Chat ID is a number. For example, a person uses 123456789 and a group uses -1001234567890. You set a Chat ID when you create a Provider. The Send section treats it as optional.
  
  How to find your Chat ID? ▶

  • Use the Telegram Bot API. It works for all chat types. How to find chat id using api?
  • For groups with Topics enabled, use the Copy Message Link method to read the Chat ID from a message link. How to use the Copy Message Link method?
  • Enter the Chat ID in the Provider form.

• Message Thread ID (String): The Message Thread ID points to a specific topic inside a Telegram group that has Topics enabled. The value is the second number in a topic’s message link. For example, the link t.me/c/1234567890/2/15 gives a thread ID of 2. Every section treats this field as optional.

• 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 2 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.

• 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.

• 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.