📘A Complete Guide to Understanding the Namirasoft Notification Sender Console

Guide Overview

This guide is designed to help you navigate and fully utilize the Namirasoft Notification Sender Console. Whether you’re creating Topics, adding Subscribers, reviewing delivery reports, or configuring messaging workflows, this guide provides practical explanations and insights to help you manage notification routing across all supported channels with ease.

Introduction to Namirasoft  Notification Sender

Namirasoft Notification Sender is the communication backbone of the Namirasoft ecosystem, built to enable timely, effective, and reliable delivery of alerts and updates. It manages Topics and Subscribers, receiving notifications triggered by other Namirasoft applications and forwarding them to your configured delivery providers. By routing messages to the right Senders for final delivery, it ensures verified communication across all your connected workflows.

• ID (String): A unique identifier automatically assigned when the topic or subscriber is created. It is used internally by Namirasoft Notification Sender to reference the item in the system. Users cannot modify it.

• User ID (Namirasoft Account’s ID): This is the unique ID of the Namirasoft Account that created the Topic or Subscriber. It links the item to a specific user for access control and tracking but does not affect how notifications are sent or processed.

• Workspace ID (Namirasoft Workspace’s ID): This is the ID of the Namirasoft Workspace to which the Topic or Subscriber belongs. It ensures that the Topic or Subscriber is associated with the correct Workspace, allowing logical grouping within a project or team environment.

• Name (string): This is the user-defined name of the Topic or Subscriber, used for display and identification in the console. It helps users recognize and manage items within their Workspace but does not influence how the system processes notifications.

• Description (string): This is an optional field where users can provide additional details or notes about the Topic or Subscriber. It serves as a reference for human understanding and does not affect system behavior or delivery logic.

• Limit (Yes/ No): It specifies whether the topic has a sending limit applied. When enabled, the system restricts how many notifications can be sent through this Topic within a defined time frame.

• Limit Count (Integer): This shows the maximum number of notifications allowed for the Topic during the active limit period. If the Topic reaches this number, further sends are blocked until the period resets.

• Limit Per Value (Integer): This one defines the numeric length of the limit period. It works in combination with Limit Per Unit to establish the time window in which the send limit applies.

• Limit Per Unit (Enum): It specifies the unit of time (such as seconds, minutes, hours, or days) used for the Topic’s limit period. Together with Limit Per Value, it controls the duration of the send restriction.

• Delay (Yes/ No): It indicates whether a delay is applied before notifications are sent through this Topic. When enabled, the system postpones delivery by a defined amount of time after sending a notification.

• Delay Value (Integer): It specifies the numeric value of the delay period. Used with Delay Unit, it determines how long the system waits before sending each notification.

• Delay Unit (String): It defines the unit of time (such as seconds, minutes, hours, or days) for the delay period. Combined with Delay Value, it sets the total wait time before a notification is delivered.

• Topic ID (String): The unique identifier of the Topic this Subscriber is associated with. It links the Subscriber to the Topic they will receive notifications from.

• Sender ID (String): This is the identifier of the Sender that delivers notifications to this Subscriber. It specifies which Sender (such as Email, SMS, Telegram, Slack, or Teams) will be used for message delivery.

• Sender Type (Enum): It Indicates the type of sender used for this Subscriber. The sender type defines the communication channel (such as Email, SMS, Telegram, Slack, or Teams).

• SMS Sender (Enum): Choose your configured SMS Sender provider from the dropdown list. If you haven’t set one up yet, click the + icon to open the Namirasoft SMS Sender console in a new tab, create a new provider, then return and click the reload (⟳) icon to refresh the list and select your new provider.

• Phone Number (String): When Sender Type is SMS, this is the phone number used to send text messages. It must be in international E.164 format and verified for SMS delivery.

• Email Sender (Enum): Select your configured Email Sender provider from the list. To add a new one, click +, complete the setup in the Namirasoft Email Sender console, then come back and hit the reload (⟳) icon to pick it.

• Email Address (string): When Sender Type is set to Email, this is the email address from which notifications will be sent. It must be a valid, verified address that you own.

• Telegram Sender (Enum): Pick your Telegram Sender provider from the dropdown. If you need another, click + to create it in the Namirasoft Telegram Sender console, return and use the reload (⟳) icon to load the new entry.

• Chat ID (String): When Sender Type is Telegram, this is the unique Telegram chat ID that identifies the destination chat or group where messages will be delivered.

• Message Thread ID (String): Also for Telegram senders, this optional field specifies a particular message thread within a chat. When provided, notifications will appear as replies in that thread rather than as new, standalone messages.

• Slack Sender (Enum): Choose your Slack Sender provider from the dropdown menu. To add a new integration, click +, configure it in Namirasoft Slack Sender console (authorize the Slack app and select a workspace), then click reload (⟳) back in the form to select it.

• Channel (String): Enter the Slack channel ID or name where your Slack Sender provider will post notifications. The channel must exist in the connected Namirasoft Slack Sender console and be accessible by the configured provider.

• Value (String): This is the destination address or identifier for this Subscriber. Its format depends on the sender type (e.g., an email address, phone number, Telegram chat ID, or Slack channel).

• Verified (Yes/ No): This indicates whether the Subscriber’s destination has been successfully verified. Only verified Subscribers can receive notifications. Verification helps ensure message deliverability and security.

• Session ID (String): This is a shared identifier for the send operation, grouping all related Topic-level and Subscriber-level entries under the same dispatch session.

• Title (String): The subject or headline used for the notification messages in this session.

• Message (String): The body content of the notification that was delivered (or attempted) during the session.

• Created At (DateTime): Appears on Topics, Subscribers, and in both Sent Topic and Sent Subscriber reports to show when each configuration or send session began.

• Updated At (DateTime): Shows the date and time when a Topic or Subscriber was last modified.

• Finished At (DateTime): Shows the date and time when a send session completed.