Skip to main content
Plan requirement: Every plan can create IM applications for AI SRE conversations. Using an application for On-call notifications requires an active On-call Professional subscription. Learn more
Choose one of two methods: Third-Party App Integration or Custom App Integration. When you create a WeCom integration, Application version defaults to Self-built app (recommended); the other option is Third-party app (scan to install). War Room and @ AI SRE in group chats are available only with a custom app.

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.
The third-party app mode is not available for private deployments. In this mode the enterprise ID is neither typed nor typeable: the enterprise an integration belongs to is bound only through the WeCom QR confirmation.

Install the Flashduty app in WeCom

If your enterprise has never installed the Flashduty app, install it in the admin console first; skip this section if it is already installed.
  1. Visit WeCom Admin Console, go to App Management → Apps page, click Add Third-Party App. WeCom: Third-Party App Integration screenshot
  2. Enter Flashduty in the search bar, after finding the app, click Add. WeCom: Third-Party App Integration screenshot
  3. 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. WeCom: Third-Party App Integration screenshot
You can skip installing beforehand: choose Flashduty app not installed yet when saving the integration, and Flashduty opens the WeCom authorization page where a WeCom admin installs it.

Bind the enterprise by QR code in Flashduty

1

Create the WeCom integration

Go to Integration Center → New Integration, choose WeCom, select Third-party app (scan to install) as the Application version, and fill in Name.
2

Choose how to bind the enterprise

Pick one of the two options under How to bind your enterprise, depending on whether the enterprise has the app installed:
3

Scan and confirm the binding in WeCom

Click Save; a WeCom authorization dialog opens:
  • For “not installed yet”, click Open the WeCom authorization page and complete the authorized install as a WeCom admin. If you are not the admin, send the link in the dialog to your admin; the dialog continues automatically once the admin finishes.
  • For “already installed”, scan the QR code with the WeCom app, or send the link to any member of that enterprise to open in WeCom.
Once WeCom identifies the enterprise, the dialog shows “Found enterprise xxx. Waiting for Confirm to be clicked on the WeCom page…”. On the Confirm WeCom binding page opened in WeCom, check the Flashduty account, the requester and the enterprise, then click Confirm. The console saves the integration automatically; you do not need to click Save again.
After binding:
  • Enterprise ID becomes read-only and shows “Confirmed through WeCom and cannot be changed.”. Switching enterprises requires scanning again; there is no field to edit the ID directly.
  • A bind session is valid for 30 minutes and can be used once. After it expires the dialog says “The link has expired. Generate a new one.” — click Generate again and scan again.
  • When binding fails the dialog explains why: This enterprise has not installed the Flashduty app. Close this dialog, choose "Flashduty app not installed yet", and install it first. (the enterprise has no app but “already installed” was chosen), The binding was cancelled on the WeCom page. (Cancel was clicked on the confirmation page), WeCom did not complete the confirmation. Generate a new link and try again. (anything else).

Custom app integration

War Room and @ AI SRE in group chats work only in this mode, which is also the default Application version when you create a WeCom integration.

Create the integration and fill in the credentials

1

Create the app in the WeCom admin console

Visit WeCom Admin Console, go to App Management → Apps page, click Create App.WeCom: Custom App Integration screenshotConfigure App Logo, App Name, and App Visibility.WeCom: Custom App Integration screenshot
2

Fill in the enterprise ID, AgentId and Secret

Get Enterprise ID from the My Enterprise page and AgentId and Secret from the App Details page of the app you just created, then fill them in the Flashduty On-call integration configuration page.If your WeCom is a private deployment, also fill in Endpoint. The Flashduty service must be able to reach that Endpoint; you can set up whitelist authorization for it.
3

Fill in the access domain

Access Domain takes one domain only: no https://, no path, and no port when Flashduty hosts it, for example flashduty.example.com.After you save, connect this domain in step 1 of the detail page: add CNAME records so Flashduty issues the certificate and forwards traffic, or forward it with your own Nginx. WeCom requires the trusted domain and the callback URL to use this domain.
A private deployment has no hosting step: the access domain is your own Flashduty domain, and WeCom must be able to reach it over the public internet.
4

Save the integration

