call
Go to Console

 

Provider Console Guide

 

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

 

What Is a Slack Provider?

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

 

Why Slack Integration Matters

Manually managing tokens, channel IDs, and message delivery can be error-prone. Namirasoft Slack Sender simplifies this process by centralizing bot token management and controlling all messaging operations with safe, app-level access.

How Namirasoft Slack Sender Handles Provider Authentication

Namirasoft lets you register each Slack bot as a unique provider. Tokens are stored securely, and every message sent through the platform is tagged to the appropriate provider. This 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. 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): This specifies the delivery method type. For Namirasoft Slack Sender, the available option is currently Channel Bot, meaning messages are delivered via a Slack bot integrated into a Slack channel.

 

  • Bot Token (String): This is the authentication token for your Slack bot. It allows Namirasoft Slack Sender to send messages on behalf of your bot. The bot token must be obtained when you create your Slack app. How to Create and Get a Slack Bot Token?

 

  • Channel (String): This is the identifier of the Slack channel where messages will be delivered. Every Provider must be configured with a Channel ID. How to Get a Slack Channel 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 Channel 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 Slack channel.

 

  • 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 Slack, this typically includes values like channel_id and other internal details that determine where messages are delivered.

 

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

        Ready to Get Started or Want to Explore the Console Guide?

        Get Started Now! Explore Console Guide