Skip to main content
Plan requirement: IM integration requires an On-call Pro or higher subscription. Learn more
This documentation uses the new version of Dingtalk Open Platform as an example.

AI SRE Required Permissions

The following list includes all permissions required when the Dingtalk IM integration uses AI SRE, including basic notifications, War Room, AI SRE conversations, and AI-generated post-mortem reports. In the Dingtalk Open Platform Permission Management page, request each official permission name below.
Official permission namePurpose
qyapi_chat_manageGet group chat information for standard notifications, Cool Apps, and bot message delivery
qyapi_robot_sendmsgSend bot messages for basic notifications, session-webhook bot replies, standard interactive cards, War Room messages, and downloading files received by the bot
qyapi_chat_readRead group chat information for War Room group status checks and member handling
qyapi_chat_base_readRead basic group chat information for War Room group queries
qyapi_get_member_by_mobileGet Dingtalk user IDs by phone number for one-click user linking and inviting members to War Rooms
Card.Instance.WriteCreate and deliver AI SRE streaming cards; required only when a Dingtalk AI streaming card template is enabled
Card.Streaming.WriteUpdate AI SRE streaming card content; required only when a Dingtalk AI streaming card template is enabled
If no Dingtalk AI streaming card template is configured, AI SRE falls back to standard interactive cards or session-webhook bot replies. Keep qyapi_robot_sendmsg granted in that mode.

1. Create Dingtalk App and Add Dingtalk Integration

1. Create Custom App

Visit Dingtalk Developer Console → App Development → Enterprise Internal Development, create an app. See Dingtalk development documentation Create Enterprise Internal App - H5 Mini App. 2025-09-18-15-02-55 You can use the Flashduty official icon as the app icon.

2. Copy Enterprise CorpId

Click the enterprise avatar in the top right corner, copy CorpId from the dropdown menu. 2025-09-18-15-03-12 Return to Flashduty On-call integration configuration page, fill in the corresponding CorpId in the form.

3. Copy App Credential Information

Enter the created app details page, navigate to App Capabilities → Credentials & Basic Info via the left menu, copy AgentId, Client ID, and Client Secret. 2025-09-18-15-04-39 Return to Flashduty On-call integration configuration page, fill in the corresponding AgentId, Client ID, and Client Secret in the form.

4. Copy Event Subscription Information

Go to Development Configuration → Events & Callbacks page. Set push method to HTTP Push, then click the button to generate Encryption aes_key and Signature Token, and copy and save them. 2025-09-18-15-05-10 Return to Flashduty On-call integration configuration page, fill in the corresponding Encryption aes_key and Signature Token, click Save.

5. Configure Event Subscription

Go to Development Configuration → Event Subscription page. Configure Event Subscription Request URL using the Event Subscription Request URL from Flashduty integration details. Click Save after configuration. 2025-09-18-15-05-34 Below the Save button, select these three group chat events: Group chat name changed, Cool app installed in group, and Cool app uninstalled from group, then click Save. 2025-09-18-15-08-07

6. Add App Capabilities

Create a Cool App. Go to Development Configuration → Add App Capabilities → Cool Apps → Cool Apps List page, click Create Cool App, select Extend to Group Chat. Enter the Edit Cool App page and complete the following steps:
  1. Fill in basic information. You can use the Flashduty official icon as the icon.
2025-09-18-15-11-03
  1. Configure feature design. Select Group Shortcut Entry and Message Card on the left. You can use the Flashduty official icon for the group shortcut icon; copy the Cool App Web URL from integration details for desktop and mobile access URLs.
2025-09-18-15-13-08
  1. Skip step three (Feature Development), proceed to step four Preview & Publish, click Publish and confirm.

7. Configure Bot and Message Push

Go to App Capabilities → Bot page, enable bot configuration, fill in name and upload icon, then click Save. You can use the Flashduty official icon as the icon. 2025-09-18-15-17-17

8. Configure App URLs

Go to App Capabilities → Web App page. Configure App Homepage URL and PC Homepage URL using the App Homepage URL and PC Homepage URL from Flashduty integration details. Click Save when done. 2025-09-18-15-20-13

9. Request App Permissions

Go to Development Configuration → Permission Management page, request the following permissions for the group app created in previous steps:
  • qyapi_chat_manage: Get group chat information
  • qyapi_robot_sendmsg: Send messages to group chats or individuals
If you need AI SRE, also confirm that all AI SRE required permissions listed at the beginning of this page have been requested. 2025-09-18-15-20-36
If you need to continue configuring War Room, publish the custom app once first. After the app is published, you can select it from the Available Apps list in Scene Groups. See App Publishing and Usage for the publishing path.

2. Configure War Room

If you don’t need War Room functionality, skip this step and proceed directly to App Publishing and Usage.
Before configuring War Room, confirm that the app has been granted the AI SRE required permissions listed at the beginning of this page.

1. Request App Permissions

Go to Development Configuration → Permission Management page, request the following permissions for the group app created in previous steps:
  • qyapi_chat_read: Get group chat information
  • qyapi_chat_base_read: Get group chat information
  • qyapi_get_member_by_mobile: Allow the current app to get Dingtalk users by phone number for inviting users to join group chats
2025-09-18-15-21-28

2. Configure Group Template

Navigate to Open Capabilities → Scene Groups via the Dingtalk Open Platform top menu bar.
  1. Configure Group Bot. Select Bot in the left menu, then click Create Group Bot.
