flashduty-knowledge-base 1.3.3 → 1.3.5

package/dist/esm/en.js

@@ -1594,7 +1594,7 @@ Alibaba Cloud SLS monitoring to Flashduty alert severity mapping:
 | 2                | Info      | Info |
 
 </div>
-`,u=`---
+`,h=`---
 title: "AWS CloudWatch Integration"
 description: "Sync AWS CloudWatch alert events to Flashduty via webhook to achieve automated alert noise reduction"
 date: "2025-05-19T10:00:00+08:00"
@@ -1673,7 +1673,7 @@ Choose this method when you need to route alerts to different channels based on
 All CloudWatch metric alarms correspond to Flashduty "warning" severity level alerts.
 
 </div>
-`,h=`---
+`,u=`---
 title: "Baidu Cloud BCM Integration"
 description: "Sync Baidu Cloud BCM alerts to Flashduty via webhook for automated alert noise reduction"
 date: "2025-05-19T10:00:00+08:00"
@@ -3164,7 +3164,7 @@ Choose this option when you need to route alerts to different channels based on
 |2|Info|Info|
 
 </div>
-`,x=`---
+`,F=`---
 title: "AWS EventBridge Alert Events"
 description: "Sync AWS EventBridge alert events to Flashduty via webhook for automated alert noise reduction"
 date: "2024-08-20T10:00:00+08:00"
@@ -3266,7 +3266,7 @@ Choose this option when you need to route alerts to different channels based on
 
 </div>
 
-`,L=`---
+`,x=`---
 title: "Dynatrace Alert Events"
 description: "Sync Dynatrace alert events to Flashduty via webhook to achieve automated alert noise reduction."
 date: "2024-08-20T10:00:00+08:00"
@@ -3373,7 +3373,7 @@ Choose this option when you need to route alerts to different channels based on
 |CUSTOM_ALERT|Info|info|
 
 </div>
-`,F=`---
+`,L=`---
 title: "Huawei Cloud LTS Alert Events"
 description: "Sync Huawei Cloud Log Tank Service (LTS) alert events to Flashduty via webhook for automated alert noise reduction."
 date: "2024-08-20T10:00:00+08:00"
