Skip to main content
Generate a unique Dingtalk robot address in Flashduty, and synchronize the occurrence and recovery of alerts through Dingtalk.

​
Operation steps

​
Create DingTalk Bot Compatible integration

You can obtain a DingTalk Bot Compatible integration address through either of these two methods:

​
Use a dedicated integration

Choose this option if all alerts go to one channel. It’s the simpler setup.
  1. In the Flashduty console, select Channel and open a channel
  2. Select Configuration → Integrations → Private integration, then click Add an integration
  3. Choose DingTalk Bot Compatible integration and click Save to generate a card
  4. Click the generated card to view the DingTalk Bot Compatible Integration URL, copy it for later use, and you’re done

​
Use a shared integration

Choose this option if you need to route alerts to different channels based on the alert payload.
  1. In the Flashduty console, go to Integration Center → Alert Events
  2. Select DingTalk Bot Compatible integration:
    • Integration Name: Define a name for the current integration
    • Message Type: Select Dingtalk alert message type, currently only Text and Markdown are supported
    • Push Mode: Choose when to trigger or recover alerts for Dingtalk notifications
  3. Copy the DingTalk Bot Compatible Integration URL for later use
  4. Configure the default route and select the corresponding channel (after integration creation, you can go to Routes to configure more routing rules)

​
Customize DingTalk Bot Compatible integration

​
DingTalk Bot Compatible integration URL

The system will generate a unique DingTalk Bot Compatible integration URL for you. This URL is compatible with Dingtalk robot message protocol. When platforms only support Dingtalk robot channels, you can use this URL to receive corresponding messages.

​
Push mode

By default, the system always creates new alerts for each message, but you can switch to these modes:
  1. Trigger or Update Alert Based on Message Title: In this mode, when receiving a new message, the system searches for open alerts based on the message title. If an alert is found, it will be updated; otherwise, a new alert will be triggered.
  2. Trigger or Close Alert Based on Rules: In this mode, when receiving a new message, the system matches messages according to your rules and triggers new alerts or closes existing alerts based on the matching results.
    • You need to fill in at least one trigger rule
    • You must set up regex extraction rules for Alert Key. The system uses this field to find historical alerts for updates or closure. If regex extraction fails, the system will use the message title to generate an Alert Key to ensure alerts won’t be lost due to configuration errors
    • You can choose whether to discard messages when none of the rules match
    Configuration example:
    • Receive all messages, close the alert when the message content contains RESOLVED, otherwise trigger a new alert
    • Extract Alert Key from message title using the rule /(.*)/.

​
Notes

  • DingTalk Bot Compatible integration URL only supports Text and Markdown message types; other message types cannot be received
  • When Dingtalk message type is Text, Flashduty will generate a default alert title “Dingtalk Alert”

​
Severity mapping

Currently, all alerts pushed to Flashduty through the DingTalk Bot Compatible integration are set to Warning severity. However, you can customize the severity using the alert pipeline.

​
Alibaba Cloud Message Center

The “Robot Reception” feature in Alibaba Cloud’s account Message Center can push account, product, and security notices to a custom webhook. Its data format can reuse the Dingtalk robot protocol, so it connects directly to the DingTalk Bot Compatible integration on this page.
  1. Log in to Alibaba Cloud Message Center, go to Robot Reception Management → Robot Management → Add Robot
  2. Select Custom for Robot Platform, enter the DingTalk Bot Compatible Integration URL from above for Webhook Address, and select Format A (typically used by Dingtalk) for Data Format
  3. Complete the CAPTCHA verification and save
Notices from Message Center are one-shot — there is no paired recovery message. Refer to “Push Mode” above and configure Trigger or Update Alert Based on Message Title or Trigger or Close Alert Based on Rules so alerts don’t stay open forever.
If you’re integrating Alibaba Cloud Monitor (CloudMonitor) alerts, use the Alibaba Cloud Monitor CM Metrics Integration directly for full dedup and recovery support.