The Group Bot configured in this step and the App Bot are two different concepts. Group bots are used to automatically create group bots when generating group chats. Group bots and app bots have different Bot IDs. To enable War Room for Dingtalk, you must additionally configure a Group Bot.
Fill in the group bot configuration. If you need AISRE, configure Message Callback URL, Message Callback Token, and Source Website as shown below. These fields are used for AISRE Dingtalk message callbacks.
Dingtalk’s current certificate validation for message callback URLs is not compatible with the ACME-issued certificate used by api.flashcat.cloud. To ensure Dingtalk can validate the callback URL and deliver messages correctly, replace the domain in the message URL provided by the Flashduty integration configuration page with dingtalk-message.flashcat.cloud.
Example Configuration:
ItemValue
Bot NameFlashduty
Bot AvatarFlashduty official icon
DescriptionFlashduty
Message Preview ImageFlashduty official icon
Detailed DescriptionFlashduty message push bot.
Message Callback URLUse the message URL provided on the Flashduty integration configuration page, and replace api.flashcat.cloud with dingtalk-message.flashcat.cloud
Message Callback TokenUse the Signature Token generated in step 4 under Development Configuration → Events & Callbacks
Source Websitehttps://www.flashduty.com
After configuration, click Create, then click Approve. After “Submission successful” appears in the top right corner, Dingtalk has automatically approved the group bot. 2025-09-18-15-22-05
  1. Configure Group Template. Select Group Template in the left menu, click Create Group Template. Set Enterprise Type to Internal, and set Available Apps to the published custom app created in previous steps. Then fill in template information in the next step. Template Name, Icon, Description, Text Introduction, Template Description, Image Introduction and other descriptive information won’t affect group template functionality—you can configure any values that meet requirements. Example Configuration:
    ItemValue
    Template NameFlashduty War Room
    IconFlashduty official icon
    DescriptionOne-click war room creation for active incidents.
    Text IntroductionOne-click war room creation for active incidents.
    Template DescriptionOne-click war room creation for active incidents.
    Image IntroductionFlashduty official icon
    In Select Bot configuration, click Select Created Bot, select the group bot created in the previous step. Keep other configurations as default. Finally click Save Edit. 2025-09-18-15-22-35 2025-09-18-15-23-06 In the Fill in Gray Group step, click Create Gray Group, then click Publish Gray. Finally, click Group Template in the left menu again, then click to enter the group template just created. Click Submit for Review, after Dingtalk automatically approves, finally click Publish.
  2. On the published group template details page, copy Template ID and Bot ID. 2025-09-18-15-23-46 Return to Flashduty On-call integration configuration page, fill in the corresponding Template ID and Bot ID, click Save.
Only one IM integration can have War Room enabled at a time. If you’ve already enabled War Room in another IM integration (such as Feishu/Lark, Slack, or WeCom), you need to disable it there first before enabling it in the current Dingtalk integration.

3. App Publishing and Usage

After completing the above steps, confirm that the custom app has been published with the latest version. If it has not been published yet, or if you changed app settings after publishing, go to App Publishing → Version Management & Publishing, create a new version, and publish it.
To ensure everyone can use the app, adjust the app Visibility to all employees before publishing.
2025-09-18-16-08-17 After publishing, you can access the app via Mobile or Desktop. First access requires login to link Dingtalk and Flashduty accounts; subsequent access will be passwordless.
Dingtalk → Workspace → Search app name → Open App

4. Linked Users

In the Linked Users tab of the integration detail page, you can view the linking status between team members and Dingtalk accounts, and quickly complete batch linking.

View Linking Status

The linked users list shows all team members and their linking status. You can filter by:
FilterDescription
AllView all team members
LinkedView only members who have linked their Dingtalk accounts
UnlinkedView only members who have not yet linked their Dingtalk accounts
Search by name or email is supported.

One-Click Linking

When unlinked members exist, click the One-Click Link button. The system will attempt to obtain Dingtalk account IDs via phone numbers and automatically link them, equivalent to members logging into Flashduty using the same phone number on Dingtalk.
The system can only push Dingtalk message notifications after members complete linking. If linking fails, verify that the member’s phone number matches their Dingtalk account.

5. FAQ

Go to Dingtalk → Workspace → Search app name → Open App, complete one login to link Dingtalk and Flashduty accounts so the system can obtain user identity for message delivery.
  • Go to Dingtalk → Workspace → Search app name → Open App, complete one login to link Dingtalk and Flashduty accounts. If already logged in, try clicking the top-right menu, switch accounts, and re-login to link the account
  • Ensure you’ve purchased sufficient Licenses. View License usage in Console → Billing Center
  1. Go to Dingtalk, install the Cool App in the target group chat, otherwise the group chat list cannot be obtained
2025-09-18-15-34-372025-09-18-15-35-44
  1. Return to escalation rule configuration page, refresh and reselect the group chat list
  2. If still unable to get the group chat list, try uninstalling the Cool App from the group and retry the above steps. If the issue persists, contact customer or dedicated technical support
Dingtalk VersionTotal Calls/MonthQPSRefresh Time
Standard10,000201st of each month
Professional500,000401st of each month
Dedicated5,500,000601st of each month
After exceeding API call limits, Dingtalk app cannot deliver messages properly. Use notification channels reasonably. See Dingtalk official documentation.