@@ -3812,7 +3812,7 @@ If you need to configure \`Custom Templating Variables\`, you can refer to the f
 |INFO|Info|Info|
 
 </div>
-`,U=`---
+`,D=`---
 title: "SolarWinds Alert Events"
 description: "Sync SolarWinds alert events to Flashduty via webhook for automated alert noise reduction"
 date: "2024-08-20T10:00:00+08:00"
@@ -3915,7 +3915,7 @@ Choose this option when you need to route alerts to different channels based on
 |Info|Info|Info|
 
 </div>
-`,D=`---
+`,U=`---
 title: "Volcengine Cloud Monitor Alert Events"
 description: "Sync Volcengine Cloud Monitor alert events to Flashduty via webhook for automated alert noise reduction"
 date: "2024-08-20T10:00:00+08:00"
@@ -4228,7 +4228,7 @@ Choose this method when you need to route alerts to different channels based on
 </div>
 
 </div>
-`,M=`---
+`,P=`---
 title: "OpManager Alert Events"
 description: "Sync OpManager alert events to Flashduty via webhook for automated alert noise reduction"
 date: "2024-07-05T10:00:00+08:00"
@@ -4362,7 +4362,7 @@ Choose this method when you need to route alerts to different channels based on
 | Attention  | Info           | Info |
 
 </div>
-`,P=`---
+`,M=`---
 title: "Meraki Alert Events"
 description: "Sync Meraki alert events to Flashduty via webhook for automated alert noise reduction"
 date: "2024-07-05T10:00:00+08:00"
@@ -4785,7 +4785,7 @@ When you need to route alerts to different channels based on alert payload infor
 
 </div>
 
-`,j=`---
+`,$=`---
 title: "zstack integration"
 description: "Push ZStack alerts to Flashduty via webhook, to achieve automatic alert noise reduction."
 date: "2024-07-05T10:00:00+08:00"
@@ -4873,7 +4873,7 @@ Choose this method when you need to route alerts to different channels based on
 
 </div>
 
-`,H=`---
+`,j=`---
 title: "Keep Alert Integration Guide"
 description: "Push alert events to Flashduty through Keep's Provider to achieve automated alert noise reduction."
 date: "2025-05-19T10:00:00+08:00"
@@ -4954,7 +4954,7 @@ Field|Required|Type|Definition
 
 <img alt="drawing" width="600" src="https://download.flashcat.cloud/flashduty/doc/en/fd/keep-2.png" />
 
-`,Y=`---
+`,H=`---
 title: "ElastAlert2 Alert Integration Guide"
 description: "Push alert events to Flashduty through ElastAlert2's Provider to achieve automated alert noise reduction."
 date: "2025-05-19T10:00:00+08:00"
@@ -5075,7 +5075,7 @@ flashduty_env: "dev"
 # ------- FlashDuty ----------------
 \`\`\`
 
-5. Restart ElastAlert and wait for the alert to trigger.`,$=`---
+5. Restart ElastAlert and wait for the alert to trigger.`,Y=`---
 title: "Dingtalk Alert Integration"
 description: "Generate a unique Dingtalk robot address in Flashduty, and synchronize the occurrence and recovery of alerts through Dingtalk"
 date: "2025-05-19T10:00:00+08:00"
@@ -5157,7 +5157,7 @@ By default, the system always creates new alerts for each message, but you can s
 ---
 
 Currently, all alerts pushed to Flashduty through the Dingtalk integration are set to Warning severity. However, you can customize the severity using the [alert pipeline](https://docs.flashcat.cloud/en/flashduty/alert-pipelines).
-`,V=`---
+`,z=`---
 title: "Feishu Alert Integration"
 description: "Generate a unique Feishu robot address in Flashduty, and synchronize the occurrence and recovery of alerts through Feishu"
 date: "2025-05-19T10:00:00+08:00"
@@ -5321,7 +5321,7 @@ Choose this method when you need to route alerts to different channels based on
 
 </div>
 
-`,z=`---
+`,V=`---
 title: "Monit Alert Integration"
 description: "Flashduty Monit alert integration, Monit service reports alerts through this integration"
 date: "2025-05-19T10:00:00+08:00"
@@ -5433,6 +5433,86 @@ Currently, all alerts pushed to Flashduty through the Cloudflare integration are
 </div>
 
 `,Z=`---
+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 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
+
+   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).`,Q=`---
 title: "Custom Change Event Integration Guide"
 description: "Push change events from your own systems to Flashduty using standard protocols. Most incidents are caused by changes, and the correlation between changes and alerts helps quickly identify incident causes."
 date: "2025-05-19T10:00:00+08:00"
@@ -5489,7 +5569,7 @@ Labels are descriptions of events. You should enrich label content as much as po
     
 </details>
 
-`,Q=`---
+`,X=`---
 title: "Jira Issue Events"
 description: "Sync Jira Issue events to Flashduty via webhooks to collect change events."
 date: "2025-05-19T10:00:00+08:00"
@@ -5563,559 +5643,674 @@ Flashduty extracts the status.name information from the webhook payload by defau
 Please contact Flashduty if you wish to modify this mapping.
 
 </div>
-`,X=`---
-title: Contributing to our documentation — Meilisearch documentation
-description: The Meilisearch documentation is open-source. Learn how to help make it even better.
-sidebarDepth: 3
+`,ee=`---
+title: "Feishu/Lark Integration"
+description: "By integrating a custom Feishu/Lark application, you can receive and respond to alerts within Feishu/Lark."
+date: "2025-05-19T10:00:00+08:00"
+url: "https://docs.flashcat.cloud/en/flashduty/lark-integration-guide?nav=01JCQ7A4N4WRWNXW8EWEHXCMF5"
 ---
+By integrating a custom Feishu/Lark application, you can receive and respond to alerts within Feishu/Lark.
 
-Integrate with Feishu(Lark) custom application to receive and respond to alerts within Feishu/Lark.
-
-<!--
-## Video Tutorial
+## 1. Create Feishu/Lark application
 ---
-<Video src="https://download.flashcat.cloud/flashduty/video/feishu.mp4"></Video>
--->
 
-## I. Create Feishu/Lark Application
----
+### 1. Create a custom application
 
-### 1. Create Custom Application
+Visit [Feishu/Lark Developer Console](https://open.feishu.cn/app) and create an internal custom application. You can use the [official Flashduty icon](https://download.flashcat.cloud/flashcat_logo_circular.png) for the application icon.
 
-Visit [Feishu/Lark Developer Console](https://open.feishu.cn/app) to create an internal custom application. (For details, see Feishu/Lark development documentation - [Create Enterprise Custom Application](https://open.feishu.cn/document/uYjL24iN/uMTMuMTMuMTM/development-guide/step1#132c1aac))
+For details, see the Feishu/Lark development documentation [Create an internal custom application](https://open.feishu.cn/document/uYjL24iN/uMTMuMTMuMTM/development-guide/step1#132c1aac).
 
-<img src="https://download.flashcat.cloud/flashduty/doc/en/feishu/feishu-1.png" alt="drawing" width="400"/>
+![2025-09-17-19-20-33](https://docs-cdn.flashcat.cloud/images/png/9af11beec76ef03b935e5ba71ac2f5f5.png)
+### 2. Copy credential information
 
-You can use the [Flashduty official icon](https://download.flashcat.cloud/flashcat_logo_circular.png) as the application icon.
+Go to the **Credentials and Basic Information** page and copy the \`App ID\` and \`App Secret\` for later use.
 
-### 2. Copy Credentials
 
-Go to the **Credentials & Basic Info** page, copy the \`App ID\` and \`App Secret\` for later use.
+![2025-09-17-19-24-11](https://docs-cdn.flashcat.cloud/images/png/9b72a772eaa94a7115e8568e9ae7b496.png)
 
-<img src="https://download.flashcat.cloud/flashduty/doc/en/feishu/feishu-2.png" alt="drawing" width="800"/>
+### 3. Copy the event callback Token information
 
-### 3. Copy Event Callback Token Information
+Go to Development Configuration → Events & Callbacks → **Encryption Strategy** page, generate and copy the \`Encrypt Key\` (recommended for better security) and \`Verification Token\` for later use.
 
-Go to **Development Configuration - Events & Callbacks - Encryption Configuration** page, copy the \`Encrypt Key\` (recommended for better security) and \`Verification Token\` for later use.
+![2025-09-17-19-27-24](https://docs-cdn.flashcat.cloud/images/png/48d8ef62cef639cb433078c878c3a4a0.png)
 
-<img src="https://download.flashcat.cloud/flashduty/doc/en/feishu/feishu-2.png" alt="drawing" width="800"/>
+## 2. Add Feishu/Lark integration
+---
 
-## II. Add Feishu/Lark Integration
+Return to the Flashduty **Integration Center** page, select IM → **Feishu/Lark**, fill in the \`Name\` and the \`App ID\`, \`App Secret\`, \`Verification Token\`, and \`Encrypt Key\` copied in the previous step, then click **Save** to complete the creation.
+
+After successful creation, you will see the added Feishu/Lark integration in the list. Click its name to enter the details page, where you can view the **Web Configuration** address, **Redirect URL**, and **Message Card Request URL**, which will be used in subsequent steps.
+
+![2025-09-17-19-32-56](https://docs-cdn.flashcat.cloud/images/png/b4bfa3d7fdf1af9b8006be168d454700.png)
+
+## 3. Configure Feishu/Lark application
 ---
 
-Return to Flashduty **Integration Center** page, select **Instant Messaging => Feishu/Lark**, fill in the \`Name\` and the previously copied \`App ID\`, \`App Secret\`, \`Verification Token\`, and \`Encrypt Key\`, then click save to create.
+### 1. Enable and configure application capabilities
 
-<img src="https://download.flashcat.cloud/flashduty/doc/en/feishu/feishu-4.png" alt="drawing" width="800"/>
+1. Return to the Feishu/Lark Developer Console, enter the created Feishu/Lark application, go to Add Application Capabilities → **Add by Capability** page, and enable both **Web Application** and **Bot** capabilities.
 
-After creation, you'll see the newly added Feishu/Lark integration in the list. Click on the name to enter details, where you'll find the **Web Configuration** URL, **Redirect URL**, and **Message Card Request URL** information, which will be used in later steps.
+![2025-09-17-19-42-32](https://docs-cdn.flashcat.cloud/images/png/b12ddbeed2b8d7f508eccc1078c2c12c.png)
 
-<img src="https://download.flashcat.cloud/flashduty/doc/en/feishu/feishu-5.png" alt="drawing" width="800"/>
+2. Go to the **Web app** page and configure the \`Desktop Homepage\` and \`Mobile Homepage\`, both using the **Web configuration** address from the integration details.
 
-## III. Configure Feishu/Lark Application
----
+For details, see the Feishu/Lark development documentation [Configure application homepage address](https://open.feishu.cn/document/uYjL24iN/uMTMuMTMuMTM/development-guide/step1#8366b844).
 
-### 1. Enable and Configure Application Capabilities
+![2025-09-17-19-49-19](https://docs-cdn.flashcat.cloud/images/png/393e7629de652d1793b69af7d4f3831c.png)
 
-1). Return to the Feishu/Lark Developer Console, enter the newly created application, go to **Add Capabilities - Add by Capability** page, and enable both **Web Application** and **Bot** capabilities.
+3. Go to Event Callbacks → **Event Configuration** page, configure the \`Request URL\` (using the **Message Card Request URL** from the integration details). Then, add the following two events:
 
-<img src="https://download.flashcat.cloud/flashduty/doc/en/feishu/feishu-6.png" alt="drawing" width="800"/>
+- \`im.chat.disbanded_v1\`
+- \`im.message.receive_v1\`
 
-2). Go to **Web Application** page, configure both \`Desktop Homepage\` and \`Mobile Homepage\` with the **Web Configuration** URL from the integration details.
+![2025-09-18-11-06-05](https://docs-cdn.flashcat.cloud/images/png/71910d8af8d60b5f30baf009081646df.png)
 
-<img src="https://download.flashcat.cloud/flashduty/doc/en/feishu/feishu-7.png" alt="drawing" width="800"/>
+4. Go to Event Callbacks → **Callback Configuration** page, configure the \`Request URL\` (using the **Message Card Request URL** from the integration details). Then, subscribe to the following two callbacks:
 
-(See Feishu/Lark development documentation - [Configure Application Homepage URL](https://open.feishu.cn/document/uYjL24iN/uMTMuMTMuMTM/development-guide/step1#8366b844))
+- \`card.action.trigger\`
+- \`card.action.trigger_v1\`
 
-3). Go to **Event Callbacks - Callback Configuration** page, configure the \`Message Card Request URL\` (using the **Message Card Request URL** from integration details) and add the callback.
+![2025-09-19-18-41-42](https://docs-cdn.flashcat.cloud/images/png/5ebe9faff7f78a6764da92a342eab7c0.png)
 
-<img src="https://download.flashcat.cloud/flashduty/doc/en/feishu/feishu-8.png" alt="drawing" width="800"/>
-<img src="https://download.flashcat.cloud/flashduty/doc/en/feishu/feishu-9.png" alt="drawing" width="800"/>
+### 2. Add redirect URL to Feishu/Lark application
 
-### 2. Add Redirect URL to Feishu/Lark Application
+Go to the **Security Settings** page and configure the \`Redirect URL\` using the **Redirect URL** from the integration details.
 
-Go to **Security Settings** page, configure the \`Redirect URL\` using the **Redirect URL** from integration details.
+For details, see the Feishu/Lark development documentation [Configure redirect URL](https://open.feishu.cn/document/uYjL24iN/uYjN3QjL2YzN04iN2cDN?lang=zh-CN#c863e533).
 
-<img src="https://download.flashcat.cloud/flashduty/doc/en/feishu/feishu-10.png" alt="drawing" width="800"/>
+![2025-09-17-19-55-04](https://docs-cdn.flashcat.cloud/images/png/6f97810d9542514c40c276588179e04f.png)
 
-(See Feishu/Lark development documentation - [Configure Redirect URL](https://open.feishu.cn/document/uYjL24iN/uYjN3QjL2YzN04iN2cDN?lang=zh-CN#c863e533))
+### 3. Apply for application permissions
 
-### 3. Request Application Permissions
+Go to the **Permission Management** page and apply for the following permissions for the group application created in the previous steps:
 
-Go to **Permission Management** page, request \`im:chat\` and \`im:message\` permissions. These permissions will allow the application to access its group chat information and send messages to groups or individuals.
+- \`im:chat\`: Get and update group information
+- \`im:message\`: Get and send single chat and group messages
+- \`contact:user.id:readonly\`: Get user ID by phone number or email <span id="war-room-scope"></span>
 
-<img src="https://download.flashcat.cloud/flashduty/doc/en/feishu/feishu-11.png" alt="drawing" width="800"/>
+![2025-09-17-19-59-38](https://docs-cdn.flashcat.cloud/images/png/61cb9fbc295e94b4d9acd7e44ac75e13.png)
 
-## IV. Application Publication and Usage
+## 4. Application release
 ---
 
-After completing the above steps, proceed with application publication and usage. The application can be used after administrator approval.
-Note: **Available Range** needs special configuration, recommended for **All Employees**.
+After completing all the above configurations, please release the application. It can be used after administrator approval.
 
-<img src="https://download.flashcat.cloud/flashduty/doc/en/feishu/feishu-12.png" alt="drawing" width="800"/>
+For details, see the Feishu/Lark development documentation [Application release and usage](https://open.feishu.cn/document/uYjL24iN/uMTMuMTMuMTM/development-guide/step-4).
 
-See Feishu/Lark development documentation - [Application Publication and Usage](https://open.feishu.cn/document/uYjL24iN/uMTMuMTMuMTM/development-guide/step-4).
+> To ensure that everyone can use the application, adjust the application **visibility** to all employees before releasing the application.
 
-Once published, you can access the application via mobile/PC client. First-time access requires login and account association (Feishu/Lark 《-》 Flashduty), subsequent uses will be login-free.
+![2025-09-17-20-01-46](https://docs-cdn.flashcat.cloud/images/png/af3d458ed4c1a3e3346c91dc6a8fa667.png)
 
-1. Mobile: Access the web application through Feishu/Lark > Workspace > Search application name > Open application.
-2. PC: Access the web application through Feishu/Lark > Workspace > Search application name > Open application.
 
-## V. Common Issues
----
-
-1. **Unable to deliver messages to individuals**, operation record shows \`Application Not Associated\`?
+After the application is released, you can access it via **mobile** or **PC**. The first access requires login to link your Feishu/Lark and Flashduty accounts. Subsequent access will be login-free.
 
-    - Go to Feishu/Lark > Workspace > Search application name > Open application, complete one login and account association (Feishu/Lark 《-》 Flashduty) for the system to obtain user identity for message pushing
+- **Mobile**: Access via Feishu/Lark → Workplace → Search for application name → **Open Application** to use the web application.
+- **PC**: Access via Feishu/Lark → Workplace → Search for application name → **Open Application** to use the web application.
 
-2. **Message card buttons not working or showing errors**?
+![2025-09-17-20-05-01](https://docs-cdn.flashcat.cloud/images/png/1da64327149790ceb45ff3b66476be7f.png)
 
-    - Ensure account association is completed. Go to Feishu/Lark > Workspace > Search application name > Open application, complete one login and account association (Feishu/Lark 《-》 Flashduty). If already logged in, try clicking the top-right menu to switch accounts and re-login to bind the account
-    - Ensure sufficient licenses are purchased. You can check license usage in Console > Billing Center
+## 5. Configure war room
 
-3. **Empty Feishu/Lark group chat list in escalation rule**?
+> Ensure the application has been authorized with the [additional permissions](#war-room-scope) required for the war room feature.
 
-    - Go to Feishu/Lark, select group chat conversation, add the created Flashduty bot as shown below:
-    - Return to the escalation rule configuration page, refresh and reselect the group chat list
+After completing the previous steps, in the **Enhanced Features** module of the Flashduty integration configuration page, check **Enable War Room** to enable this feature without additional configuration.
 
-<img alt="drawing" width="800" src="https://download.flashcat.cloud/flashduty/doc/en/feishu/feishu-13.png" />
-<img src="https://download.flashcat.cloud/flashduty/doc/en/feishu/feishu-14.png" alt="drawing" width="800"/> 
+## 6. FAQ
+---
 
-4. **Feishu/Lark Custom Application API Limits:** [Feishu/Lark Documentation](https://open.feishu.cn/document/uAjLw4CM/ugTN1YjL4UTN24CO1UjN/platform-updates-/custom-app-api-call-limit)
+1. **Messages cannot be delivered to individuals, and the operation log shows \`app not linked\`?**
+   - Go to Feishu/Lark → Workplace → Search for application name → **Open Application**, complete login once to link your Feishu/Lark and Flashduty accounts, so the system can obtain user identity for message push.
+2. **Message card buttons are unresponsive or show errors?**
+   - Ensure the account has been linked. You can go to Feishu/Lark → Workplace → Search for application name → **Open Application** to complete login once. If you have 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 the license usage in Console → **Billing Center**.
+3. **The Feishu/Lark group chat list in escalation rules is empty?**
+   - 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.
 
-    **Call Volume Limits:**
+![2025-09-18-14-26-32](https://docs-cdn.flashcat.cloud/images/png/a5878acb02929c9f660c549577de5c17.png)
 
-    |     Feishu/Lark Version     | Total Calls/Month | Reset Time  |                       
-    | :----------: | :--: | :----: |
-    |Basic Free Version|10,000 calls|1st of each month|
-    |Other Versions|Unlimited|-|        
+4. **Feishu/Lark custom application API limits?**
+   - **Call volume limits:**
 
-    **Frequency Control Limits:**
+     | **Feishu/Lark Version** | **Total Calls/Month** | **Refresh Time** |
+     | :---: | :---: | :---: |
+     | Basic Free | 10,000 | 1st of each month |
+     | Other Versions | Unlimited | - |
 
-    |    Scenario     | Limit |                   
-    | :----------: | :--: | 
-    |All APIs|Maximum 50 calls/second per application|
-    |Message Sending API|Maximum 1000 calls/minute per application|
-    |Group Bot Webhook|Maximum 100 calls/minute|
-    |Sending messages to the same user or group|Maximum 5 calls/second|
+   - **Rate limits:**
 
-    **Note:** Messages cannot be pushed normally when exceeding limits, please use notification channels reasonably`,ee=`---
+     | **Scenario** | **Limit** |
+     | :---: | :--- |
+     | All APIs | Max 50 calls/second per app |
+     | Send message APIs | Max 1000 calls/minute per app |
+     | Group bot webhook | Max 100 calls/minute |
+     | Send to same user or group | Max 5 calls/second |
+   
+   > After exceeding API call limits, the Feishu/Lark application will not be able to push messages normally. It is recommended to use notification channels reasonably. See [Feishu/Lark official documentation](https://open.feishu.cn/document/uAjLw4CM/ugTN1YjL4UTN24CO1UjN/platform-updates-/custom-app-api-call-limit) for details.
+5. **Why is the war room feature not working as expected?**
+   - Please check again whether you have configured the [required permissions](#war-room-scope) for the war room feature.
+   - Please refer to the **FAQ** section of the Flashduty [War Room Introduction](https://docs.flashcat.cloud/en/flashduty/war-room?nav=01JCQ7A4N4WRWNXW8EWEHXCMF5).`,ne=`---
 title: "Dingtalk Integration"
-description: "Integrate with Dingtalk custom application to receive and respond to alerts within Dingtalk"
+description: "By integrating a custom Dingtalk application, you can receive and respond to alerts within Dingtalk."
 date: "2025-05-19T10:00:00+08:00"
-url: "https://docs.flashcat.cloud/en/flashduty/dingtalk-integration-guide"
+url: "https://docs.flashcat.cloud/en/flashduty/dingtalk-integration-guide?nav=01JCQ7A4N4WRWNXW8EWEHXCMF5"
 ---
 
-Integrate with Dingtalk custom application to receive and respond to alerts within Dingtalk.
+By integrating a custom Dingtalk application, you can receive and respond to alerts within Dingtalk.
+
+> This document uses the new version of the Dingtalk Open Platform as an example.
+
+
+## I. Create Dingtalk Application and Add Dingtalk Integration
 
-**(This guide uses the new version of Dingtalk Open Platform as an example)**
-<!--
-## Video Tutorial
----
-<Video src="https://download.flashcat.cloud/flashduty/video/dingding.mp4"></Video>
--->
-## I. Create Dingtalk Application
 ---
 
-### 1. Create Custom Application
+### 1. Create a Custom Application
+
+Visit the [Dingtalk Developer Console](https://open-dev.dingtalk.com/fe/app) → Application Development → **Internal Enterprise Development** to create an application.
+
+For details, please refer to the Dingtalk development documentation [Create an in-house application-H5 micro-application](https://open.dingtalk.com/document/orgapp/microapplication-creation-and-release-process#title-ovn-666-1ty).
+
+![2025-09-18-15-02-55](https://docs-cdn.flashcat.cloud/images/png/3a66cc08c2a9ecb5669c985e05deb129.png)
 
-Visit [Dingtalk Developer Console](https://open-dev.dingtalk.com/fe/app) - Application Development - Internal Enterprise Development to create an application. (See Dingtalk development documentation - [Create Internal Enterprise Application - H5 Microapp](https://open.dingtalk.com/document/orgapp/microapplication-creation-and-release-process#title-ovn-666-1ty))
+You can use the [Flashduty official icon](https://download.flashcat.cloud/flashcat_logo_circular.png) for the application icon.
 
-<img src="https://download.flashcat.cloud/flashduty/doc/en/ding/ding-1.png" alt="drawing" width="400"/>
+### 2. Copy the Enterprise \`CorpId\`
 
-You can use the [Flashduty official icon](https://download.flashcat.cloud/flashcat_logo_circular.png) as the application icon.
+Click on the enterprise avatar in the top right corner of the page and copy the \`CorpId\` from the dropdown menu.
 
-### 2. Copy Enterprise CorpId
+![2025-09-18-15-03-12](https://docs-cdn.flashcat.cloud/images/png/3abe7ce647a78264290a8d311b62a842.png)
 
-Click on the enterprise in the upper right corner of the page, copy the \`CorpId\` from the dropdown menu for later use.
+Return to the Flashduty integration configuration page and fill in the corresponding \`CorpId\` in the form.
 
-<img src="https://download.flashcat.cloud/flashduty/doc/en/ding/ding-2.png" alt="drawing" width="500"/>
+### 3. Copy Application Credential Information
 
-### 3. Copy Application Credentials
+Enter the application details interface you created, go to the Application Capability → **Credentials and Basic Information** page via the left menu bar, and copy the \`AgentId\`, \`Client ID\`, and \`Client Secret\`.
 
-Go to the **Credentials and Basic Information** page, copy \`AgentID\`, \`ClientID\`, and \`ClientSecret\` for later use.
+![2025-09-18-15-04-39](https://docs-cdn.flashcat.cloud/images/png/075fc5989770ef3e76aa39320fe55bdf.png)
 
-<img src="https://download.flashcat.cloud/flashduty/doc/en/ding/ding-3.png" alt="drawing" width="500"/>
+Return to the Flashduty integration configuration page and fill in the corresponding \`AgentId\`, \`Client ID\`, and \`Client Secret\` in the form.
 
 ### 4. Copy Event Subscription Information
 
-Go to **Development Configuration - Events and Callbacks** page.
+Go to Development Configuration → **Events and Callbacks** page. Set the push method to \`HTTP Push\`, then click the button to generate an \`Encryption aes_key\` and a \`Signature Token\`, and copy them.
 
-Generate \`Encryption aes_key\` and \`Signature Token\` for later use.
+![2025-09-18-15-05-10](https://docs-cdn.flashcat.cloud/images/png/0369b205a2fcf0f798267a4573e54996.png)
 
-**(Note: After generating aes_key and Token, please temporarily save the information elsewhere, as it will disappear after leaving the page)**
+Return to the Flashduty integration configuration page, fill in the corresponding \`Encryption aes_key\` and \`Signature Token\` in the form, and click the **Save** button.
 
-<img src="https://download.flashcat.cloud/flashduty/doc/en/ding/ding-4.png" alt="drawing" width="500"/>
+### 5. Configure Event Subscription
 
-## II. Add Dingtalk Integration
----
+Go to the Development Configuration → **Event Subscription** page.
 
-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.
+Configure the **Event Subscription Request URL** using the \`Event Subscription Request URL\` from the Flashduty integration details. **Save** after configuration.
 
-<img src="https://download.flashcat.cloud/flashduty/doc/en/ding/ding-5.png" alt="drawing" width="400"/>
+![2025-09-18-15-05-34](https://docs-cdn.flashcat.cloud/images/png/4f2f07c6bfd852b5c47ce2ae63559212.png)
 
-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.
+Below the **Save** button, select the three group session events: \`Group chat name is changed\`, \`Install the cool application in the group\`, and \`Uninstall the cool application in the group\`. Click **Save** after configuration.
 
-<img src="https://download.flashcat.cloud/flashduty/doc/en/ding/ding-6.png" alt="drawing" width="400"/>
+![2025-09-18-15-08-07](https://docs-cdn.flashcat.cloud/images/png/e4fadf912cdad71dbfcc8c3d678f3277.png)
 
-## III. Configure Dingtalk Application
----
+### 6. Add Application Capabilities
 
-### 1. Add Cool App, Web App, and Bot
-<img src="https://download.flashcat.cloud/flashduty/doc/en/ding/ding-7.png" alt="drawing" width="500"/>
+Create a Cool App. Go to Development Configuration → Add Application Capability → Cool App → **Cool App List** page, click the **Create Cool App** button, and select **Extend to group sessions**.
 
-1) Create Cool App: On the **Cool Apps - Cool App List** page, click **Create Cool App** button, select **Extend to Group Chat**
+Enter the **Edit Cool App** page and complete the following steps:
 
-<img src="https://download.flashcat.cloud/flashduty/doc/en/ding/ding-8.png" alt="drawing" width="500"/>
+1. Fill in the basic information. You can use the [Flashduty official icon](https://download.flashcat.cloud/flashcat_logo_circular.png) for the icon.
 
-2) Enter the **Edit Cool App** page, complete the following steps:
+![2025-09-18-15-11-03](https://docs-cdn.flashcat.cloud/images/png/d5191000378f4df25bb96bc1f19b0db2.png)
 
-2.1) First step, fill in basic information, you can use the [Flashduty official icon](https://download.flashcat.cloud/flashcat_logo_circular.png) as the icon.
+2. Configure the functional design. Select **Group Quick Access** and **Message Card** on the left. You can use the [Flashduty official icon](https://download.flashcat.cloud/flashcat_logo_circular.png) for the group quick access icon. For the desktop and mobile access addresses, please copy the **Cool App Web URL** from the integration details.
 
-<img src="https://download.flashcat.cloud/flashduty/doc/en/ding/ding-9.png" alt="drawing" width="500"/>
+![2025-09-18-15-13-08](https://docs-cdn.flashcat.cloud/images/png/88385f8c5aa382d13bc9f5c0d0b8b18f.png)
 
-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](https://download.flashcat.cloud/flashcat_logo_circular.png). Copy the **Cool App Web URL** from the integration details for both desktop and mobile access URLs.
+3. Skip the third step of functional development, proceed to the fourth step **Preview & Release**, click the **Release** button and confirm.
 
-<img src="https://download.flashcat.cloud/flashduty/doc/en/ding/ding-10.png" alt="drawing" width="500"/>
+### 7. Configure Bot and Message Push
 
-2.3) Skip the third step of function development, proceed to the fourth step **Preview and Release**, click the **Release** button and confirm.
+Go to the Application Capability → **Bot** page, enable the bot configuration, fill in the name and upload an icon, then click **Save**. You can use the [Flashduty official icon](https://download.flashcat.cloud/flashcat_logo_circular.png) for the icon.
 
-### 2. Configure Bot and Message Push
+![2025-09-18-15-17-17](https://docs-cdn.flashcat.cloud/images/png/62f4d4582baa0b446876e41e1a9d8eca.png)
 
-Enter the **Application Capabilities - Bot** page, enable bot configuration, fill in the name and upload an icon. You can use the [Flashduty official icon](https://download.flashcat.cloud/flashcat_logo_circular.png), then save.
+### 8. Configure Application URLs
 
-<img src="https://download.flashcat.cloud/flashduty/doc/en/ding/ding-11.png" alt="drawing" width="500"/>
+Go to the Application Capability → **Web Application** page.
 
-### 3. Configure Application URLs
+Configure the **Application Homepage URL** and **PC Homepage URL** with the \`Application Homepage URL\` and \`PC Homepage URL\` from the Flashduty integration details. Click **Save** when done.
 
-Enter the **Application Capabilities - Web Application** page
+![2025-09-18-15-20-13](https://docs-cdn.flashcat.cloud/images/png/9c430307d54f27eaedb009235540f6c5.png)
 
-1) Configure **Application Homepage URL** and **PC Homepage URL** with the content from the integration details' **Application Homepage URL** and **PC Homepage URL**.
+### 9. Apply for Application Permissions
 
-2) Click **Save** in the upper right corner.
+Go to the Development Configuration → **Permissions** page and apply for the following permissions for the group application created in the previous steps:
 
-<img src="https://download.flashcat.cloud/flashduty/doc/en/ding/ding-12.png" alt="drawing" width="500"/>
+- \`qyapi_chat_manage\`: Get group chat information
+- \`qyapi_robot_sendmsg\`: Send messages to group chats or individuals
 
-### 4. Configure Event Subscription
+![2025-09-18-15-20-36](https://docs-cdn.flashcat.cloud/images/png/4417440194002a011e2feca5fa5c9469.png)
 
-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**.
+## II. Configure War Room
 
-<img src="https://download.flashcat.cloud/flashduty/doc/en/ding/ding-13.png" alt="drawing" width="500"/>
+> If you do not need to configure the War Room feature, you can skip this step and proceed directly to [**Application Release and Usage**](#publish).
 
-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**.
+<span id="war-room-scope"></span>
 
-<img src="https://download.flashcat.cloud/flashduty/doc/en/ding/ding-14.png" alt="drawing" width="500"/>
+### 1. Apply for Application Permissions
 
-### 5. Apply for Application Permissions
+Go to the Development Configuration → **Permissions** page and apply for the following permissions for the group application created in the previous steps:
 
-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.
+- \`qyapi_chat_read\`: Get group chat information
+- \`qyapi_chat_base_read\`: Get group chat information
+- \`qyapi_get_member_by_mobile\`: Allows the current application to get Dingtalk user information based on mobile numbers to invite users to join group chats
 
-<img src="https://download.flashcat.cloud/flashduty/doc/en/ding/ding-15.png" alt="drawing" width="500"/>
+![2025-09-18-15-21-28](https://docs-cdn.flashcat.cloud/images/png/39142395390ce09726e3a95991549116.png)
 
-## IV. Application Release and Usage
----
+### 2. Configure Group Template
+
+Go to Open Capability → **Scene Group** from the top menu bar of the Dingtalk Open Platform.
+
+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](https://download.flashcat.cloud/flashcat_logo_circular.png) |
+   | Introduction | Flashduty |
+   | Message Preview Image | [Flashduty official icon](https://download.flashcat.cloud/flashcat_logo_circular.png) |
+   | 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.
+
+   ![2025-09-18-15-22-05](https://docs-cdn.flashcat.cloud/images/png/75e853ae6c420d69916e17f5d8922945.png)
+
+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.
 
-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)
+   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.
 
-<img src="https://download.flashcat.cloud/flashduty/doc/en/ding/ding-16.png" alt="drawing" width="500"/>
-<img src="https://download.flashcat.cloud/flashduty/doc/en/ding/ding-17.png" alt="drawing" width="500"/>
+   **Example Configuration**:
 
-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.
+   | **Configuration Item** | **Value** |
+   | ---------- | --------------------------------------------------------------------------------- |
+   | Template Name | Flashduty War Room |
+   | Icon | [Flashduty official icon](https://download.flashcat.cloud/flashcat_logo_circular.png) |
+   | 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](https://download.flashcat.cloud/flashcat_logo_circular.png) |
 
-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.
+   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**.
+
+   ![2025-09-18-15-22-35](https://docs-cdn.flashcat.cloud/images/png/9292a8418a96fcb3fee1d424a41d33a2.png)
+   ![2025-09-18-15-23-06](https://docs-cdn.flashcat.cloud/images/png/c76433b0962fb0f0531b4f56b60ce903.png)
+
+   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**.
+
+   ![2025-09-18-15-23-46](https://docs-cdn.flashcat.cloud/images/png/315acf0b5951100781f96cd4d854d0c6.png)
+
+   Return to the Flashduty integration configuration page, fill in the corresponding \`Template ID\` and \`Bot ID\` in the form, and click the **Save** button.
+
+<span id="publish"></span>
+
+## III. Application Release and Usage
 
-## 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
+After completing the above steps, go to Application Release → **Version Management and Release**, create a new version, and publish it.
 
-2. **Message card buttons are ineffective or show errors?**
+> To ensure that everyone can use the application, you need to adjust the **Visible Scope** of the application to all employees before publishing.
 
-    - 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
+![2025-09-18-16-08-17](https://docs-cdn.flashcat.cloud/images/png/86df5b6148cf1264745d957bd2d43fcf.png)
 
-3. **Escalation rule Dingtalk group chat list is empty?**
+After the application is published, you can access it via the **mobile client** or **PC client**. The first time you access it, you need to log in and associate your Dingtalk and Flashduty accounts. Subsequent uses will be login-free.
 
-    - 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
+- **Mobile Client**: Access the web application through Dingtalk → Workbench → Search for application name → **Open Application**.
+- **PC Client**: Access the web application through Dingtalk → Workbench → Search for application name → **Open Application**.
 
-<img src="https://download.flashcat.cloud/flashduty/doc/en/dingtalk-install-1.png" alt="drawing" width="500"/>
+## IV. FAQ
 
-<img src="https://download.flashcat.cloud/flashduty/doc/en/dingtalk-install-2.png" alt="drawing" width="500"/>
+---
+
+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**](https://console.flashcat.cloud/wallet).
+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.
+
+      ![2025-09-18-15-34-37](https://docs-cdn.flashcat.cloud/images/png/7f1e931df0ae740a37ce6615ac3b18ba.png)
+      ![2025-09-18-15-35-44](https://docs-cdn.flashcat.cloud/images/png/367dfd391bf4d57c22088d20a4844e33.png)
+
+   - 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. **Dingtalk Custom Application API Call Limits:** [Dingtalk Documentation](https://open.dingtalk.com/document/orgapp/descriptions-about-adjusting-limit-and-frequency-of-api-calls?spm=ding_open_doc.document.0.0.6f6b21d9WtkxJI)
+4. **Why is the War Room feature not working as expected?**
+   - Please double-check if you have configured the [required permissions](#war-room-scope) for the application's War Room feature.
+   - Please refer to the **FAQ** section of the Flashduty [War Room Introduction](https://docs.flashcat.cloud/en/flashduty/war-room?nav=01JCQ7A4N4WRWNXW8EWEHXCMF5) document.
 
-|     Dingtalk Version     | Total Calls/Month | QPS| Refresh Time  |                       
-| :----------: | :--: | :----: | :----:|
-|Standard|10,000|20|1st of each month|
-|Professional|500,000|40|1st of each month|
-|Enterprise|5,500,000|60|1st of each month|
+5. **Dingtalk Custom Application API Call Limits**
 
-**Note:** Messages cannot be pushed normally after exceeding limits, please use notification channels reasonably
-`,ne=`---
+   | **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](https://open.dingtalk.com/document/orgapp/descriptions-about-adjusting-limit-and-frequency-of-api-calls?spm=ding_open_doc.document.0.0.6f6b21d9WtkxJI).`,te=`---
 title: "WeCom Integration"
-description: "Integrate WeCom third-party application to receive and respond to alerts within WeCom"
+description: "By integrating a WeCom application, you can receive and respond to alerts within WeCom."
 date: "2025-05-19T10:00:00+08:00"
-url: "https://docs.flashcat.cloud/en/flashduty/wecom-integration-guide"
+url: "https://docs.flashcat.cloud/en/flashduty/wecom-integration-guide?nav=01JCQ7A4N4WRWNXW8EWEHXCMF5"
 ---
 
-Integrate WeCom third-party application to receive and respond to alerts within WeCom.
+By integrating a WeCom application, you can receive and respond to alerts within WeCom.
 
-<!-- >
-## Video Guide
----
-<Video src="https://download.flashcat.cloud/flashduty/video/wechat.mp4"></Video>
--->
+This document supports both [integrating third-party applications](#third-party) and [integrating custom enterprise applications](#self).
 
-## I. Install the Application
----
 
-1. Visit [WeCom Admin Console](https://work.weixin.qq.com/wework_admin/frame#apps) - \`App Management\` - \`Third-party\`, and select Add Third-party App
+> You only need to configure one of the two methods: **Integrate third-party application** or **Integrate custom application**.
 
-<img src="https://download.flashcat.cloud/flashduty/doc/en/wecom/wecom-1.png" alt="drawing" width="500"/>
+<span id="third-party"></span>
 
-2. Search for \`flashduty\` in the search bar, locate the app, and click the \`Add\` button
+## 1. Integrate third-party application
 
-<img src="https://download.flashcat.cloud/flashduty/doc/en/wecom/wecom-2.png" alt="drawing" width="500"/>
+---
 
-3. Modify the app's \`Visibility\`, recommend setting it to all members or specific departments to avoid modifying settings when adding new members. Click \`Agree and Add\` to complete installation
+> As a WeCom service provider, Flashduty offers a long-term free version of the Flashduty application. This application requires WeCom API permissions to function (passwordless login + message sending).
+>
+> This license currently supports **up to 60 days** free of charge. After exceeding this usage period, Flashduty needs to purchase a WeCom license for you to continue using it.
 
-<img src="https://download.flashcat.cloud/flashduty/doc/en/wecom/wecom-3.png" alt="drawing" width="500"/>
+1. Visit [WeCom Admin Console](https://work.weixin.qq.com/wework_admin/frame#apps), go to Application Management → **Applications** page, and click **Add Third-party Application**.
 
-4. Visit [WeCom Admin Console](https://work.weixin.qq.com/wework_admin/frame#apps) - \`My Enterprise\` page, copy the \`Corp ID\` and paste it into the integration configuration as \`Corp ID\`, click save to complete the setup
+   ![2025-09-18-12-59-55](https://docs-cdn.flashcat.cloud/images/png/783157a331b4b1246c1941dc53874d27.png)
 
-<img src="https://download.flashcat.cloud/flashduty/doc/en/wecom/wecom-4.png" alt="drawing" width="500"/>
+2. Enter \`Flashduty\` in the search bar, and click the **Add** button after finding the application.
 
-5. **Please Note: As a WeCom service provider, Flashduty offers a long-term free version of the \`FlashDuty\` application. The app requires WeCom API access license for functionality (passwordless login + messaging). This license is free for up to \`60 days\`, after which we must purchase a WeCom license for continued use.**
+   ![2025-09-18-13-00-54](https://docs-cdn.flashcat.cloud/images/png/2b36bb53b8a6de1738a626ad00c5fd6e.png)
 
-## II. FAQ
----
+3. Modify the application **visibility range**. It is recommended to select all employees or specific department nodes to avoid needing to modify when new enterprise members are added. Then click **Agree to the above authorization and add** to complete the installation.
 
-1. **Clicking the integration save button returns \`authorize app first\` error?**
+   ![2025-09-18-13-14-47](https://docs-cdn.flashcat.cloud/images/png/4e1bd7ecaedc799ca0a2889f59cf8c00.png)
 
-   - Check if you've completed the app installation steps, such as whether you can see the \`FlashDuty\` app in your workspace
-   - Verify if you've correctly configured the \`Corp ID\`
+4. Visit [WeCom Admin Console](https://work.weixin.qq.com/wework_admin/frame#apps), go to **My Enterprise** page, and obtain the \`Enterprise ID\`.
 
-2. **How to complete account linking? Or message sending shows \`App Not Linked\`?**
+   ![2025-09-18-13-05-43](https://docs-cdn.flashcat.cloud/images/png/11887f4892a2ed05ee13efdca936845f.png)
 
-   - Log into WeCom client (desktop or mobile), go to \`Workspace\`, find and enter the \`FlashDuty\` app
-   - First-time access requires login, choose member account - password or SSO, successful login completes account linking between \`Flashduty\` and \`WeCom\`
-   - Subsequent access will be passwordless
+5. Return to the Flashduty integration configuration page, fill in the \`Enterprise ID\` obtained in the previous step, and click **Save** to complete the integration.
 
-3. **How to send incident notifications?**
+<span id="self"></span>
 
-   - Must complete account linking as per Question 1 before sending notifications
-   - Go to channel details page - escalation rule, select WeCom integration in personal channels to complete notification setup
-   - Supports customizing WeCom notification content through template management page. Note: **Custom area supports maximum 8 lines**, excess content will be truncated by WeCom
+## 2. Integrate custom enterprise application
 
-<img src="https://download.flashcat.cloud/flashduty/doc/en/wecom/wecom-5.png" alt="drawing" width="500"/>
+---
 
-4. **How to handle alerts in WeCom?**
+1. Visit [WeCom Admin Console](https://work.weixin.qq.com/wework_admin/frame#apps), go to Application Management → **Applications** page, and click **Create Application**.
 
-   - Click the card message to directly access alert details
-   - Click \`Start Processing\` to set alert status to \`In Progress\`
-   - Click \`Close Directly\` to set alert status to \`Closed\`
-   - Click \`Snooze 2h\` to snooze the alert for 2 hours, click \`...\` in top-right corner for more snooze options
+   ![2025-09-18-13-06-26](https://docs-cdn.flashcat.cloud/images/png/166b4c18de5677d1fd686a5953dda6a7.png)
 
-5. **Why is there a \`Refresh Status\` button on card messages?**
+2. Configure **Application Logo**, **Application Name**, and **Application Visibility Range**.
 
-   - WeCom limits card updates to once per 72 hours after interaction. Each button operation counts as an interaction
-   - Flashduty requests card content updates when alert status changes
-   - When alert status changes frequently, updates might fail due to update limit, use refresh button for one additional update opportunity
+   ![2025-09-18-13-07-17](https://docs-cdn.flashcat.cloud/images/png/c0373856679ae5a37d13dd36562f0c61.png)
 
-6. **How to open card messages in \`System Default Browser\` on Mac desktop?**
+3. Return to the Flashduty integration configuration page and select whether WeCom is a \`non-private deployment version\` based on your actual situation.
 
-   - Mac desktop client defaults to internal browser for links
-   - Try keyboard shortcut \`ctrl\` + \`command\` + \`shift\` + \`d\` to enable debug mode, then select \`Debug - Browser & WebView Related - Open in System Browser\` to change link opening behavior. Use the same shortcut to exit debug mode and retain settings
+   If your WeCom is a private deployment version, you need to fill in the \`Endpoint\` in the configuration page. This address needs to be accessible by the Flashduty service. You may consider setting up **whitelist authorization** for it.
 
-7. **Incident notification fails with \`WeCom License Not Activated\`?**
+4. Visit [WeCom Admin Console](https://work.weixin.qq.com/wework_admin/frame#apps), go to **My Enterprise** page, obtain the \`Enterprise ID\`, and fill it in the Flashduty integration configuration page.
 
-   - Contact Flashduty customer service or dedicated support for license purchase and activation
-`,te=`---
-title: "Slack Integration"
-description: "Integrate with Slack to receive and respond to alerts within Slack"
-date: "2025-05-19T10:00:00+08:00"
-url: "https://docs.flashcat.cloud/en/flashduty/slack-integration-guide"
----
+5. Return to [WeCom Admin Console](https://work.weixin.qq.com/wework_admin/frame#apps), go to **Application Management** page, click on the application you created to enter the details page. Obtain the \`AgentId\` from the page and fill it in the Flashduty integration configuration page.
 
-Integrate with Slack to receive and respond to alerts within Slack.
+6. On the application details page, obtain the \`Secret\` and fill it in the Flashduty integration configuration page.
 
-## I. Install the App
----
+7. On the application details page, go to **Web Authorization and JS-SDK** page, click **Set Trusted Domain**, and configure **Callback domain for application OAuth 2.0 web authorization** as required.
 
-1. Go to FlashDuty \`Integration Center\` - \`Instant Messaging\` - \`Slack\` - \`Add\`
+   > The trusted domain needs to point to Flashduty's backend address \`{api_host}\` (can be achieved through CNAME or proxy forwarding).
+   >
+   > For trusted domain requirements, see the official WeCom documentation [《Internal Development Domain Configuration Guide》](https://open.work.weixin.qq.com/wwopen/common/readDocument/40754).
 
-2. You will be redirected to Slack. Select your \`Workspace\` in the top right corner, then click \`Allow\`
+   ![2025-09-18-13-08-43](https://docs-cdn.flashcat.cloud/images/png/8509e75449c933c3f750c93ce621e641.png)
 
-<img src="https://download.flashcat.cloud/flashduty/integration/slack/slack_app_options.png" alt="drawing" width="400"/>
+   Return to the Flashduty integration configuration page, fill in this domain, and complete the verification.
 
-3. Enter the integration name and click \`Save\`
+8. On the application details page, go to **Receive Messages** page and **Set API Reception**. Click **Random Generation** for both \`Token\` and \`EncodingAESKey\`, then copy and save the generated values.
 
+   ![2025-09-18-13-10-03](https://docs-cdn.flashcat.cloud/images/png/ced9137a2fe74afa34d118ce279579e2.png)
 
-## II. Common Issues
----
+   Return to the Flashduty integration configuration page, fill in the saved \`Token\` and \`EncodingAESKey\`, and click **Save** to complete the integration.
 
-1. **Cannot find desired private channel in escalation rule channel list**
-   - Adding the app to a channel requires Step 1 \`Install App\` to complete without errors
-   - In the Slack channel, run \`/invite @FlashDuty\`. A message saying \`has joined\` or \`has been added by xx to xxx\` indicates successful addition
+9. Copy the \`Callback Address\` from the Flashduty integration details page, return to the **Receive Messages** page in WeCom. In the **API Reception** settings, fill in the \`Callback Address\` and the \`Token\` and \`EncodingAESKey\` saved in the previous step, then click **Save**.
 
-2. **Cannot find desired public channel in escalation rule channel list**
-   - Add the app authorizer to the public channel
-   - Or follow \`Common Issue 1\` to add the app to the channel
+   ![2025-09-18-13-10-56](https://docs-cdn.flashcat.cloud/images/png/9a1bee272010ceaa38d2f39025215379.png)
 
-3. **Error when clicking Allow button in Step 2 of installation**
-   - Try again, as there might be communication issues between the server and Slack causing authorization problems. Return to the add integration page and retry
-   - If the error persists, contact customer support
+10. Company's Trusted IP : 47.94.95.118; 123.56.8.183; 47.94.193.81; 1.13.19.96
 
-4. **Error when clicking Save button in Step 3 of installation**
-   - Try again, as there might be communication issues when FlashDuty attempts to obtain the permanent authorization code. Return to the add integration page and retry
-   - If the error persists, contact customer support
+   ![2025-09-19-11-06-36](https://docs-cdn.flashcat.cloud/images/png/0aa3c0129f7c99785ea77d088cd65774.png)
 
-5. **Slack App shows not_authed error**
-   - Try again, as there might be issues with Slack service
-   - If the error persists, contact customer support
+## 3. Configure war room
 
-6. **Slack App shows Operation timed out error**
-   - Try again, as there might be communication timeout issues between the server and Slack
-   - If the error persists, contact customer support
+---
 
-7. **Slack App shows This app responded with Status Code 500 error**
-   - Try again, as there might be server errors, such as the integration being disabled
-   - If the error persists, contact customer support
+> The war room feature is only supported when **custom enterprise application** mode is enabled.
 
-8. **Slack App shows Other questions error**
-   - Try again, as this might be an unrecorded issue
-   - If the error persists, contact customer support`,ae=`---
-title: "Microsoft Teams Integration"
-description: "Integrate Microsoft Teams as a third-party application to receive and respond to alerts within Microsoft Teams"
+After completing the previous steps, in the **Enhanced Features** module of the Flashduty integration configuration page, check **Enable War Room** to enable this feature without additional configuration.
+
+## 4. FAQ
+
+---
+
+1. **After clicking the integration save button, the system reports \`authorize app first\`?**
+   - Please check if you have completed the application installation steps. For example, can you see the Flashduty application in the WeCom workplace?
+   - Please check if you have correctly configured the \`Corp ID\`.
+2. **How to complete account linking or message sending prompts \`app not linked\`?**
+   - Log in to the WeCom client (both desktop and mobile are acceptable), go to **Workplace**, find and open the Flashduty application.
+   - The first time you enter the application, you need to log in. Select your member account and log in successfully through password or single sign-on to complete the linking of your Flashduty account and WeCom account.
+   - Subsequent entries to the application will automatically log in without a password.
+3. **How to send incident notifications?**
+   - Before sending notifications, you must complete account linking as described in the previous question.
+   - Enter the specified channel, navigate to \`Escalation Rules\` → **Personal Channels**, and select \`WeCom\` as the notification method.
+   - Flashduty supports customizing WeCom notification content. You can go to the **Template Management** page to set custom templates. **The custom area can display up to 8 lines**, and excess content will be truncated by WeCom.
+  ![2025-09-18-12-02-26](https://docs-cdn.flashcat.cloud/images/png/9cb6a325b4b16875fec3e0c5054be25b.png)
+4. **How to handle alerts within WeCom?**
+   - Click on the card message to directly enter the alert details page.
+   - Click **Start Processing** to directly set the alert to \`Processing\` status.
+   - Click **Close Directly** to directly set the alert to \`Closed\` status.
+   - Click **Snooze for 2 hours** to directly snooze the alert for 2 hours. If you want to snooze for longer, click the \`...\` in the upper right corner of the card to see more snooze options.
+5. **Why does the card message provide a \`Status Refresh\` button?**
+   - According to WeCom's restrictions, after one card interaction, it can only be updated once within 72 hours. Each button operation is considered an interaction.
+   - When the alert status changes, Flashduty will request to update the card content.
+   - When the alert status changes frequently, the card may not be updated in real-time due to exceeding the update limit. At this time, you can click the **Refresh** button to manually get a chance to update the card status.
+6. **On Mac desktop, how to set clicking card messages to open with the \`system default browser\`?**
+   - Mac desktop uses WeCom's built-in browser to open links by default.
+   - You can try using the shortcut \`ctrl\` + \`command\` + \`shift\` + \`d\` to enable debug mode, then select **Debug** → **Browser, WebView Related** → **Open Web Page with System Browser** to change how links are opened. Use the same shortcut to close debug mode, and the settings will be retained.
+7. **Incident notification failed with prompt \`WeCom license not activated\`?**
+   - Please contact Flashduty customer service or your dedicated technical support to purchase and activate the license for you.
+8. **Why is the war room feature not working as expected?**
+   - Please refer to the **FAQ** section of the Flashduty [War Room Introduction](https://docs.flashcat.cloud/en/flashduty/war-room?nav=01JCQ7A4N4WRWNXW8EWEHXCMF5).`,ae=`---
+title: "Slack Integration"
+description: "By integrating the Slack third-party application, you can receive and respond to alerts within Slack."
 date: "2025-05-19T10:00:00+08:00"
-url: "https://docs.flashcat.cloud/en/flashduty/microsoft-teams-integration-guide"
+url: "https://docs.flashcat.cloud/en/flashduty/slack-integration-guide?nav=01JCQ7A4N4WRWNXW8EWEHXCMF5"
 ---
 
-Integrate Microsoft Teams as a third-party application to receive and respond to alerts within Microsoft Teams.
+By integrating the Slack third-party application, you can receive and respond to alerts within Slack.
 
-## I. Install/Update Application
----
+<span id="install-app"></span>
 
-Microsoft Teams integration is currently in Beta. Before associating, you need to complete the following operations:
+## 1. Install application
 
-::: caution
-These steps must be completed by a Microsoft Teams administrator
-:::
+---
 
-### 1. Download Application
-Download [FlashDutyBot-v1.0.3.zip](https://flashduty-docs.oss-cn-beijing.aliyuncs.com/docs/FlashdutyBot-v1.0.3.zip) to your local machine
+1. Visit Flashduty Integration Center → IM → **Slack**, and click **Add**.
+2. On the redirected Slack page, select **Workspace** in the upper right corner, then click **Allow**.
+   ![2025-09-18-15-58-05](https://docs-cdn.flashcat.cloud/images/png/c241bc7f7a657bd552bfe3b03bdb2e3b.png)
+3. Enter the data source name and click **Save**.
 
-### 2. Install Application
-Go to **Microsoft Teams, navigate to [+Apps] - [Manage your apps] - [Upload an app] - [Upload an app to your org's app catalog]** and upload the FlashDutyBot.zip package
+## 2. Configure war room
 
-![](https://fcpub-1301667576.cos.ap-nanjing.myqcloud.com/flashduty/integration/microsoft-teams/upload-app.png)
+After completing the previous steps, in the **Enhanced Features** module of the Flashduty integration configuration page, check **Enable War Room** to enable this feature without additional configuration.
 
-#### Configure Application Visibility
-Go to [Microsoft Teams Admin Center](https://admin.teams.microsoft.com/policies/manage-apps), find the FlashDuty application, and adjust the application visibility to everyone (or your custom scope)
+## 3. FAQ
 
-::: tip
-If the application status shows [Blocked], please wait a moment and refresh the page or modify it manually
-:::
-![](https://flashduty-docs.oss-cn-beijing.aliyuncs.com/imges/png/install-bot-2.png)
+---
 
-#### Check if Installation is Successful
-Wait a few minutes, and organization members can find this application integration under [+Apps] - [Built for your org]
+1. **The private channel I want is not in the group chat list of escalation rules?**
+   - Ensure the [**Install Application**](#install-app) step has been completed successfully without errors.
+   - Enter the relevant Slack channel and execute the \`/invite @Flashduty\` command. When you see the prompt \`has joined\` or \`has been added by xxx to xxx\`, it means the addition was successful.
+2. **The public channel I want is not in the group chat list of escalation rules?**
+   - Add the application authorizer to the public channel.
+   - Refer to the method in **Question 1** to add the application to the channel.
+3. **Error after clicking the \`Allow\` button in installation step 2?**
+   - Please retry. This may be due to abnormal communication between the server and Slack causing authorization failure. Please return to the add data source page and try again.
+   - If the error persists after retrying, please contact customer service.
+4. **Error after clicking the \`Save\` button in installation step 3?**
+   - Please retry. This may be due to abnormal communication between the Flashduty server and Slack when obtaining the permanent authorization code. Please return to the add data source page and try again.
+   - If the error persists after retrying, please contact customer service.
+5. **Slack App prompts \`not_authed\` error?**
+   - Please retry, this may be a temporary issue with Slack service.
+   - If the error persists after retrying, please contact customer service.
+6. **Slack App prompts \`Operation timed out\` error?**
+   - Please retry. This may be due to communication timeout between the server and Slack.
+   - If the error persists after retrying, please contact customer service.
+7. **Slack App prompts \`This app responded with Status Code 500\` error?**
+   - Please retry. This may be an error on the Flashduty server side (for example, the data source is closed).
+   - If the error persists after retrying, please contact customer service.
+8. **Slack App prompts other unknown errors?**
+   - Please retry.
+   - If the error persists after retrying, please contact customer service to record and resolve new issues.
+9. **Why is the war room feature not working as expected?**
+   - For previously authorized Slack IM integrations, you need to manually reauthorize Slack in the Flashduty integration configuration page to grant the application the additional permissions required for the war room feature.
+   - Please refer to the **FAQ** section of the Flashduty [War Room Introduction](https://docs.flashcat.cloud/en/flashduty/war-room?nav=01JCQ7A4N4WRWNXW8EWEHXCMF5).`,ie=`---
+title: "Microsoft Teams Integration"
+description: "By integrating the Microsoft Teams third-party application, you can receive and respond to alerts within Microsoft Teams."
+date: "2025-05-19T10:00:00+08:00"
+url: "https://docs.flashcat.cloud/en/flashduty/microsoft-teams-integration-guide?nav=01JCQ7A4N4WRWNXW8EWEHXCMF5"
+---
+By integrating the Microsoft Teams third-party application, you can receive and respond to alerts within Microsoft Teams.
+
+## 1. Install and update application
+---
 
-![](https://flashduty-docs.oss-cn-beijing.aliyuncs.com/imges/png/find-bot.png)
+The Microsoft Teams integration is currently in Beta. You need to complete the following operations before linking.
 
-### 3. Update Application
 ::: caution
-If you have installed an application version lower than 1.0.3, please follow the steps below to update
+This step needs to be completed by a Microsoft Teams administrator.
 :::
 
-Go to [Microsoft Teams Admin Center](https://admin.teams.microsoft.com/policies/manage-apps), find and enter the FlashDuty application details page
-
-![update-bot-1](https://flashduty-docs.oss-cn-beijing.aliyuncs.com/imges/png/update-bot-1.png)
+### 1. Download application
+Download [FlashDutyBot-v1.0.3.zip](https://flashduty-docs.oss-cn-beijing.aliyuncs.com/docs/FlashdutyBot-v1.0.3.zip) to your local device.
 
-Upload the new version FlashdutyBot.zip
+### 2. Install application
+In Microsoft Teams, navigate to +Apps → Manage your apps → Upload an app → **Upload an app to your org's app catalog**, then upload the application package \`FlashDutyBot.zip\`.
 
-![update-bot-2](https://flashduty-docs.oss-cn-beijing.aliyuncs.com/imges/png/update-bot-2.png)
+![2025-09-18-13-48-04](https://docs-cdn.flashcat.cloud/images/png/bfa4afaf489c3582e858cad99eb76ae5.png)
 
-Wait for the application version to update in the client (may take several tens of minutes)
+#### Configure application visibility
+Go to [Microsoft Teams Admin Center](https://admin.teams.microsoft.com/policies/manage-apps), find the Flashduty application, and adjust the application visibility to everyone or your specified scope.
 
-![update-bot-3](https://flashduty-docs.oss-cn-beijing.aliyuncs.com/imges/png/update-bot-3.png)
-
-## II. Associate Teams
+::: tip
+If the application status is "Blocked", please wait a moment and refresh the page or manually modify it.
+:::
+![2025-09-18-13-49-11](https://docs-cdn.flashcat.cloud/images/png/ea961e7965a2d0c69f8575c4252fb333.png)
 
-### 1. Add FlashDuty Application to Target Team
 
-#### 1.1 Find the FlashDuty Application
-If there is no application, please contact your Microsoft Teams organization administrator
+#### Check if successfully added
+After waiting a few minutes, organization members can find this application in +Apps → **Built for your org**.
 
-![link-bot](https://flashduty-docs.oss-cn-beijing.aliyuncs.com/imges/png/link-bot-1.png)
+![2025-09-18-17-05-37](https://docs-cdn.flashcat.cloud/images/png/f7827638d1877005ca674cbbd2aaa4a3.png)
 
-#### 1.2 Add to Target Team
+### 3. Update application
 ::: caution
-Note: This step must select the General Channel of the target Team, otherwise incidents cannot be sent to the Team
+If your installed application version is lower than 1.0.3, please follow this process to update.
 :::
 
-![link-bot-team-1](https://flashduty-docs.oss-cn-beijing.aliyuncs.com/imges/png/link-bot-team-1.png)
+1. Go to [Microsoft Teams Admin Center](https://admin.teams.microsoft.com/policies/manage-apps), find and enter the Flashduty application details page.
+![2025-09-18-13-50-41](https://docs-cdn.flashcat.cloud/images/png/32a62878f9e765cd8b2eb79ceb00bb02.png)
+
+2. Upload the new version \`FlashdutyBot.zip\`.
+![2025-09-18-13-51-56](https://docs-cdn.flashcat.cloud/images/png/f18ac3504516750c31f8357e65f6d680.png)
 
-### 2. Send Association Command
-@FlashDuty and send linkTeam {ID} to the added Team, then click Associate Now
+3. Wait for the application version to update in the client (may take tens of minutes).
+![2025-09-18-13-52-56](https://docs-cdn.flashcat.cloud/images/png/290f609c30055031ab0ccf6636cdbb01.png)
 
-![link-bot-team-2](https://flashduty-docs.oss-cn-beijing.aliyuncs.com/imges/png/link-bot-team-2.png)
+## 2. Link Team
+---
+### 1. Add Flashduty application
+1. Find the Flashduty application in the app marketplace.
+> If there is no application, please contact your Microsoft Teams organization administrator.
 
-## III. Associate Chats
+![2025-09-18-17-06-34](https://docs-cdn.flashcat.cloud/images/png/0905e663241ce448a1381ef8c08aa777.png)
 
-### 1. Add FlashDuty Application to Target Chat
+2. Add the application to the target Team.
+::: caution
+This step must select the General Channel of the target Team, otherwise incidents cannot be sent to the Team.
+:::
 
-#### 1.1 Find the FlashDuty Application
-If there is no application, please contact your Microsoft Teams organization administrator
+![2025-09-18-17-11-29](https://docs-cdn.flashcat.cloud/images/png/01fa86b63d01d2735aa6c4a53efb3c69.png)
 
-![link-bot](https://flashduty-docs.oss-cn-beijing.aliyuncs.com/imges/png/link-bot-1.png)
+### 2. Send link command
+In the Team, @Flashduty and send the command \`linkTeam {ID}\`, then click **Link Now**.
 
-#### 1.2 Add to Target Chat
+![2025-09-18-13-55-05](https://docs-cdn.flashcat.cloud/images/png/3192b5481b0595fcb58e5cc43abad125.png)
 
-![link-bot-chat-1](https://flashduty-docs.oss-cn-beijing.aliyuncs.com/imges/png/link-bot-chat-1.png)
+## 3. Link Chat
+---
+### 1. Add Flashduty application
+1. Find the Flashduty application in the app marketplace.
+> If there is no application, please contact your Microsoft Teams organization administrator.
 
-### 2. Send Association Command
-@FlashDuty and send linkChat {ID} {ChatName} to the added Team, then click Associate Now
+![2025-09-18-17-06-34](https://docs-cdn.flashcat.cloud/images/png/0905e663241ce448a1381ef8c08aa777.png)
 
-![link-bot-chat-2](https://flashduty-docs.oss-cn-beijing.aliyuncs.com/imges/png/link-bot-chat-2.png)
+2. Add the application to the target Chat.
 
-## IV. Associate Users
+![2025-09-18-17-14-23](https://docs-cdn.flashcat.cloud/images/png/6e56d7de341737fe495e5ff18eb1af34.png)
 
-### 1. Add FlashDuty Application
+### 2. Send link command
+In the Chat, @Flashduty and send the command \`linkChat {ID} {ChatName}\`, then click **Link Now**.
 
-#### 1.1 Find the FlashDuty Application
-If there is no application, please contact your Microsoft Teams organization administrator
+![2025-09-18-13-56-17](https://docs-cdn.flashcat.cloud/images/png/d0beee141db63714ccecb095affee79b.png)
 
-![link-bot](https://flashduty-docs.oss-cn-beijing.aliyuncs.com/imges/png/link-bot-1.png)
+## 4. Link user
+---
+### 1. Add Flashduty application
+1. Find the Flashduty application in the app marketplace.
+> If there is no application, please contact your Microsoft Teams organization administrator.
 
-#### 1.2 Click to Open Application
-![link-bot-user-1](https://flashduty-docs.oss-cn-beijing.aliyuncs.com/imges/png/link-bot-user-1.png)
+![2025-09-18-17-06-34](https://docs-cdn.flashcat.cloud/images/png/0905e663241ce448a1381ef8c08aa777.png)
 
-### 2. Send Association Command
-Copy the command: linkUser {} and send it to the chat, then click Associate Now
+2. Click **Open Application**.
 
-![link-bot-user-2](https://flashduty-docs.oss-cn-beijing.aliyuncs.com/imges/png/link-bot-user-2.png)
+![2025-09-18-13-56-55](https://docs-cdn.flashcat.cloud/images/png/2e6862103d718a913d2b3c449cbf2366.png)
 
-## Common Issues
-<details>
-<summary>Team or individual not receiving messages</summary>
-Please check if the teams and users are successfully associated in Integration Center => Instant Messaging => Microsoft Teams
-</details>
+### 2. Send link command
+Copy and send the command \`linkUser {}\` to the chat, then click **Link Now**.
 
-<details>
-<summary>How to view associated teams and users</summary>
-Please check in Integration Center => Instant Messaging => Microsoft Teams under Associated Teams and Associated Users
-</details>
+![2025-09-18-13-57-13](https://docs-cdn.flashcat.cloud/images/png/671ae7883bbba839419e539762db99de.png)
 
-<details>
-<summary>How to cancel associated teams and users</summary>
-Currently not supported
-</details>
+## 5. FAQ
+---
 
-`,ie=`Configure alert webhooks to receive HTTP callbacks at your specified URL when alerts have specific actions (such as triggering or closing). The callback content includes the latest key information about the alert, allowing integration with your custom tools.
+1. **Team or individual cannot receive messages?**
+   - Please go to Integration Center → IM → **Microsoft Teams** to check if teams and users have been successfully linked.
+2. **How to view linked teams and users?**
+   - Please go to Integration Center → IM → **Microsoft Teams** to view in **Linked Teams** and **Linked Users**.
+3. **How to cancel linked teams and users?**
+   - This feature is not currently supported.`,oe=`Configure alert webhooks to receive HTTP callbacks at your specified URL when alerts have specific actions (such as triggering or closing). The callback content includes the latest key information about the alert, allowing integration with your custom tools.
 
 <span id="EventTypes"></span>
 
@@ -6283,7 +6478,7 @@ curl -X POST 'https://example.com/alert/webhook?a=a' \\
 4. **Trusted IP whitelist for push sources?**
    - {ip_whitelist}
    - May be updated in the future, please check periodically
-`,oe=`Configure incident webhooks to receive HTTP callbacks at your specified URL when incidents have specific actions (such as triggering or closing). The callback content includes the latest key information about the incident, allowing integration with your custom tools.
+`,se=`Configure incident webhooks to receive HTTP callbacks at your specified URL when incidents have specific actions (such as triggering or closing). The callback content includes the latest key information about the incident, allowing integration with your custom tools.
 
 <span id="EventTypes"></span>
 
@@ -6490,7 +6685,7 @@ curl -X POST 'https://example.com/incident/webhook?a=a' \\
 
 4. **Trusted IP whitelist for push sources?**
    - {ip_whitelist}
-   - May be updated in the future, please check periodically`,se=`Custom incident actions allow you to quickly invoke external interfaces during incident troubleshooting for incident self-healing, information enrichment, and other custom operations.
+   - May be updated in the future, please check periodically`,re=`Custom incident actions allow you to quickly invoke external interfaces during incident troubleshooting for incident self-healing, information enrichment, and other custom operations.
 
 ## I. Creating Actions
 
@@ -6737,7 +6932,7 @@ When an incident occurs and is confirmed to be caused by a change, directly trig
 
 ### Update Status Page
 
-When an incident is confirmed to affect online services, trigger external status page updates to prompt`,re=`---
+When an incident is confirmed to affect online services, trigger external status page updates to prompt`,le=`---
 title: "Jira Sync"
 description: "Sync incidents with Jira issues through Jira Sync Webhook."
 date: "2025-05-19T10:00:00+08:00"
@@ -6819,7 +7014,7 @@ In the Integration Center, select **Webhook**, choose **Jira Sync** integration,
 
 - Flashduty syncs information according to default field mappings and your custom field configurations. If your Jira issue type has required fields without mapping relationships, Jira issue creation may fail.
 - Jira issue details are accessed using project KEY + number format. If you modify the project KEY, saved issue URLs in Flashduty may become inaccessible, so please modify project KEYs with caution.
-`,le=`---
+`,de=`---
 title: "ServiceNow Sync"
 description: "Sync incidents with ServiceNow Incidents through ServiceNow sync webhook."
 date: "2025-05-19T10:00:00+08:00"
@@ -6831,6 +7026,7 @@ Through ServiceNow sync webhook, Flashduty incidents are associated and synchron
 ## In ServiceNow
 
 ### Create User
+Create a user to connect to the ServiceNow instance for Incident sync and updates. Skip this step if you already have an available user.
 
 1. Log in to the ServiceNow instance console, select \`ALL\`, enter \`USERS\` and select \`Organization\`-\`Users\`.
 2. Click \`New\` to create a new user.
@@ -6842,14 +7038,20 @@ Through ServiceNow sync webhook, Flashduty incidents are associated and synchron
 
 ### Configure User
 
-The user used to access ServiceNow needs to have administrator roles.
+   > **User Role Description**
+  > **itil:** The main usage scope of this role in Flashduty is limited to field retrieval in ServiceNow Incident Table and does not involve any other operations.
+  >
+  > **personalize_dictionary:** This role in Flashduty is primarily used only for field retrieval from ServiceNow Incident Tables, and does not involve any other operations.
+  > 
+  > For more information about the permission scope of these two roles, please refer to the ServiceNow [official documentation](https://www.servicenow.com/docs/bundle/washingtondc-platform-administration/page/administer/roles/reference/r_BaseSystemRoles.html#d130465e3182)
 
 1. On the user list page, find the newly created \`flashduty\` user and go to the configuration page.
 2. In the edit page, click \`Set Password\` to set a password.
-3. Click \`Roles\` to add **admin and itil** roles.
+3. Click \`Roles\` to add **personalize_dictionary and itil** roles (If custom field mapping configuration is not required, the personalize_dictionary permission does not need to be retained).
 4. Click \`Update\` to update the configuration.
 
-<img alt="drawing" width="600" src="https://download.flashcat.cloud/flashduty/doc/snow/snow-2.png" />
+![2025-09-24-16-29-05](https://docs-cdn.flashcat.cloud/images/png/a4416dff926e89b505224e03a4f774c6.png)
+![2025-09-24-16-29-58](https://docs-cdn.flashcat.cloud/images/png/19371c16f4c516c095752f2a8e0d45bf.png)
 
 ## In Flashduty
 
@@ -6861,14 +7063,27 @@ Enter the username/password and instance name configured above into the integrat
 - **Management Team:** When a management team is selected, only team members and tenant administrators can edit this integration.
 - **Channel:** Select the channel where this integration takes effect.
 - **Sync Direction:**
+
   - To_ServiceNow: Sync Flashduty incidents to ServiceNow.
   - From_ServiceNow: Sync ServiceNow Incidents to Flashduty.
   - Two-way: Bidirectional sync between Flashduty and ServiceNow.
-- **Trigger Mode**:
+
+- **Trigger Mode:**
+
   - Auto Trigger: Requires configuration of corresponding conditions, Flashduty will automatically sync incidents that meet the conditions to ServiceNow.
   - Manual Trigger: Requires manual triggering of ServiceNow sync in the More Actions section of the incident details page (the integration configuration name is the trigger name).
-- **Severity Mapping:** ServiceNow's Priority is determined by the combined values of Impact and Urgency, so you can refer to ServiceNow's \`Priority Lookup Rules\` for configuration. Additionally, note that only when ServiceNow Incident's Urgency changes will it trigger updates to Flashduty incident severity.
-- **Custom Field Mapping:** You can choose to sync certain labels or all labels of incidents as well as custom field content to ServiceNow fields (only text-type fields are supported).
+
+- **Severity Mapping:** 
+    - ServiceNow's Priority is determined by the combined values of Impact and Urgency, so you can refer to ServiceNow's \`Priority Lookup Rules\` for configuration.
+    - Only when the Urgency of a ServiceNow Incident changes will it trigger an update to the Flashduty incident severity.
+    - Since Flashduty cannot obtain ServiceNow's Impact and Urgency lists while following the principle of least privilege, only default values are provided. If you need to customize the mapping relationship, please contact technical support.
+
+- **Custom Field Mapping:** You can map tags or custom fields from incidents to corresponding text fields in ServiceNow tickets, enabling automatic information filling. This feature supports synchronizing common contextual information (such as service name, instance address, metric name, etc.) to ServiceNow for easier subsequent troubleshooting and tracking.
+
+    - Only supports target fields of single-line text or multi-line text types.
+    - Supports extracting values from incident tags (such as service, instance) or custom attributes.
+    - If the source field is empty, the target field will also remain empty and will not overwrite existing content.
+    - Mapping configurations are managed centrally in integration settings, eliminating the need for manual entry each time.
 
 ## In ServiceNow
 
@@ -7076,34 +7291,235 @@ Note: The body configures default receiving fields. If you have custom fields th
 
 | ServiceNow          | Flashduty     | Notes |
 | ------------------- | ------------- | ----- |
-| Short_description   | Title         |       |
+| Short_description   | Title         |  Title     |
+| Description         | Description   |   Description    |
+| Additional comments | Comments      |  Comments     |
+| State               | Progress      |  Progress    |
+| Urgency             | Severity      |  Severity     |
+| Others              | Custom Fields |  Custom Fields    |
+
+### Status Mapping
+
+| ServiceNow  | Flashduty  | Notes                  |
+| ----------- | ---------- | ---------------------- |
+| New         | Trigger    |           Trigger             |
+| In Progress | Processing |           Processing             |
+| On Hold     | Snoozed    | Default snooze 2 hours |
+| Resolved    | CLosed     |            CLosed            |
+| Closed      | CLosed     |            CLosed            |
+| Canceled    | CLosed     |            CLosed            |
+
+### Priority Mapping
+
+Only when ServiceNow's Urgency value changes will it affect Flashduty's Severity
+
+| ServiceNow | Flashduty | Notes |
+| ---------- | --------- | ----- |
+| Low        | Info      |  Info     |
+| Medium     | Warning   |   Warning    |
+| High       | Critical  |   Critical    |
+
+
+## QA
+
+<details>
+  <summary>Can the UserID be customized when creating a new ServiceNow user?</summary>
+  Yes, it can be customized. The documentation uses "flashduty" as the UserID to better identify that this user is used for Incident synchronization.
+</details>
+
+<details>
+  <summary>Getting 401 error when configuring integration</summary>
+  A 401 error is generally caused by an incorrect password. Please check if the password is correct, or reset a new password (when setting the password, do not check the "Password needs reset" option).
+</details>`,ce=`---
+title: "ServiceDesk Plus Sync"
+description: "Sync incidents with ServiceDesk Plus requests through ServiceDesk Plus sync webhook."
+date: "2025-05-19T10:00:00+08:00"
+url: "https://docs.flashcat.cloud/en/flashduty/servicedesk-plus-sync"
+---
+
+Through ServiceDesk Plus sync webhook, Flashduty incidents are associated and synchronized with ServiceDesk Plus requests to achieve integration between Flashduty and ServiceDesk Plus.
+
+This integration is based on the official v3 API protocol provided by ServiceDesk Plus and is compatible with its interface specifications. If you are using an on-premises deployment version, please confirm whether its API supports the v3 version. Additionally, there are differences in authorization configuration between the cloud and on-premises  of ServiceDesk Plus. Please refer to the relevant documentation for specific configurations.
+
+  - [Cloud](#cloud-version)
+  - [On-premises](#on-premises)
+
+When configuring this integration, if you choose the sync direction as From_ServiceDesk_Plus, you can skip the authorization-related configuration and directly refer to [Configure Sync](#configure-sync).
+
+## Cloud  <span id="cloud-version"></span>
+
+### In ServiceDesk Plus
+#### Step 1 Create Authorization Application
+Please select the corresponding Developer Console address according to your ServiceDesk Plus service region: [Data Centres](https://www.manageengine.com/products/service-desk/sdpod-v3-api/getting-started/data-centers.html)
+
+1. Log in to the Developer Console, select \`Self Client\` type Client and create it.
+2. Click \`Generate Code\`, fill in the \`Scope\`: **SDPOnDemand.requests.ALL,SDPOnDemand.setup.READ,SDPOnDemand.custommodule.READ**. Refer to [official documentation](https://www.manageengine.com/products/service-desk/sdpod-v3-api/getting-started/oauth-2.0.html#scopes) for permission scope.
+
+3. Select the maximum **10 minutes** for \`Time Duration\`, fill in the \`Scope Description\` as customizable, for example: For Flashduty sync use, and create.
+4. Copy the generated **Code**, **Client ID** and **Client Secret** for backup.
+
+![2025-09-24-14-59-28](https://docs-cdn.flashcat.cloud/images/png/793fa15bd6e919e81fd3baaaab591275.png)
+![2025-09-24-15-00-56](https://docs-cdn.flashcat.cloud/images/png/3b1b9d7a9c4bcc93ddf4cd73e47713f5.png)
+
+###### Note: The Code is only valid for 10 minutes and can only be used once, so after obtaining the Code, please complete the [Integration Authorization](#integration-authorization) as soon as possible within the validity period.
+
+### In Flashduty
+#### Step 2 Integration Authorization <span id="integration-authorization"></span>
+Please select the corresponding API Endpoint and Accounts Server URL according to your ServiceDesk Plus service region: [Data Centres](https://www.manageengine.com/products/service-desk/sdpod-v3-api/getting-started/data-centers.html)
+
+1. Select **Cloud** for \`Platform Type\`, fill in \`API Endpoint\` and \`Accounts Server URL\`.
+2. Fill in the \`Code\`, \`Client ID\` and \`Client Secret\` generated in the **Create Authorization Application** step into the corresponding edit boxes and click Next to complete [Integration Configuration](#integration-configuration) (if an error occurs, please re-obtain the Code or contact technical support to troubleshoot the problem).
+
+## On-premises <span id="on-premises"></span>
+### In ServiceDesk Plus
+#### Step 1 Generate API Key
+1. Log in to the ServiceDesk Plus console, click \`Generate API Key\` in the personal center.
+2. Select **Never Expires** for \`Token Expiration Time\`, copy the generated **Token** for backup, and complete [Integration Authorization](#on-premises-integration-authorization).
+
+###### Note: The user who generates the API key needs to have relevant permissions, such as create/update requests, obtain template/priority/custom field lists and other permissions. If the permissions are insufficient, it will cause the integration configuration to fail. It is recommended to use an administrator role to generate.
+
+### In Flashduty
+#### Step 2 Integration Authorization <span id="on-premises-integration-authorization"></span>
+1. Select **On-premises** for \`Platform Type\`, fill in \`API Endpoint\`.
+2. Fill in the generated **Token** into the corresponding edit box and click Next to complete [Integration Configuration](#integration-configuration).
+
+
+## General Configuration
+
+### In Flashduty
+#### Step 1 Integration Configuration <span id="integration-configuration"></span>
+
+1. **Integration Name:** Define a name for the current integration.
+2. **Management Team:** When a management team is selected, only team members and tenant administrators can edit this integration.
+3. **Sync Direction:**
+
+    - To_ServiceDesk_Plus: Sync Flashduty incidents to ServiceDesk Plus.
+    - From_ServiceDesk_Plus: Sync ServiceDesk Plus requests to Flashduty.
+    - Two-way: Bidirectional sync between Flashduty and ServiceDesk Plus.
+    
+4. **Trigger Mode**:
+    - Auto Trigger: Requires configuration of corresponding conditions, Flashduty will automatically sync incidents that meet the conditions to ServiceDesk Plus.
+    - Manual Trigger: Requires manual triggering of ServiceDesk Plus sync in the More Actions section of the incident details page (the integration configuration name is the trigger name).
+
+5. **Channel:** Select the channel where this integration takes effect.
+6. **Request Template:** Select the template to use when creating requests.
+7. **Severity Mapping:** The mapping relationship between Flashduty severity and ServiceDesk Plus priority. For default mapping relationship, please refer to [Priority Mapping](#priority-mapping).
+8. **Custom Field Mapping:** You can map labels or custom fields in incidents to corresponding text fields in ServiceDesk Plus tickets to achieve automatic information filling. This feature supports syncing common context information (such as service name, instance address, metric name, etc.) to ServiceDesk Plus for subsequent troubleshooting and tracking.
+    - Only supports target fields of single-line text or multi-line text type.
+    - Supports extracting values from incident labels (such as service, instance) or custom attributes.
+    - If the source field is empty, the target field will also remain empty and will not overwrite existing content.
+    - Mapping configuration is managed uniformly in integration settings without manual filling each time.
+
+9. **Assignee Mapping:** When Flashduty incidents are synced to ServiceDesk Plus and need to be automatically assigned to Technician or Group, you can get the value of Flashduty incident labels as the assignee (if the corresponding assignee does not exist, it will cause sync failure, please choose carefully).
+
+10. Click \`Save\` to complete the configuration.
+
+### In ServiceDesk Plus
+#### Step 2 Create Requester
+When Flashduty incidents are synced to ServiceDesk Plus, the Requester automatically set by the system
+
+1. Log in to the ServiceDesk Plus console and find the \`Setup\` configuration page.
+2. Select \`Users & Permissions\`, then enter the \`Users\` creation page and select \`New Requester\`.
+3. Fill in **flashduty** for \`Name (Display Name)\` and \`First Name\`, fill in **flashduty-sync@flashcat.cloud** for \`Email\`.
+4. Other settings can be configured as needed, click \`Save\` to save the configuration.
+
+![2025-09-24-15-03-31](https://docs-cdn.flashcat.cloud/images/png/9ee174f85ac918476888efd759511d31.png)
+
+#### Step 3 Configure Sync <span id="configure-sync"></span>
+To achieve synchronization of ServiceDesk Plus requests to Flashduty, please refer to this configuration item. **Note:** Different versions may have slightly different paths, but the configuration method is the same.
+##### Create Webhook
+1. Log in to the ServiceDesk Plus console and find the \`Setup\` configuration page.
+2. Select \`Automation\`, then enter the \`Custom Actions\` page and select \`Webhooks\`.
+3. Click \`New Webhook\`, fill in **to_Flashduty** for \`Webhook Name\` in the edit page.
+4. Fill in the integration's <span class='integration_url'>push URL</span> for \`URL\`.
+5. Select **Requests** for \`Applies to\`, select **POST** for \`Method\`, fill in **Content-Type application/json** in \`Headers\`.
+6. Select **JSON** for \`Message Body\` Type and fill in the following content:
+
+  \`\`\` 
+  # Cloud
+  {
+    "subject":"\${subject}",
+    "request_id":"\${id}",
+    "description":"\${udf_fields.txt_destination}",
+    "priority":"\${priority.name}",
+    "status":"\${status.name}",
+    "txt_test_field":"\${udf_fields.txt_test_field}"
+  
+  }
+  \`\`\`
+
+   \`\`\` 
+  # On-premises
+  {
+    "suject":"\${{request.subject}}",
+    "request_id":"\${{request.id}}",
+    "description":"\${{request.description}}",
+    "status":"\${{request.status.name}}",
+    "priority":"\${{request.priority.name}}",
+    "udf_sline_301":"\${{request.udf_fields.udf_sline_301}}"
+  }
+
+  \`\`\`
+7. Click \`Save\` to complete the configuration.
+
+![2025-09-23-13-32-32](https://docs-cdn.flashcat.cloud/images/png/94ca1d094ed38ebcaf299364eddfd0ac.png)
+
+##### Create Trigger
+1. Log in to the ServiceDesk Plus console and find the \`Setup\` configuration page.
+2. Select \`Automation\`, then enter the \`Triggers\` page and select \`Request\`.
+3. Click \`New Trigger\`, fill in **to_Flashduty** for \`Name\` in the edit page.
+4. Select **Request** for \`Trigger applies to\`, check **Create and Edited** for \`Execute when a request is\`.
+5. Select **Any time** for \`Execute during\` and check **Enable Trigger**.
+6. Select \`Without condition\` for \`Conditions\` or configure according to actual needs.
+7. Select **Webhook** in \`Actions\` and check **to_Flashduty** channel.
+8. Click \`Save\` to complete the configuration.
+
+![2025-09-23-13-42-20](https://docs-cdn.flashcat.cloud/images/png/9573d79763af656e0e08c5bdc3649a14.png)
+
+
+## Sync Information
+
+### Form Fields
+
+| ServiceDesk Plus    | Flashduty     | Notes |
+| ------------------- | ------------- | ----- |
+| Subject   | Title         |       |
 | Description         | Description   |       |
-| Additional comments | Comments      |       |
-| State               | Progress      |       |
-| Urgency             | Severity      |       |
+| Status              | Progress      |       |
+| Priority            | Severity      |       |
 | Others              | Custom Fields |       |
 
 ### Status Mapping
 
-| ServiceNow  | Flashduty  | Notes                  |
+| ServiceDesk Plus | Flashduty  | Notes                  |
 | ----------- | ---------- | ---------------------- |
-| New         | Trigger    |                        |
+| Open         | Trigger    |                        |
 | In Progress | Processing |                        |
+| Assigned | Processing |                        |
+| Pending Verification | Processing |                        |
+| Staging | Processing |                        |
 | On Hold     | Snoozed    | Default snooze 2 hours |
 | Resolved    | CLosed     |                        |
 | Closed      | CLosed     |                        |
 | Canceled    | CLosed     |                        |
+| Rejected    | CLosed     |                        |
 
-### Priority Mapping
-
-Only when ServiceNow's Urgency value changes will it affect Flashduty's Severity
+### Priority Mapping <span id="priority-mapping"></span>
 
-| ServiceNow | Flashduty | Notes |
+| ServiceDesk Plus | Flashduty | Notes |
 | ---------- | --------- | ----- |
 | Low        | Info      |       |
 | Medium     | Warning   |       |
 | High       | Critical  |       |
-`,de=`---
+
+
+## FAQ
+
+<details>
+  <summary> Can the Scope be changed</summary>
+  No, the Scope currently used is already the smallest unit. Flashduty needs to perform get/create/update operations when syncing requests with ServiceDesk Plus, and needs to obtain priority/custom field lists when configuring integration, so corresponding permission support is required.
+</details>
+`,he=`---
 title: "Configure Notification Templates"
 description: "Customize notification content through template configuration"
 date: "2024-05-10T10:00:00+08:00"
@@ -7352,7 +7768,36 @@ CloseTime | int64 | No | Close time, EndTime is alert recovery time, CloseTime i
     {{jsonGet .Labels.rule_note "#(userId==7777)#.instanceId" }}
 
     \`\`\`
-10. **如何使用逻辑与、或等条件进行内容显示判断？**
+
+10. **How to Retrieve the Image URL via the Src Attribute of [Image](#Image)**
+    - The imageSrcToURL function can be implemented, accepting parameters: $root and Src
+    - If Src is an image_key from the Image Upload API, it should be converted into a short-term accessible URL
+    - If Src is an accessible http/https address, the address should be returned directly
+    - Dingtalk/Slack Apps employ this method to render images
+    \`\`\`go
+    {{ $root := . }}
+    {{ range $i, $v := .Images }}
+    {{ $imageURL := imageSrcToURL $root $v.Src }}
+    {{ if $imageURL }}![]({{$imageURL}}){{ end }}{{end}}
+    \`\`\`
+
+11. **How to Convert and Upload Images to a Third-Party Notification Platform**
+    - The transferImage function can be implemented, accepting parameters: $root and Src
+    - Src can be an image_key from the Image Upload API or an accessible http/https image URL
+    - Image size must not exceed 10 MB
+    - Supported image formats include JPG, JPEG, PNG, WEBP, GIF, BMP, ICO, TIFF, HEIC
+    - Requires enabling the application permission to access and upload image or file resources
+    - Lark/Feishu Apps employ this method to render images
+
+    \`\`\`go
+    {{ $root := . }}
+    {{ range $i, $v := .Images }}
+      {{ $transferURL := transferImage $root $v.Src }}
+      {{ if $transferURL }}![]({{$transferURL}}){{ end }}
+    {{ end }}
+    \`\`\`
+
+12. **How to use logical AND, OR, and other conditions for conditional rendering/content display judgment?**
 
     \`\`\`
     # Supported functions
@@ -7385,7 +7830,7 @@ CloseTime | int64 | No | Close time, EndTime is alert recovery time, CloseTime i
   
     \`\`\`
 
-11. **How do I find more functions and their usage examples?**
+13. **How do I find more functions and their usage examples?**
    - Function list: https://github.com/flashcatcloud/sprig/blob/master/functions.go#L97
    - Usage examples: Check corresponding _test.go files, e.g., date function test cases at https://github.com/flashcatcloud/sprig/blob/master/date_test.go
 
@@ -7398,10 +7843,15 @@ Below are specific instructions for each notification channel.
 You need to configure \`Integration Center-Instant Message-Feishu\` integration first to send message cards. If custom content is not set, the system default template will be used, rendering all label information:
 
 \`\`\`go
-{{if .Description}}**description** :{{toHtml .Labels.body_text .Description}}{{end}}
-{{if .Labels.resource}}**resource** : {{toHtml (joinAlertLabels . "resource" ", ")}}{{end}}
+{{if .Labels.body_text}}{{.Labels.body_text}}{{else if .Description}}{{.Description}}{{end}}
+{{if .Labels.resource}}**resource** : {{(joinAlertLabels . "resource" ", ")}}{{end}}
 {{range $k, $v := .Labels}}
-{{if not (in $k "resource" "body_text")}}**{{$k}}** : {{toHtml $v}}{{end}}{{end}}
+{{if not (in $k "resource" "body_text" "body_text_with_table")}}**{{$k}}** : {{$v}}{{end}}{{end}}
+{{ $root := . }}
+{{ range $i, $v := .Images }}
+  {{ $transferURL := transferImage $root $v.Src }}
+  {{ if $transferURL }}![]({{$transferURL}}){{ end }}
+{{ end }}
 \`\`\`
 
 As shown below:
@@ -7448,6 +7898,10 @@ You need to configure \`Integration Center-Instant Message-Dingtalk\` integratio
 {{if .Labels.resource}}**resource** : {{toHtml (joinAlertLabels . "resource" ", ")}}{{end}}
 {{range $k, $v := .Labels}}
 {{if not (in $k "resource" "body_text")}}**{{$k}}** : {{toHtml $v}}{{end}}{{end}}
+{{ $root := . }}
+{{ range $i, $v := .Images }}
+{{ $imageURL := imageSrcToURL $root $v.Src }}
+{{ if $imageURL }}![]({{$imageURL}}){{ end }}{{ end }}
 \`\`\`
 
 As shown below:
@@ -7526,13 +7980,22 @@ As shown below:
 
 ## Slack App
 ---
+
 You need to configure \`Integration Center-Instant Message-Slack\` integration first to send message cards. If custom content is not set, the system default template will be used, rendering only common label information:
 
 \`\`\`go
-{{if .Description}}*description* :{{toHtml .Labels.body_text .Description}}{{end}}
-{{if .Labels.resource}}*resource* : {{toHtml (joinAlertLabels . "resource" ", ")}}{{end}}
+{{if .Labels.body_text}}{{.Labels.body_text}}{{else if .Description}}{{.Description}}{{end}}
+{{if .Labels.resource}}*resource* : {{(joinAlertLabels . "resource" ", ")}}{{end}}
 {{range $k, $v := .Labels}}
-{{if not (in $k "resource" "body_text")}}*{{$k}}* : {{toHtml $v}}{{end}}{{end}}
+{{if not (in $k "resource" "body_text" "body_text_with_table")}}*{{$k}}* : {{$v}}{{end}}{{end}}
+{{ $root := . }}
+{{ range $i, $v := .Images }}
+ {{ $imageURL := imageSrcToURL $root $v.Src }}
+ {{ if $imageURL }}
+  ---
+  ![{{$v.Alt}}]({{$imageURL}})
+ {{ end }}
+{{ end }}
 \`\`\`
 
 As shown below:
@@ -7544,6 +8007,7 @@ If you want to display only key label information, you can refer to the code seg
 - We've listed some common labels, you can add or remove as needed
 - Messages can be around 15000 characters long, content beyond this will be truncated
 - In Slack app, the system will automatically remove empty rendered lines (due to non-existent labels), so you can configure freely
+- To display images, use three consecutive hyphens \`---\` to separate it from other content. The image syntax must begin with \`![\` format, as demonstrated in the ​​FAQ​​ section
 
 \`\`\`go
 {{if (index .Labels "resource")}}*resource*：{{toHtml (joinAlertLabels . "resource" ", ")}}{{end}}
@@ -8223,7 +8687,7 @@ As shown in the image below:
 
 <img src="https://download.flashcat.cloud/flashduty/changelog/20230720/email_render.png" alt="drawing" style="display: block; margin: 0 auto;" width="500"/>
 
-</div>`,ce=`---
+</div>`,ue=`---
 title: "Link Integration"
 description: "Through Link integration, you can quickly access external links by obtaining key parameters from incident attributes, labels, and other information"
 date: "2025-05-19T10:00:00+08:00"
@@ -8280,4 +8744,4 @@ https://cmdb.com/vm?sn=VM123456
 1. When referenced content does not exist, Link integration will still generate the corresponding link but will not be able to retrieve the value
 2. Each channel can bind up to three Link integrations
 3. Pay attention to reference syntax; improper variable reference formatting will result in failure to retrieve corresponding values
-`,ue={CustomAlert:n,Email:t,N9e:a,Prometheus:i,Grafana:o,Zabbix:s,UptimeKuma:r,AliyunARMS:l,AliyunCmEvent:d,AliyunCm:c,AliyunSLS:e,AWSCW:e,AzureMonitor:u,BaiDuBCM:h,HuaWeiCES:g,InfluxDB:p,OpenFalcon:m,PagerDuty:f,TencentBK:y,TencentCLS:v,TencentCm:b,TencentEb:w,OceanBase:C,Graylog:k,Skywalking:I,Sentry:S,Jiankongbao:A,AWSEventBridge:x,Dynatrace:L,HuaweiyunLTS:F,GoogleCM:_,Zilliz:G,Splunk:R,AppDynamics:T,SolarWinds:U,VolcEngineMetric:D,VolcEngineEvent:E,VolcEngineTLS:N,OpManager:M,Meraki:P,StateCloud:W,Guance:q,CustomChange:Z,Jira:Q,Lark:X,Dingtalk:ee,Wecom:ne,Slack:te,MicrosoftTeams:ae,AlertWebhook:ie,IncidentWebhook:oe,CustomAction:se,Templates:de,HuaweiyunAPM:O,JiraSync:re,ZStack:j,Keep:H,ElastAlert2:Y,DingtalkAlert:$,FeishuAlert:V,VolcEngineDetect:B,Link:ce,ServiceNowSync:le,Monit:z,Rum:K,Cloudflare:J};module.exports=ue;
+`,ge={CustomAlert:n,Email:t,N9e:a,Prometheus:i,Grafana:o,Zabbix:s,UptimeKuma:r,AliyunARMS:l,AliyunCmEvent:d,AliyunCm:c,AliyunSLS:e,AWSCW:e,AzureMonitor:h,BaiDuBCM:u,HuaWeiCES:g,InfluxDB:p,OpenFalcon:m,PagerDuty:f,TencentBK:y,TencentCLS:v,TencentCm:b,TencentEb:w,OceanBase:C,Graylog:k,Skywalking:I,Sentry:S,Jiankongbao:A,AWSEventBridge:F,Dynatrace:x,HuaweiyunLTS:L,GoogleCM:_,Zilliz:G,Splunk:R,AppDynamics:T,SolarWinds:D,VolcEngineMetric:U,VolcEngineEvent:E,VolcEngineTLS:N,OpManager:P,Meraki:M,StateCloud:W,Guance:q,CustomChange:Q,Jira:X,Lark:ee,Dingtalk:ne,Wecom:te,Slack:ae,MicrosoftTeams:ie,AlertWebhook:oe,IncidentWebhook:se,CustomAction:re,Templates:he,HuaweiyunAPM:O,JiraSync:le,ZStack:$,Keep:j,ElastAlert2:H,DingtalkAlert:Y,FeishuAlert:z,VolcEngineDetect:B,Link:ue,ServiceNowSync:de,Monit:V,Rum:K,Cloudflare:J,WecomAlert:Z,ServiceDeskPlusSync:ce};module.exports=ge;