Skip to main content

Subscription Management

NineData's subscription management feature supports custom notification methods based on different subscription types, helping you manage message delivery more conveniently and improve operational efficiency.

Feature Introduction​

  • Subscription types: Subscription types are divided into three categories: SQL tasks, permission requests, and data exports.
  • Process nodes: Each subscription type contains multiple process nodes, such as "to be submitted" and "to be approved" for SQL task types. You can configure the message recipients and notification methods for each process node as needed.
  • Notification methods: Supports five notification methods: internal message, SMS, email, phone, and Webhook. You can choose the appropriate notification method as needed, and different process nodes can select different notification methods to meet different scenarios.
  • Recipients: Supports custom message recipients, and different process nodes can select different recipients.

In the subscription management, each subscription type has default recipients and notification methods (""), and the default content cannot be canceled. You can add new recipients and notification methods based on the default settings.

Prerequisite​

Steps​

  1. Log in to the NineData Console.

  2. Click and then click in the left navigation pane.

  3. On the tab, you can configure the and notification methods for the target .

    Configure Recipients

    1. Click in the column on the right side of the target .

    2. On the page, select below .

    3. Click the text box below , select the recipient, and click .

      tip

      You can also choose Webhook to push messages in the form of group sending according to your needs. If you choose Webhook, you need to configure it in advance. For more information, see Appendix.

    Configure Notification Methods

    Select , , or on the right side of the target subscription type according to business requirements. All recipients under this subscription type will receive messages through the selected notification method.

Appendix: Configuring Webhook​

  1. Log in to the NineData console.

  2. Click on > in the left navigation pane.

  3. Click on the Webhook tab and then click on in the upper right corner of the page.

  4. On the page, configure the settings according to the following table.

    Parameter
    		Description
    Enter a name for the webhook. For ease of future retrieval and management, use a meaningful name with up to 24 characters.
    Enter the webhook address of the group robot. If the webhook address has signature verification enabled, enter the signature key in the box below (leave blank if signature verification is not enabled).
    Refer to the following official documents to obtain the webhook address:
    Enter the signature key corresponding to the webhook address. Leave this field blank if the webhook address does not have signature verification enabled.
    (optional)Binds the webhook to an environment. Only subscription management information related to the bound environment will be sent to this webhook.
    (optional)Binds the webhook to a data source. Only subscription management information related to the bound data source will be sent to this webhook.

  5. Click on , the system will automatically validate the webhook address and signature key (if applicable). If they are invalid, an error message will be displayed and you will need to modify the configuration according to the error message and try again.

    tip

    When creating a Webhook in a third-party tool, it's common practice to enable security settings as needed to ensure the reliability of the message source. These settings may include a signature key, IP whitelist, keywords, etc. Here are a few points to keep in mind:

    • Using a Signature Key as a Security Measure: Due to the variety of subscription message types sent by NineData, it's challenging to set a uniform set of keywords. To prevent missing important messages, we recommend using a signature key as the security measure for your Webhook.
    • Keyword Considerations: If you must use keywords, note that Webhook keywords are case-sensitive. For example, when NineData sends a welcome message containing the keyword "NineData," if you use "ninedata" instead in your keyword selection, you won't successfully receive the message. If you're configuring the Webhook in the NineData console, you'll also receive errors like "Keyword not found."
Last updated on