Click Save. The Token and EncodingAESKey for receive messages and for the smart robot are all generated by Flashduty; you do not fill them in when creating the integration, you generate them in the matching step on the detail page.After saving, the Finish setup in WeCom section on the detail page walks you through the rest.

Finish setup in WeCom

The detail page lists six steps in this order, numbered the same as this section. Steps whose outcome WeCom reports are ticked automatically; for the steps nothing reports back, click the confirm button inside the step once you have done it, which requires permission to edit the integration.
A private deployment has no step 1 (the access domain is your own deployment address), so the later steps shift down by one, and the verification file goes to the document root of your own server.

1. Connect the access domain

There are two ways to connect the access domain; pick one:
  • CNAME hosting (recommended): add CNAME records at your DNS provider. Flashduty issues the certificate and forwards traffic, so there is no server for you to maintain.
  • Forward it yourself: set up the certificate on your own Nginx or load balancer and forward every request for this domain to Flashduty. This is the only option when the domain is in use elsewhere and cannot be hosted.
Step 1 on the detail page selects CNAME hosting by default, and selects Forward it yourself once it finds your forwarding reachable.

CNAME hosting

Add the CNAME records shown in step 1 of the detail page at the DNS provider that hosts the access domain: Use the values shown on the page. The Certificate record proves the domain belongs to you, and Flashduty uses it to issue the HTTPS certificate through DNS-01 validation; the two access entry records route traffic to Flashduty, and one of them is enough. Which entry to use: the international entry wecom.flashduty.com (Hong Kong) is the default and works for any domain; if the domain has completed ICP access filing on Alibaba Cloud, you can use the mainland entry cn.wecom.flashduty.com instead for faster access inside China; if your DNS provider supports region-based resolution, configure both. A domain without Alibaba Cloud ICP access filing that points at the mainland entry is blocked by Alibaba Cloud. Once the records resolve and the certificate is issued, step 1 is ticked automatically and shows “Resolving · Certificate issued”. While records are missing it shows “N record(s) not resolving yet”; when every record resolves but the certificate is still being issued it shows “Issuing certificate”. Click Check again to read the state again.
If a status page or another Flashduty account already holds this domain, Flashduty cannot host it for this integration; step 1 shows “Domain in use” and goes straight to the forwarding config. If you would rather not forward it yourself, edit the integration and use a different access domain; if the domain really is yours, contact Flashduty support.

Forward it yourself

Requirements for forwarding it yourself:
  • A certificate issued by a trusted CA.
  • Every path of this domain forwarded to wecom.flashduty.com, with the original Host header kept. Flashduty identifies the integration by Host; when Flashduty adds or changes paths later, your config stays the same.
  • Both http and https forwarded, with no redirect: WeCom fetches the domain verification file over http.
  • If the domain has completed ICP access filing on Alibaba Cloud, you can forward to cn.wecom.flashduty.com instead for faster access inside China.
Below is an Nginx example. Step 1 on the detail page generates it for the integration’s access domain, ready to copy. Configure any other proxy or load balancer to the requirements above:
When done, click Check again: once https://<access domain>/ping answers pong, step 1 shows “Self-hosted proxy · Reachable”.

2. Set the trusted domain

On the app details page, go to Developer Interface → Web Authorization & JS-SDK, click Set Trusted Domain, and enter the access domain. See WeCom’s Enterprise Internal Development Domain Configuration Guide for the requirements. WeCom: Custom App Integration screenshot Then on that page click Request domain verification, download WW_verify_xxx.txt, and back in step 2 of the detail page click Upload verification file to upload it. WeCom fetches this file from the document root of the domain, and Flashduty serves it there (WeCom follows no redirect, so both http and https must serve it directly). Once WeCom has fetched it, step 2 is ticked automatically and shows “WeCom fetched the verification file”; while waiting for WeCom to fetch an uploaded file it shows “Waiting for WeCom to fetch it”, and before uploading it shows “Verification file not uploaded”. Back in WeCom, click OK to finish the verification. Fill the same domain into the OAuth2.0 web authorization callback domain on the same page.
WeCom requires the domain’s ICP filing entity to be the same enterprise or a related one (parent/subsidiary, head office/branch, and so on). If it is not, WeCom refuses to save and you can only use another domain or ask WeCom support to accept proof of the relationship.
When you forward the domain yourself, the step 1 config forwards /WW_verify_*.txt to Flashduty, so upload the file on the detail page as usual. For a private deployment, or if you serve the verification file from the document root of your own server instead, both http and https must serve it directly, with no redirect; once verification passes, click I’ve verified it to record the step.

