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

​
Operation steps

​
Create WeCom Bot Compatible integration

You can obtain a WeCom 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 WeCom Bot Compatible integration and click Save to generate a card
  4. Click the generated card to view the WeCom 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 WeCom Bot Compatible integration:
    • Integration Name: Define a name for the current integration
    • Message Type: Select Wecom alert message type, currently only Text and Post (rich text) are supported
    • Push Mode: Choose when to trigger or recover alerts for Wecom notifications
  3. Copy the WeCom 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 WeCom Bot Compatible integration

​
WeCom Bot Compatible integration URL

The system will generate a unique WeCom Bot Compatible integration URL for you. This URL is compatible with Wecom robot message protocol. When platforms only support Wecom 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: 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 random 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
The regex extraction rule must be a valid regular expression (RE2 syntax): on submit the frontend validates that it compiles, and an illegal regex (such as unsupported syntax) cannot be saved and shows “Please enter a valid regex”. Only when the regex is valid but matches nothing does the system fall back to generating a random Alert Key.
Configuration example:
  • Receive all messages, close the alert when the message content contains RESOLVED, otherwise trigger a new alert
  • Extract Alert Key from messages using the rule /(.*)/.

​
Silence detection

In the integration card (edit and preview), the Silence Detection (Heartbeat) setting is available below the base settings: if no valid event arrives within the configured interval, the system generates a Warning alert.

​
Notes

  • WeCom Bot Compatible integration URL only supports Text and Markdown message types; other message types cannot be received
  • Flashduty will generate a default alert title: “Wecom robot Alert , If you need to change the title, you can customize it using the alert pipeline”

​
Severity mapping

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