All Products
Search

This Product

    Data Management:Use DingTalk, DingTalk Enterprise, Feishu, and Lark to send notification messages

    Document Center

    Data Management:Use DingTalk, DingTalk Enterprise, Feishu, and Lark to send notification messages

    Last Updated:Nov 13, 2025

    DMS integrates with DingTalk, DingTalk Enterprise, and Feishu to serve as notification channels. You can view notifications on mobile devices and clients. Approvers can also approve tickets on their mobile devices.

    Prerequisites

    You have created an organization in DingTalk or Feishu.

    Note

    This organization is an internal enterprise organization. It is not a public Alibaba Cloud organization, such as Alibaba Cloud Service Support.

    Precautions

    • Ticket approval is supported only on mobile devices.

    • If you are an Alibaba Group internal user, contact DMS technical support (DingTalk group number: 87370028482).

    • The US site does not support message notifications.

    Preparations

    1. Configure an application to receive messages.

      DingTalk/DingTalk Enterprise

      1. Create an application.

        1. Log on to and join a DingTalk organization.

          1. Log on to the DingTalk Open Platform.

          2. Select your enterprise's organization. For example, "XXX Test Organization".

        2. Go to the DingTalk console to create a DingTalk application.

          1. In the top-right corner of the page, click My Console.

          2. Click the Application Development tab. In the left navigation pane, choose Internal Enterprise Application > DingTalk Application.

          3. Click Create Application.

          4. Enter an Application Name and Application Description, and click Save.

        3. Configure a DingTalk robot to receive messages.

          1. Click the name of the application that you created to go to the application editing page.

          2. In the navigation pane on the left, choose Application Capabilities > Add Application Capability, and then add a robot.

          3. Configure the Robot Introduction, Robot Description, and Message Reception Mode, and then click Publish.

            Note

            Set Message Reception Mode to HTTP mode.

        4. Configure web application information.

          1. After you add the web application, in the Application Capabilities menu, click Web Application.

          2. Set the homepage URL for the application and click Save.

            The homepage URL depends on the current DMS data processing region. For example, if the data processing region is Singapore, the application homepage URL is https://dms-ap-southeast-1.alibabacloud.com.

            Note

            To view the data processing region, see Switch DMS deployment regions.

            image

            • China (Hangzhou): https://dms-cn-hangzhou.alibabacloud.com.

            • Japan (Tokyo): https://dms-ap-northeast-1.alibabacloud.com.

            • Singapore: https://dms-ap-southeast-1.alibabacloud.com.

            • Malaysia (Kuala Lumpur): https://dms-ap-southeast-3.alibabacloud.com.

            • Indonesia (Jakarta): https://dms-ap-southeast-5.alibabacloud.com.

            • SAU (Riyadh - Partner Region): https://dms-me-central-1.alibabacloud.com.

            • China (Hong Kong): <a href="https://dms-cn-hongkong.alibabacloud.com" id="0c5ce72573cfn" uuid="ba897e6a-66d7-4d24-b1cd-c1cc256337fc">https://dms-cn-hongkong.alibabacloud.com</a>.

            • South Korea (Seoul): <a href="https://dms-ap-northeast-2.alibabacloud.com" id="95873e62e290c" uuid="3ed56fc3-194d-4618-b7eb-70ae2871deeb">https://dms-ap-northeast-2.alibabacloud.com</a>.

        5. Configure permissions.

          In the left navigation pane, choose Development Configuration > Permission Management, and then request the following permissions:

          • Basic permissions required to call Simple Notification Service (SNS) APIs

          • Read permission for member information

          • Permission to retrieve basic member information based on mobile phone numbers

          • Basic permission to call enterprise APIs

          • Basic permission to retrieve user access credentials for DingTalk open interfaces

          • Permission to manage basic information of DingTalk groups

          • Permission for internal enterprise robots to send messages

          • Write permission for interactive card instances

        6. Create and publish a new version.

          You must publish a version of the custom enterprise application before other users in the enterprise can use it.

          In the navigation pane on the left, choose Version Management and Publishing. Click Create New Version, enter the configuration information, and click Save.

      2. Create a card.

        1. Create a template.

          1. Go to the Card Platform and click Create Template.

          2. Enter a Template Name, select a Card Type and Card Template Scenario, and then click Create.

            For Card Template Scenario, select Normal Card. For Associated Application, select the application that you created.

        2. Import a card template.

          Choose More > Import Template. Import and save the message notification card template. For a sample template, see DingTalkTemplate.json.

        3. Publish the message notification card template.

      Feishu/Lark (International)

      1. Log on to the Feishu Open Platform or Lark Open Platform and go to the developer console.

        1. Go to the Feishu Open Platform or Lark Open Platform.

        2. You can click Log On.

          The logon account must belong to the target enterprise organization. For example, the organization name is "XXX Test Organization".

        3. Log on and go to the Developer Console.

      2. Click Create Custom Enterprise Application. Configure parameters such as Name and Application Description, and then click Create. For more information, see Development process for custom enterprise applications.

      3. Add a Feishu robot.

        1. (Optional) Click the application name to go to the application editing page.

          Note

          If you just created the application, you can skip this step.

        2. In the left navigation pane, choose App Features > Add App Feature.

        3. On the Add By Feature tab, in the Robot card, click Add.

        4. On the Robot page, you can enter a robot name and click Save.

      4. Add a web application.

        1. In the left navigation pane, choose App Features > Add App Feature.

        2. On the Add By Feature tab, in the Web App card, click Add.

        3. On the Web App page, enter the URL for the Mobile Homepage and click Save.

          The homepage URL depends on the current DMS data processing region. For example, if the data processing region is Singapore, the application homepage URL is https://dms-ap-southeast-1.alibabacloud.com.

          Note

          To view the data processing region, see Switch DMS deployment regions.

          image

          • China (Hangzhou): https://dms-cn-hangzhou.alibabacloud.com.

          • Japan (Tokyo): https://dms-ap-northeast-1.alibabacloud.com.

          • Singapore: https://dms-ap-southeast-1.alibabacloud.com.

          • Malaysia (Kuala Lumpur): https://dms-ap-southeast-3.alibabacloud.com.

          • Indonesia (Jakarta): https://dms-ap-southeast-5.alibabacloud.com.

          • SAU (Riyadh - Partner Region): https://dms-me-central-1.alibabacloud.com.

      5. Add a redirection URL and a trusted H5 domain name.

        1. In the left navigation pane, choose Development Configuration > Security Settings.

        2. On the Redirect URLs tab, you can configure the Redirect URL and Trusted H5 Domain Name.

          The redirection URL and trusted H5 domain name depend on the DMS data processing region. For example, if the DMS data processing region is Singapore, the redirection URL is https://dms-ap-southeast-1.alibabacloud.com/console/mobile/index/ and the trusted H5 domain name is https://dms-ap-southeast-1.alibabacloud.com.

        3. Click Add for each entry.

      6. Configure application permissions.

        1. In the navigation pane on the left, choose Development Configuration > Permission Management.

        2. On the Permission Management tab, click Enable Permissions.

        3. On the App Identity Permission (tenant_access_token) tab, request the following permissions. For more information about requesting permissions and their descriptions, see Request Permissions and Permission Description.

          • Retrieve user ID

          • Retrieve user ID by mobile number or email

          • Upload images and attachments to cloud documents

            Note

            Lark does not support this permission.

          • Retrieve and send private and group messages

          • Send messages as the application

          • Send messages to multiple users in batches

          • Retrieve and upload image or file resources

      7. Publish an application version.

        You must publish a version of the custom enterprise application before other users in the enterprise can use it.

        1. In the left navigation pane, choose App Release > Version Management & Publishing.

        2. Click Create Version.

        3. Enter the App Version, select the Default Mobile Capability, configure other settings, and click Save.

          Set the Availability to All Members.

    2. Retrieve key information from DingTalk, DingTalk Enterprise, or Feishu. This information is used to configure notification channels in DMS.

      DingTalk

      • Retrieve the AppId, AgentId, AppKey, and AppSecret

        You can obtain the AppId, AgentId, AppKey, and AppSecret for the application from the Credentials and Basic Information page on the DingTalk Open Platform.

      • Retrieve the RobotCode

        On the DingTalk developer platform, you can obtain the RobotCode from the Application Capabilities > Robot page.

      • Retrieve the card template ID

        You can obtain the ID from the Template Management > Template List page of the Card Platform.

      • Retrieve the CorpId (Optional)

        Go to the DingTalk developer console and click your profile picture to retrieve the CorpId.

        Note

        After you configure the CorpId parameter in the DMS notification channel, you can receive messages and approve tickets without switching your DingTalk organization to the one where the custom enterprise application is located.

      DingTalk Enterprise

      • Retrieve the AppKey and AppSecret

        Obtain the application's AppKey and AppSecret from the Basic Information page of the DingTalk Open Platform.

      • Retrieve the RobotCode

        On the Robot page of the DingTalk Open Platform, you can obtain the RobotCode from the credential information.

      • Retrieve the card template ID

        You can obtain the ID on the Development Tools > Card Builder page of the Card Platform.

      • Retrieve the CorpId (Optional)

        Go to the DingTalk developer console and click your profile picture to retrieve the CorpId.

        Note

        After you configure the CorpId parameter in the DMS notification channel, you can receive messages and approve tickets without switching your DingTalk organization to the one where the custom enterprise application is located.

      Feishu/Lark

      You can obtain the AppId and AppSecret on the Basic Information > Credentials and Basic Information page of the Feishu Open Platform or Lark Open Platform.

    Step 1: Enable and configure notification channels in DMS

    The channel management feature in DMS lets you enable or disable tenant-level notification channels and maintain configuration information for applications such as Feishu and DingTalk Enterprise.

    Note

    After you enable a target channel, the notification settings that you configure in DMS take effect. DMS then sends you notifications through that channel.

    Only administrators or DBAs can configure notification channels.

    1. Log on to the DMS console V5.0.

    2. Click the 2023-01-28_15-57-17.png icon in the upper-left corner of the console and choose All Features > Operations Management > Notification Management.

      Note

      If you are using the console in normal mode, choose Operations Management > Notification Management from the top menu bar.

    3. In the upper-left corner of the page, click Channel Management.

    4. Select the target notification channel.

    5. Configure the required information for Feishu, Lark, DingTalk, or DingTalk Enterprise.

      The following example shows how to configure channel information for Feishu. The procedure for other channels is similar.

      1. In the Feishu channel section, click Edit.

      2. Enter the AppId and AppSecret, and then click Save.

    Step 2: Set users to receive message notifications

    The following example shows how to configure notifications for data export tickets that are pending approval:

    1. The administrator adds the users who will receive messages to DMS. For more information, see User Management.

    2. The administrator or DBA navigates to the DMS Notification Management page.

      On the Notification Management page, select the DMS feature module for which you want to update message notifications.

    3. In the Module/Business Type filter box, select Ticket > Data Exporting.

    4. Find the ticket with the Pending Approval business status and click Modify in the column on the right.

    5. In the Additional Notification Users section, select the desired users and click OK.

    6. Enable message notifications.

      Notifications for subsequent data export tickets that are pending approval will be sent directly to the specified users through DingTalk, DingTalk Enterprise, or Feishu.

    References

    DMS lets you quickly process tickets on mobile devices to greatly improve development efficiency. For more information, see Approve tickets on a mobile device.

    FAQ

    • Q: I configured channel information for Feishu, DingTalk, DingTalk Enterprise, or Lark in my personal notification settings. Why am I not receiving DMS message notifications through Feishu, DingTalk, or other channels?

      A: Check whether you have enabled the Feishu, DingTalk, DingTalk Enterprise, or Lark notification channel. The information that you configure takes effect only after you enable the corresponding channel. DMS can then send you message notifications through that channel. For more information about how to enable a channel, see Step 1: Enable and configure notification channels in DMS.

    • Q: Why do I not receive DingTalk or Feishu messages even after I configured the notification channel information and specified the users to receive messages?

      A: Follow these steps to resolve the issue:

      1. You can verify whether the administrator or DBA has enabled the corresponding channel in DMS by choosing Notification Management > Channel Management. For more information, see Step 1: Enable and configure notification channels in DMS.

      2. Click your DMS profile picture and make sure that the corresponding notification channel is enabled in the notification methods.

    • Q: I did not change my notification settings, but I suddenly stopped receiving DingTalk or Feishu messages. What could be the reason?

      A: The number of API calls for your custom enterprise application may have exceeded the limit, which prevents you from receiving messages. You can view the API call volume in the developer console of DingTalk or Feishu. For more information about how to adjust the number of API calls, see the documentation for DingTalk and Feishu.