Third-Party App Integration and Custom App Integration only need to configure one method as needed.
1. Third-Party App Integration
As a WeCom service provider, Flashduty provides a long-term free version of the Flashduty app. This app requires WeCom API call authorization to use (passwordless login + message sending). This authorization currently supports up to 60 days free; beyond this usage period, Flashduty needs to purchase WeCom licenses for you before you can continue using it.
-
Visit WeCom Admin Console, go to App Management → Apps page, click Add Third-Party App.
-
Enter
Flashdutyin the search bar, after finding the app, click Add.
-
Modify app Visibility, recommend selecting all employees or specific department nodes to avoid modifying when new enterprise members join. Then click Agree to the above authorization and add to complete installation.
-
Visit WeCom Admin Console, go to My Enterprise page, get
Corp ID.
-
Return to Flashduty On-call integration configuration page, fill in the
Corp IDobtained in the previous step, click Save to complete integration.
2. Custom App Integration
-
Visit WeCom Admin Console, go to App Management → Apps page, click Create App.
-
Configure App Logo, App Name, and App Visibility.
-
Return to Flashduty On-call integration configuration page, select whether your WeCom is
Non-private deployment versionbased on your actual situation. If your WeCom is a private deployment version, you need to fill inEndpointin the configuration page. This address needs to be accessible by Flashduty services—you may consider setting up whitelist authorization for it. -
Visit WeCom Admin Console, go to My Enterprise page, get
Corp ID, and fill it in the Flashduty On-call integration configuration page. -
Return to WeCom Admin Console, go to App Management page, click the app you created to enter details page. Get
AgentIdfrom the page and fill it in the Flashduty On-call integration configuration page. -
On the app details page, get
Secretand fill it in the Flashduty On-call integration configuration page. - On the app details page, go to Web Authorization & JS-SDK page, click Set Trusted Domain, and configure as required.
The trusted domain needs to point to Flashduty On-call’s backend address
{api_host} (achievable via CNAME or proxy forwarding). For trusted domain requirements, see WeCom official documentation Enterprise Internal Development Domain Configuration Guide.
Return to Flashduty On-call integration configuration page, fill in this domain and complete verification.
-
On the app details page, go to Receive Messages page, and Set API Receive. Click Random Generate for
TokenandEncodingAESKeyrespectively, then copy and save the generated values.
Return to Flashduty On-call integration configuration page, fill in the saved TokenandEncodingAESKey, click Save to complete integration. -
Copy the
Callback URLfrom Flashduty On-call integration details page, return to WeCom’s Receive Messages page. In API Receive settings, fill in thisCallback URLand theTokenandEncodingAESKeysaved in the previous step, then click Save.
- Configure Frontend Trusted Domain
The trusted domain needs to point to Flashduty On-call’s frontend address
console.flashcat.cloud (achievable via CNAME or proxy forwarding). For trusted domain requirements, see WeCom official documentation Enterprise Internal Development Domain Configuration Guide.
- Configure Trusted IP Address:
47.93.12.134
3. Configure War Room
After completing previous steps, in the Flashduty On-call integration configuration page’s Enhanced Features section, check Enable War Room to activate this feature—no additional configuration needed.4. FAQ
After clicking integration save button, system shows 'authorize app first' error?
After clicking integration save button, system shows 'authorize app first' error?
How to complete account linking or message delivery shows 'App not linked'?
How to complete account linking or message delivery shows 'App not linked'?
- Login to WeCom client (desktop or mobile), go to Workspace, find and open the Flashduty app
- First entry requires login. Select your member account, after successful login via password or SSO, Flashduty account and WeCom account will be linked
- Subsequent app access will be automatically passwordless
How to send incident notifications?
How to send incident notifications?
- Before sending notifications, account linking must be completed as described in the previous question
- Go to the specified channel, navigate to
Escalation Rules→ Personal Channel, selectWeComas notification method - Flashduty On-call supports customizing WeCom notification content. Go to Template Management page to set custom templates
Custom area can display up to 8 lines; excess will be truncated by WeCom.

How to handle alerts within WeCom?
How to handle alerts within WeCom?
- Click card message to go directly to alert details page
- Click Start Processing to directly set alert to
Processingstatus - Click Close Directly to directly set alert to
Closedstatus - Click Snooze 2 hours to snooze the alert for 2 hours. For longer snooze times, click
...in the card’s top-right corner for more snooze options
Why does the card message have a 'Refresh Status' button?
Why does the card message have a 'Refresh Status' button?
How to set Mac desktop to open with system default browser?
How to set Mac desktop to open with system default browser?
Mac desktop defaults to opening links with WeCom’s built-in browser. Try using shortcut
ctrl + command + shift + d to enable debug mode, then select Debug → Browser, WebView Related → Open Webpage with System Browser to change link opening method. Use the same shortcut to disable debug mode; settings will be preserved.Incident notification failed with 'WeCom license not enabled' prompt?
Incident notification failed with 'WeCom license not enabled' prompt?
Please contact Flashduty customer service or your dedicated technical support to purchase and enable the license.
Why isn't War Room working as expected?
Why isn't War Room working as expected?
See the FAQ section in War Room documentation.
Why does opening the app in WeCom Workspace show 'redirect_uri needs to use app trusted domain'?
Why does opening the app in WeCom Workspace show 'redirect_uri needs to use app trusted domain'?
Please confirm whether the domain in the
redirect_uri parameter of the App Homepage URL has completed WeCom’s required domain ownership verification. See WeCom official documentation Enterprise Internal Development Domain Configuration Guide.