fix: i18n

Author: debidong

README.md

@@ -70,4 +70,9 @@ date: "2023-12-18T10:00:00+08:00"
 请你严格依照 @polish_instructions.md 的要求，对文档 @your_doc_name 进行润色。
 ```
 
-完成润色后，可在 VSCode / Cursor 中打开文档，然后在文档 tab 页中右击，点击 `格式化文档`。
+<<<<<<< HEAD
+完成润色后，可在 VSCode / Cursor 中打开文档，然后在文档 tab 页中右击，点击 `格式化文档`。
+
+=======
+完成润色后，可在 VSCode / Cursor 中打开文档，然后在文档 tab 页中右击，点击 `格式化文档`。
+>>>>>>> f-warroom

flashduty/en/1. On-call/8. Integrations/8.1 Alerts integration/8.1.52 WecomAlert Integration.md

@@ -0,0 +1,81 @@
+---
+title: "Wecom Alert Integration"
+description: "Generate a unique Wecom robot address in Flashduty, and synchronize the occurrence and recovery of alerts through Wecom"
+date: "2025-05-19T10:00:00+08:00"
+url: "https://docs.flashcat.cloud/en/flashduty/Wecom-alert-integration-guide"
+---
+
+Generate a unique Wecom robot address in Flashduty, and synchronize the occurrence and recovery of alerts through Wecom.
+
+<div class="hide">
+
+## Operation Steps
+---
+
+### Create Wecom Alert Integration
+
+You can obtain a Wecom alert integration address through either of these two methods:
+
+#### Using Dedicated Integration
+
+Choose this method when you don't need to route alert events to different channels. It's simpler and recommended.
+
+<details>
+  <summary>Expand</summary>
+  
+  1. Go to the Flashduty console, select **Channel**, and enter a specific channel's details page
+  2. Select the **Integration** tab, click **Add Integration** to enter the integration page
+  3. Choose **Wecom Alert** integration and click **Save** to generate a card
+  4. Click the generated card to view the **Wecom Alert Integration URL**, copy it for later use, and you're done
+    
+</details>
+
+#### Using Shared Integration
+
+Choose this method when you need to route alerts to different channels based on the alert event's payload information.
+
+<details>
+  <summary>Expand</summary>
+  
+  1. Go to the Flashduty console, select **Integration Center => Alert Events** to enter the integration selection page
+  2. Select **Wecom Alert** integration:
+        - **Integration Name**: Define a name for the current integration
+        - **Message Type**: Select Wecom alert message type, currently only Text and Markdown are supported
+        - **Push Mode**: Choose when to trigger or recover alerts for Wecom notifications
+  3. Copy the **Wecom Alert 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)
+  5. Done
+    
+</details>
+</div>
+
+### Customize Wecom Alert Integration
+
+#### Wecom Alert Integration URL
+
+The system will generate a unique Wecom alert 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 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 messages using the rule **/(.*)/**.
+
+
+### Notes
+- Wecom alert 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](https://docs.flashcat.cloud/en/flashduty/alert-pipelines)"
+
+## Severity Mapping
+---
+
+Currently, all alerts pushed to Flashduty through the Wecom integration are set to Warning severity. However, you can customize the severity using the [alert pipeline](https://docs.flashcat.cloud/en/flashduty/alert-pipelines).

flashduty/en/1. On-call/8. Integrations/8.3 IM integration/8.3.1 Feishu(Lark) Integration Guide.md

@@ -55,8 +55,8 @@ For details, see the Feishu/Lark development documentation [Configure applicatio
 
 3. Go to Event Callbacks → **Callback Configuration** page, configure the `Subscription Method` (using the **Message Card Request URL** from the integration details). Then, subscribe to the following two callback events:
 
-- `im.message.receive_v1`
-- `im.chat.disbanded_v1`
+- `card.action.trigger`
+- `card.action.trigger_v1`
 
 ![2025-09-17-19-53-14](https://docs-cdn.flashcat.cloud/images/png/c42542dc49930c2e20f5921749bf3565.png)
 
@@ -115,7 +115,7 @@ After completing the previous steps, in the **Enhanced Features** module of the
    - Go to Feishu/Lark and add the created Flashduty bot to the specified group chat.
    - Return to the escalation rule configuration page, refresh and reselect the group chat list.
 
-![2025-09-18-14-26-32](https://docs-cdn.flashcat.cloud/images/png/a5878acb02929c9f660c549577de5c17.png)
+![2025-09-17-20-07-23](https://docs-cdn.flashcat.cloud/images/png/27a5422ec27b5f63fb6dee81b3d50510.png)
 
 4. **Feishu/Lark custom application API limits?**
    - **Call volume limits:**