Flashduty Docs
中文EnglishRoadmapAPI官网控制台
中文EnglishRoadmapAPI官网控制台
  1. IM integration
  • Getting Started
    • Introduction
    • Quick start
    • FAQ
    • Product Comparison
  • Incidents
    • What is an Incident
    • View Incidents
    • Handle Incidents
    • Escalations and Assignments
    • Custom Fields
    • Custom Actions
    • Alert Noise Reduction
    • Past Incidents
    • Outlier Incidents
  • Configure Flashduty
    • Channels
    • Integrate Alerts
    • Alert Noise Reduction
    • Escalation Rules
    • Label Enrichment
    • Schedules
    • Templates
    • Service Calendars
    • Preferences
    • Alert Routing
    • Silence and Inhibition
    • Filters
    • Notification Bots
    • Alert Pipeline
  • Platform
    • Teams and Members
    • Permissions
    • Single Sign-On
    • Insights
  • Advanced Features
    • Referencing Variables
    • Dynamic Assignment
  • Integrations
    • Alerts integration
      • Standard Alert Integration
      • Email Integration
      • Nightingale/FlashCat Integration
      • Prometheus Integration
      • Grafana Integration
      • Zabbix Integration
      • Uptime Kuma Integration
      • Alibaba Cloud ARMS Integration
      • Alibaba Cloud Monitor CM Event Integration
      • Alibaba Cloud Monitor CM Metrics Integration
      • Alibaba Cloud SLS Integration
      • AWS CloudWatch Integration
      • Azure Monitor Integration
      • Baidu Cloud BCM Integration
      • Huawei Cloud CES Integration
      • Influxdata Integration
      • Open Falcon Integration
      • PagerDuty Integration
      • Tencent BlueKing Integration
      • Tencent Cloud CLS Integration
      • Tencent Cloud Monitor CM Integration
      • Tencent Cloud EventBridge
      • OceanBase Integration
      • Graylog Integration
      • Skywalking Integration
      • Sentry Integration
      • Jiankongbao Integration
      • AWS EventBridge Integration
      • Dynatrace Integration
      • Huawei Cloud LTS Integration
      • GCP Integration
      • Splunk Alert Events Integration
      • AppDynamics Alert Integration
      • SolarWinds Alert Events Integration
      • Volcengine CM Alert Events Integration
      • Volcengine CM Event Center Integration
      • Volcengine TLS Integration
      • OpManager Integration
      • Meraki Integration
      • Keep Integration
      • ElastAlert2 Alert Integration
      • StateCloud Alert Events
      • Guance Alert Events
      • Zilliz Alert Events
      • Huawei Cloud APM Alerts
      • zstack integration
    • Change integration
      • Standard Change Event
      • Jira Issue Events
    • IM integration
      • Feishu (Lark) Integration Guide
      • Dingtalk Integration
      • WeCom Integration
      • Slack Integration
      • Microsoft Teams Integration
    • Single Sign-On
      • Authing Integration
      • Keycloak Guide
      • OpenLDAP Guide
    • Webhooks
      • Alert webhook
      • Incident webhook
      • Costom action
  • Terms
    • Terms of Service
    • User Agreement/Privary Policy
    • SLA
    • Data Security
  1. IM integration

Dingtalk Integration

Integrate with Dingtalk custom application to receive and respond to alerts within Dingtalk.
(This guide uses the new version of Dingtalk Open Platform as an example)

I. Create Dingtalk Application#


1. Create Custom Application#

Visit Dingtalk Developer Console - Application Development - Internal Enterprise Development to create an application. (See Dingtalk development documentation - Create Internal Enterprise Application - H5 Microapp)
drawing
You can use the Flashduty official icon as the application icon.

2. Copy Enterprise CorpId#

Click on the enterprise in the upper right corner of the page, copy the CorpId from the dropdown menu for later use.
drawing

3. Copy Application Credentials#

Go to the Credentials and Basic Information page, copy AgentID, ClientID, and ClientSecret for later use.
drawing

4. Copy Event Subscription Information#