3. Set up API message receiving

On the app details page, go to Receive Messages → Set API Receive, fill in the three items shown in step 3 of the detail page, and click Save: WeCom calls the URL immediately when you save. Once the verification passes, step 3 is ticked automatically and shows “Verified”; until then it shows “Waiting for WeCom to verify”.
Do not click Random generate in WeCom: use the Token and EncodingAESKey Flashduty generates, so both sides match.
Token and EncodingAESKey are shown only once and only a masked value remains after you leave the page, so copy them into WeCom right away. To replace them, click Generate again: the pair already saved stops working immediately, so any old value still in WeCom must be replaced and saved, otherwise callbacks stop arriving; it goes back to “Waiting for WeCom to verify” and is ticked again only after WeCom verifies the new pair. WeCom: Custom App Integration screenshot WeCom: Custom App Integration screenshot

4. Configure the trusted enterprise IP

At the bottom of the app details page, click Trusted Enterprise IP to configure it, then copy the whole IP line shown in step 4 of the detail page into it. On SaaS the line is 47.93.12.134;47.94.95.118;123.56.8.183;47.94.193.81;1.13.19.96, and every enterprise using Flashduty enters this same line; for a private deployment, enter the egress IP your Flashduty servers use to reach WeCom. WeCom only allows configuring the trusted IP after step 2 or step 3 is done. Step 4 is determined by Flashduty running one check against WeCom: a successful check shows “Active”; WeCom answering 60020 shows “Not set up”, meaning the trusted IP is still missing; any other error code is shown as WeCom returned it; an unreachable WeCom shows “Check failed”. Click Check again to read the state again. WeCom: Custom App Integration screenshot
The IP shown on the detail page is the correct egress IP only while no private Endpoint is set (that is, while Flashduty proxies the WeCom calls). If WeCom reports “the following IP belongs to a third-party service provider”, send a screenshot to Flashduty support. For a private deployment, enter the egress IP of your own Flashduty server.

5. Set the workspace app homepage

On the app details page, click set on Workspace App Homepage, choose Web page, and enter the address shown in step 5 of the detail page. A newly created integration has no separate “frontend trusted domain” to configure. WeCom does not report this setting back, so click I’ve set it after configuring it. WeCom: Custom App Integration screenshot

6. Create the smart robot (optional)

An optional step for @mentioning the smart robot in single chats and group chats to use AI SRE; see Configure the AI SRE smart robot for the details. Step 6 gives https://<access domain>/event/push/wecom/bot?integration_key=<integration_key>, and its Token and EncodingAESKey are likewise generated by Flashduty, shown once, and not interchangeable with the receive-message pair. The step is ticked automatically once WeCom verifies the URL.

Linked users

In the Linked Users tab of the integration detail page, filter members by All / Linked / Unlinked, or search by name or email. Click One-Click Link to match members to WeCom accounts by their phone number or email and link them automatically, the same result as a member logging into Flashduty from WeCom. Members receive WeCom notifications only after they are linked. If linking fails, verify that the member’s phone number or email matches their WeCom account.

Configure war room

War Room functionality is only supported in Custom App Integration mode.
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. Only one IM integration can have War Room enabled at a time; turn it off in the other integration first. See War Room.

AI SRE controls

Configure the AI SRE switch under Enhanced Features. It is enabled by default; see IM platform for what it does. The two WeCom app modes support different AI SRE entry points:

Configure the AI SRE smart robot

@mention the Smart Robot in a WeCom single chat or group chat to start an AI SRE investigation session without leaving WeCom. The Smart Robot can only be configured in Custom App Integration mode.
  • AI SRE must be enabled for your account, and Allow AI SRE conversations in IM must be on in the Flashduty WeCom integration (War Room is not required). Otherwise the robot does not respond to messages.
  • The callback URL is built from the Access Domain saved in the integration, so save the integration and its access domain first as described in Custom App Integration; only then does step 6 of the detail page show a usable URL.
The Smart Robot uses its own set of credentials (Token and Encoding-AESKey), different from the Receive Messages Token / EncodingAESKey in Custom App Integration. Mixing the two causes signature verification failures.
1

