call
Go to Console

 

 

Subscriber Console Guide

 

This page provides a complete guide to using the Subscriber section of the Namirasoft Notification Sender Console. It walks you through how to create and manage Subscribers, which are responsible for routing messages from Topics to their final destinations through provided channels.

What Is a Subscriber?

A Subscriber defines how and where messages from a Topic are delivered. When a Topic receives a message, all of its associated Subscribers are triggered, and each delivers the message to a specific channel and recipient. Subscribers are configured with a delivery method, including email addresses, phone numbers, Telegram chat IDs, etc., depending on the selected channel.

Why Subscribers Matter

Subscribers give you full control over the final delivery of your messages. You can direct system alerts, billing updates, or incident notifications to the right audience by defining Subscribers that suit your team’s needs.

How Namirasoft Notification Sender Uses Subscribers

When a message is sent to a Topic, Namirasoft Notification Sender locates all associated Subscribers. It then uses the configuration in each Subscriber to deliver the message using the defined channel and destinations. Each Subscriber is independently processed, so even if one delivery fails, others can succeed. This parallel, decoupled model ensures reliability and resilience in message delivery.

Overview of Subscriber Fields and Options

This section explains each field and setting available when creating or managing a Subscriber in the console. It helps you understand how Subscribers are configured, how they link to Topics, and how delivery channels are defined for effective message routing.

 

  • ID (String): A unique identifier automatically assigned when the 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 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 Subscriber belongs. It ensures that the Subscriber is associated with the correct Workspace, allowing logical grouping within a project or team environment.

 

  • Topic (String): This is the name of the Topic this Subscriber is associated with, as chosen by the user. It links the Subscriber to the Topic they will receive notifications from. In the Subscriber List view, clicking the Topic ID redirects you to that Topic’s details page.

 

  • Subscriber ID (String): This is the unique internal identifier for the Subscriber entity, automatically generated by the system. it is used for referencing and logging purposes.

 

  • Subscriber Type (Enum): This indicates the type of delivery method used by the Subscriber, such as SMS, Email, Telegram, Slack, or Microsoft Teams.

 

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

 

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

 

  • Name (string): This is the user-defined name of the 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 Subscriber. It serves as a reference for human understanding and does not affect system behavior or delivery logic.

 

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

 

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

 

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

 

  • Message (String): The full content of the message sent to the Subscriber. This includes any text or payload that was received from the Topic and passed to the delivery provider.

 

  • Message ID (String): This is the unique identifier of the message that was routed to this Subscriber. This links the delivery record back to the original message sent by a Namirasoft app.

 

  • Successful (Enum): This shows whether the message was successfully delivered to the specified destination or failed.

 

  • Result (String): This is the status response or message returned by the delivery provider which is used to track and debug message delivery outcomes.

 

  • 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 Subscriber was last modified.

 

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

Ready to Start or Want to Explore the Console Guide?

Get Started Now Explore Console Guide