Go to Development Configuration - Events and Callbacks page.
Generate Encryption aes_key and Signature Token for later use.
(Note: After generating aes_key and Token, please temporarily save the information elsewhere, as it will disappear after leaving the page)
drawing

II. Add Dingtalk Integration#


Return to Flashduty Integration Center page, select Instant Messaging > Dingtalk, fill in the Integration Name and application information copied in the previous step, then click save to create.
drawing
After saving, you will see information such as Web Configuration address, Server Outbound IP address, and Event Subscription Request URL, which will be used in later steps.
drawing

III. Configure Dingtalk Application#


1. Add Cool App, Web App, and Bot#

drawing
1.
Create Cool App: On the Cool Apps - Cool App List page, click Create Cool App button, select Extend to Group Chat
drawing
2.
Enter the Edit Cool App page, complete the following steps:
2.1) First step, fill in basic information, you can use the Flashduty official icon as the icon.
drawing
2.2) Second step, configure functionality design, select Group Quick Access and Message Card on the left. For the group quick access icon, you can use the Flashduty official icon. Copy the Cool App Web URL from the integration details for both desktop and mobile access URLs.
drawing
2.3) Skip the third step of function development, proceed to the fourth step Preview and Release, click the Release button and confirm.

2. Configure Bot and Message Push#

Enter the Application Capabilities - Bot page, enable bot configuration, fill in the name and upload an icon. You can use the Flashduty official icon, then save.
drawing

3. Configure Application URLs#

Enter the Application Capabilities - Web Application page
1.
Configure Application Homepage URL and PC Homepage URL with the content from the integration details' Application Homepage URL and PC Homepage URL.
2.
Click Save in the upper right corner.
drawing

4. Configure Event Subscription#

1.
On the Development Configuration - Event Subscription page, configure the Request URL with the content from the integration details' Event Subscription Request URL, then Save.
drawing
2.
Below the Save button, select three group chat events: Group Chat Name Change, Cool App Installation in Group, and Cool App Uninstallation in Group, then Save.
drawing

5. Apply for Application Permissions#

Enter the Permission Management page, apply for qyapi_chat_manage and qyapi_robot_sendmsg permissions. These two permissions will allow the current application to obtain its own group chat information and send messages to groups or individuals.
drawing

IV. Application Release and Usage#


After completing the above steps, go to Application Release - Version Management and Release, create a new version, then proceed with the release (make sure to adjust the visibility to all employees, otherwise others cannot use it)
drawingdrawing
After the application is released, you can access it via mobile/PC client. First-time access requires login and account association (Dingtalk 《-》 Flashduty), subsequent uses will be login-free.
1.
Mobile: Access the web application through Dingtalk > Workspace > Search application name > Open application.
2.
PC: Access the web application through Dingtalk > Workspace > Search application name > Open application.

V. Common Issues#


1.
Cannot deliver messages to individuals, operation record shows Application Not Associated?
Go to Dingtalk > Workspace > Search application name > Open application, complete one login and account association (Dingtalk 《-》 Flashduty), so the system can obtain user identity for message pushing
2.
Message card buttons are ineffective or show errors?
Go to Dingtalk > Workspace > Search application name > Open application, complete one login and account association (Dingtalk 《-》 Flashduty). If already logged in, try clicking the menu in the upper right corner, switch accounts, and log in again to bind the account
Ensure you have purchased sufficient licenses. You can check license usage in Console > Billing Center
3.
Escalation rule Dingtalk group chat list is empty?
Go to Dingtalk, select group chat 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 still unable to get the group chat list, try uninstalling the Cool App from the group and repeat the above steps. If it still doesn't work, please contact customer or dedicated technical support
drawingdrawing
4.
Dingtalk Custom Application API Call Limits: Dingtalk Documentation
Dingtalk VersionTotal Calls/MonthQPSRefresh Time
Standard10,000201st of each month
Professional500,000401st of each month
Enterprise5,500,000601st of each month
Note: Messages cannot be pushed normally after exceeding limits, please use notification channels reasonably
修改于 2024-11-25 03:16:53
上一页
Feishu (Lark) Integration Guide
下一页
WeCom Integration
Built with