Create a Smart Robot in WeCom

In the WeCom app, open Workspace from the left sidebar and go to Smart Robot management. Create a new Smart Robot, select Manual creation, then Create in API mode.Have an internal company member create it: even with visibility set to all internal members, others only see the robot after the creator shares it.
2

Enter the callback URL

On the Smart Robot’s API configuration page, set the connection method to Use URL callback. Enter the URL shown in step 6 of the Flashduty WeCom integration detail page. Its format is:
WeCom sends a GET request to this URL for verification; Flashduty answers it automatically. Once the verification passes, step 6 of the detail page is ticked automatically.
3

Generate the Token and Encoding-AESKey

In step 6 of the detail page, click Generate and show to generate the Token and EncodingAESKey, and enter both values together with the URL above on the Smart Robot’s API configuration page, then save.Do not click “Random generate” in WeCom: both sides must use the same pair Flashduty generated.The plaintext is shown only at generation time; afterwards only a masked value remains. Clicking Generate again makes the previous pair stop working immediately: replace the old values in WeCom, save, and verify the callback URL again (the step is ticked again only after that verification passes).
WeCom does not automatically add the Smart Robot to a War Room group after the War Room is created. To use AI SRE in the War Room, manually add the Smart Robot to the corresponding group chat.

How to use

Once configured, @mention the Smart Robot in a WeCom single chat or group chat and type a question or incident description to start an AI SRE session. Supported message types:

FAQ

Check in order:
  1. Confirm that AI SRE is enabled for your account and Allow AI SRE conversations in IM is on in the integration.
  2. Confirm the integration_key in the callback URL exactly matches the value shown on the Flashduty integration details page.
  3. Confirm the Token and Encoding-AESKey entered in WeCom are the pair generated in step 6 of the detail page (Smart Robot), not the pair generated in step 3 (Receive Messages).
  4. Check the robot’s callback records in WeCom (if available) to see whether requests arrive and whether any error codes are returned.
  • Confirm that the Flashduty server is publicly reachable by WeCom servers and that the access domain is reachable: with hosting, the DNS records from step 1 must resolve and the certificate must be issued; when you forward it yourself, https://<access domain>/ping must answer pong.
  • Confirm that the Token and Encoding-AESKey entered in WeCom exactly match the pair generated in step 6 of the detail page.
  • Confirm that the integration_key parameter in the callback URL is correct and that the corresponding integration is enabled.
This usually means the Token or Encoding-AESKey is wrong. The Smart Robot’s credentials and the custom app’s Receive Messages credentials are two independent sets. Generate the matching set again in step 6 (Smart Robot) or step 3 (Receive Messages) of the detail page, enter the new values in WeCom and save, then verify the callback URL again.
  • Check if you’ve completed the app installation steps. For example, can you see the Flashduty On-call app in WeCom Workspace
  • A third-party app’s enterprise is set by a QR binding confirmation; scan again as described in Third-Party App Integration
  1. Login to WeCom client (desktop or mobile), go to Workspace, find and open the Flashduty app
  2. First entry requires login. Select your member account, after successful login with a password or SSO, Flashduty account and WeCom account will be linked
  3. Subsequent app access will be automatically passwordless
  1. Before sending notifications, account linking must be completed as described in the previous question
  2. Go to the specified channel, navigate to Escalation Rules → Personal Channel, select WeCom as notification method
  3. 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.
WeCom: How to send incident notifications? screenshot
  • Click card message to go directly to alert details page
  • Click Start Processing to directly set alert to Processing status
  • Click Close Directly to directly set alert to Closed status
  • 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
Due to WeCom limitations, after one card interaction, it can only be updated once within 72 hours. Each button operation counts as one interaction.When alert status changes, Flashduty On-call requests to update card content. When alert status changes frequently, cards may not update in real-time due to exceeding update limits. You can click the Refresh button to manually get one card status update opportunity.
Contact Flashduty customer service or your dedicated technical support to purchase and enable the license.
See the FAQ section in War Room documentation.
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.
On Mac, WeCom opens links in its built-in browser by default. Press ctrl + command + shift + d to enable debug mode, then select Debug → Browser, WebView Related → Open Webpage with System Browser. Press the same shortcut to leave debug mode; the setting stays.