Dingtalk Integration

This document uses the new version of the Dingtalk Open Platform as an example.

I. Create Dingtalk Application and Add Dingtalk Integration#

1. Create a Custom Application#

2. Copy the Enterprise CorpId#

3. Copy Application Credential Information#

4. Copy Event Subscription Information#

5. Configure Event Subscription#

6. Add Application Capabilities#

7. Configure Bot and Message Push#

8. Configure Application URLs#

9. Apply for Application Permissions#

II. Configure War Room#

If you do not need to configure the War Room feature, you can skip this step and proceed directly to Application Release and Usage.

1. Apply for Application Permissions#

2. Configure Group Template#

1.

Configure Group Bot. Select Bot from the left menu bar, then click Create group bot.

The Group Bot configured in this step and the Application Bot are two different concepts. The group bot is used to automatically create a group bot when a group chat is generated. The group bot and the application bot have different Bot IDs. To enable the War Room feature for Dingtalk, you must configure an additional Group Bot.

Fill in the group bot configuration. The Message Callback URL, Message Callback Token, and Information Source Website configurations have no practical effect in Flashduty's application scenario; you can configure them with any values that meet the requirements.

Example Configuration:

Configuration Item	Value
Bot Name	Flashduty
Bot Avatar	Flashduty official icon
Introduction	Flashduty
Message Preview Image	Flashduty official icon
Detailed Description	Flashduty message push bot.
Message Callback URL	https://flashcat.cloud/
Message Callback Token	token
Information Source Website	https://flashcat.cloud/

After completing the configuration, click Create, then click Approve. After the "Submission successful" pop-up appears in the top right corner, Dingtalk has automatically completed the approval of the group bot.

2.

Configure Group Template. Select Group Template from the left menu bar, and click Create group template.

Set the Enterprise Type to Internal Enterprise and the Optional Application to the custom application created in the previous steps. Then, fill in the template information in the next step.

Introductory information such as Template Name, Icon, Description, Copywriting Introduction, Template Description, and Image Introduction will not affect the use of the group template feature; you can configure them with any values that meet the requirements.

Example Configuration:

Configuration Item	Value
Template Name	Flashduty War Room
Icon	Flashduty official icon
Description	Create a war room for active incidents with one click.
Copywriting Introduction	Create a war room for active incidents with one click.
Template Description	Create a war room for active incidents with one click.
Image Introduction	Flashduty official icon

In the Select Bot configuration item, click Select created bot and choose the group bot created in the previous step. Keep other configuration items at their default settings. Finally, click Save Edit.

In the Fill in grayscale group step, click Create grayscale group, then click Publish grayscale.

Finally, click Group Template in the left menu bar again, then click to enter the group template you just created. Click Submit for Review, and after Dingtalk automatically approves it, finally click Publish.

3.

In the published group template details page, copy the Template ID and Bot ID.

Return to the Flashduty integration configuration page, fill in the corresponding Template ID and Bot ID in the form, and click the Save button.

III. Application Release and Usage#

To ensure that everyone can use the application, you need to adjust the Visible Scope of the application to all employees before publishing.

IV. FAQ#

1.

Why can't messages be delivered to individuals, and the operation record shows app not linked?

Go to Dingtalk → Workbench → Search for application name → Open Application, and complete a login to associate your Dingtalk and Flashduty accounts. The system needs to obtain your user identity to push messages.

2.

Why are the message card buttons not working or showing an error?

Go to Dingtalk → Workbench → Search for application name → Open Application, and complete a login to associate your Dingtalk and Flashduty accounts. If you have already logged in, try clicking the menu in the upper right corner, switching accounts, and logging in again to bind your account.

Ensure you have purchased enough licenses. You can check your used license status in Console → Billing Center.

3.

Why is the Dingtalk group chat list in the escalation rule empty?

Go to Dingtalk, select a group chat session, and install the Cool App. Otherwise, the group chat list cannot be obtained.

Return to the escalation rule configuration page, refresh, and reselect the group chat list.

If you still cannot get the group chat list, try uninstalling the Cool App in the group and then repeating the above steps. If the problem persists, please contact customer or dedicated technical support.

4.

Why is the War Room feature not working as expected?

Please double-check if you have configured the required permissions for the application's War Room feature.

Please refer to the FAQ section of the Flashduty War Room Introduction document.

5.

Dingtalk Custom Application API Call Limits

Dingtalk Version	Total Calls/Month	QPS	Refresh Time
Standard	10,000	20	1st of each month
Professional	500,000	40	1st of each month
Exclusive	5,500,000	60	1st of each month

After exceeding the API call limit, the Dingtalk application will not be able to push messages normally. It is recommended to use notification channels reasonably. For details, see the official Dingtalk documentation.