flashduty-knowledge-base 1.3.4 → 1.3.5

package/dist/esm/en.js

@@ -506,7 +506,7 @@ Nightingale/Flashcat to Flashduty alert severity mapping:
     
 </details>
 
-`,o=`---
+`,i=`---
 title: "Prometheus Integration Guide"
 description: "Push Prometheus alert events to Flashduty through AlertManager using webhooks. When an alert is triggered, it sends a trigger event to Flashduty, and when the alert recovers, it sends a recovery event."
 date: "2025-05-19T10:00:00+08:00"
@@ -688,7 +688,7 @@ Prometheus to Flashduty severity mapping:
 
 
 
-`,i=`---
+`,o=`---
 title: "Grafana Integration"
 description: "Sync Grafana alert events to Flashduty via webhook to achieve automated alert noise reduction."
 date: "2025-05-19T10: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>
-`,_=`---
+`,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"
@@ -3486,7 +3486,7 @@ Choose this option when you need to route alerts to different channels based on
 |Info|Info|Info|
 
 </div>
-`,L=`---
+`,_=`---
 title: "Google Cloud Monitoring Alert Events"
 description: "Sync Google Cloud Monitoring alert events to Flashduty via webhook for automated alert noise reduction"
 date: "2024-07-05T10: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"
@@ -4521,7 +4521,7 @@ Choose this option when you need to route alerts to different channels based on
 | North | Beijing2/Changchun/Harbin/North China/Inner Mongolia3/Qingdao/Shenyang3/Shijiazhuang/Taiyuan/Tianjin/Zhengzhou |
 
 </div>
-`,G=`---
+`,q=`---
 title: "Guance Alert Events"
 description: "Sync Guance alert events to Flashduty via webhook for automated alert noise reduction"
 date: "2024-07-05T10:00:00+08:00"
@@ -4606,7 +4606,7 @@ Choose this option when you need to route alerts to different channels based on
 | Data Missing | Info | Info |
 
 </div>
-`,q=`---
+`,G=`---
 title: "Zilliz Alert Events"
 description: "Sync Zilliz alert events to Flashduty via webhook for automated alert noise reduction"
 date: "2024-07-05T10: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).
-`,B=`---
+`,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"
@@ -5239,7 +5239,7 @@ By default, the system always creates new alerts for each message, but you can s
 ---
 
 Currently, all alerts pushed to Flashduty through the Feishu(lark) integration are set to Warning severity. However, you can customize the severity using the [alert pipeline](https://docs.flashcat.cloud/en/flashduty/alert-pipelines).
-`,z=`---
+`,B=`---
 title: "Volcengine Cloud-Detect Alert Events"
 description: "Sync Volcengine Cloud-Detect alert events to Flashduty via webhook for automated alert noise reduction"
 date: "2024-07-05T10:00:00+08:00"
@@ -5341,7 +5341,7 @@ Go to the \`Monit\` - \`Alert Rules\` - \`Rule Details\` page to configure monit
 ![2025-08-19-20-35-45](https://docs-cdn.flashcat.cloud/images/png/59c9d2566db9a0482fb2eabb729ea739.png)
 
 In some cases, you may want to route alerts generated by the same alert rule to different channels based on conditions. In this case, you can choose to deliver alerts directly to the integration rather than to the channels, and set routing rules under the current integration.
-`,J=`---
+`,K=`---
 title: "RUM Alert Integration"
 description: "Flashduty RUM alert integration, RUM service reports alerts through this integration"
 date: "2025-05-19T10:00:00+08:00"
@@ -5361,7 +5361,7 @@ Go to the \`RUM\` - \`Application Details\` - \`Alert Settings\` page to enable
 ![2025-08-20-10-16-14](https://docs-cdn.flashcat.cloud/images/png/b6ad24809a2ee8f0b3c0b38988b46030.png)
 
 For more information, please refer to [RUM Issue Alerting](https://docs.flashcat.cloud/en/flashduty/rum/issue-alerting?nav=01JCQ7A4N4WRWNXW8EWEHXCMF5).
-`,K=`---
+`,J=`---
 title: "Cloudflare Alert Events"
 description: "Sync Cloudflaret alert events to Flashduty via webhook for automated alert noise reduction"
 date: "2024-07-05T10: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,7 +5643,7 @@ Flashduty extracts the status.name information from the webhook payload by defau
 Please contact Flashduty if you wish to modify this mapping.
 
 </div>
-`,X=`---
+`,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"
@@ -5618,12 +5698,19 @@ For details, see the Feishu/Lark development documentation [Configure applicatio
 
 ![2025-09-17-19-49-19](https://docs-cdn.flashcat.cloud/images/png/393e7629de652d1793b69af7d4f3831c.png)
 
-3. Go to Event Callbacks → **Callback Configuration** page, configure the \`Subscription Method\` (using the **Message Card Request URL** from the integration details). Then, subscribe to the following two callback events:
+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:
 
-- \`im.message.receive_v1\`
 - \`im.chat.disbanded_v1\`
+- \`im.message.receive_v1\`
+
+![2025-09-18-11-06-05](https://docs-cdn.flashcat.cloud/images/png/71910d8af8d60b5f30baf009081646df.png)
 
-![2025-09-17-19-53-14](https://docs-cdn.flashcat.cloud/images/png/c42542dc49930c2e20f5921749bf3565.png)
+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:
+
+- \`card.action.trigger\`
+- \`card.action.trigger_v1\`
+
+![2025-09-19-18-41-42](https://docs-cdn.flashcat.cloud/images/png/5ebe9faff7f78a6764da92a342eab7c0.png)
 
 ### 2. Add redirect URL to Feishu/Lark application
 
@@ -5639,7 +5726,7 @@ Go to the **Permission Management** page and apply for the following permissions
 
 - \`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 (for configuring war rooms)<span id="war-room-scope"></span>
+- \`contact:user.id:readonly\`: Get user ID by phone number or email <span id="war-room-scope"></span>
 
 ![2025-09-17-19-59-38](https://docs-cdn.flashcat.cloud/images/png/61cb9fbc295e94b4d9acd7e44ac75e13.png)
 
@@ -5702,7 +5789,7 @@ After completing the previous steps, in the **Enhanced Features** module of the
    > 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).`,ee=`---
+   - 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: "By integrating a custom Dingtalk application, you can receive and respond to alerts within Dingtalk."
 date: "2025-05-19T10:00:00+08:00"
@@ -5925,7 +6012,7 @@ After the application is published, you can access it via the **mobile client**
    | 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).`,ne=`---
+   > 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: "By integrating a WeCom application, you can receive and respond to alerts within WeCom."
 date: "2025-05-19T10:00:00+08:00"
@@ -6011,6 +6098,10 @@ This document supports both [integrating third-party applications](#third-party)
 
    ![2025-09-18-13-10-56](https://docs-cdn.flashcat.cloud/images/png/9a1bee272010ceaa38d2f39025215379.png)
 
+10. Company's Trusted IP : 47.94.95.118; 123.56.8.183; 47.94.193.81; 1.13.19.96
+
+   ![2025-09-19-11-06-36](https://docs-cdn.flashcat.cloud/images/png/0aa3c0129f7c99785ea77d088cd65774.png)
+
 ## 3. Configure war room
 
 ---
@@ -6050,7 +6141,7 @@ After completing the previous steps, in the **Enhanced Features** module of the
 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).`,te=`---
+   - 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"
@@ -6104,7 +6195,7 @@ After completing the previous steps, in the **Enhanced Features** module of the
    - 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).`,ae=`---
+   - 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"
@@ -6141,7 +6232,7 @@ If the application status is "Blocked", please wait a moment and refresh the pag
 #### Check if successfully added
 After waiting a few minutes, organization members can find this application in +Apps → **Built for your org**.
 
-![2025-09-18-13-49-58](https://docs-cdn.flashcat.cloud/images/png/199728ab0b1f9f24db80da0b3ecc8cd2.png)
+![2025-09-18-17-05-37](https://docs-cdn.flashcat.cloud/images/png/f7827638d1877005ca674cbbd2aaa4a3.png)
 
 ### 3. Update application
 ::: caution
@@ -6163,14 +6254,14 @@ If your installed application version is lower than 1.0.3, please follow this pr
 1. Find the Flashduty application in the app marketplace.
 > If there is no application, please contact your Microsoft Teams organization administrator.
 
-![2025-09-18-13-53-57](https://docs-cdn.flashcat.cloud/images/png/8942fdf4327c96abcf31f4a9b7bf12d2.png)
+![2025-09-18-17-06-34](https://docs-cdn.flashcat.cloud/images/png/0905e663241ce448a1381ef8c08aa777.png)
 
 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.
 :::
 
-![2025-09-18-13-54-41](https://docs-cdn.flashcat.cloud/images/png/8618dfd0f89507a6424e40d898d66fbd.png)
+![2025-09-18-17-11-29](https://docs-cdn.flashcat.cloud/images/png/01fa86b63d01d2735aa6c4a53efb3c69.png)
 
 ### 2. Send link command
 In the Team, @Flashduty and send the command \`linkTeam {ID}\`, then click **Link Now**.
@@ -6183,11 +6274,11 @@ In the Team, @Flashduty and send the command \`linkTeam {ID}\`, then click **Lin
 1. Find the Flashduty application in the app marketplace.
 > If there is no application, please contact your Microsoft Teams organization administrator.
 
-![2025-09-18-13-53-57](https://docs-cdn.flashcat.cloud/images/png/8942fdf4327c96abcf31f4a9b7bf12d2.png)
+![2025-09-18-17-06-34](https://docs-cdn.flashcat.cloud/images/png/0905e663241ce448a1381ef8c08aa777.png)
 
 2. Add the application to the target Chat.
 
-![2025-09-18-13-56-17](https://docs-cdn.flashcat.cloud/images/png/d0beee141db63714ccecb095affee79b.png)
+![2025-09-18-17-14-23](https://docs-cdn.flashcat.cloud/images/png/6e56d7de341737fe495e5ff18eb1af34.png)
 
 ### 2. Send link command
 In the Chat, @Flashduty and send the command \`linkChat {ID} {ChatName}\`, then click **Link Now**.
@@ -6200,7 +6291,7 @@ In the Chat, @Flashduty and send the command \`linkChat {ID} {ChatName}\`, then
 1. Find the Flashduty application in the app marketplace.
 > If there is no application, please contact your Microsoft Teams organization administrator.
 
-![2025-09-18-13-53-57](https://docs-cdn.flashcat.cloud/images/png/8942fdf4327c96abcf31f4a9b7bf12d2.png)
+![2025-09-18-17-06-34](https://docs-cdn.flashcat.cloud/images/png/0905e663241ce448a1381ef8c08aa777.png)
 
 2. Click **Open Application**.
 
@@ -6387,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
-`,ie=`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>
 
@@ -6594,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
 
@@ -6841,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"
@@ -6923,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"
@@ -6935,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.
@@ -6946,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 **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
 
@@ -6965,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
 
@@ -7180,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
+### Priority Mapping <span id="priority-mapping"></span>
 
-Only when ServiceNow's Urgency value changes will it affect Flashduty's Severity
-
-| 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"
@@ -8375,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"
@@ -8432,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
-`,he={CustomAlert:n,Email:t,N9e:a,Prometheus:o,Grafana:i,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:_,GoogleCM:L,Zilliz:q,Splunk:R,AppDynamics:T,SolarWinds:U,VolcEngineMetric:D,VolcEngineEvent:E,VolcEngineTLS:N,OpManager:P,Meraki:M,StateCloud:W,Guance:G,CustomChange:Z,Jira:Q,Lark:X,Dingtalk:ee,Wecom:ne,Slack:te,MicrosoftTeams:ae,AlertWebhook:oe,IncidentWebhook:ie,CustomAction:se,Templates:de,HuaweiyunAPM:O,JiraSync:re,ZStack:$,Keep:j,ElastAlert2:H,DingtalkAlert:Y,FeishuAlert:B,VolcEngineDetect:z,Link:ce,ServiceNowSync:le,Monit:V,Rum:J,Cloudflare:K};module.exports=he;
+`,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;