Connecting an IM tool used to mean creating an app in its admin console, copying credentials, and setting callback addresses by hand. Between October 16 and 19, Feishu, DingTalk, and WeCom moved most of that work to a QR code scan, and members no longer link their IM accounts one by one.
Feishu: scan to create a Flashduty-managed app
A new Feishu integration offers Create a new app (recommended) or Use an existing app. After you save, scan the QR code in Feishu. Flashduty creates or takes over the app in your Feishu tenant, configures events, callbacks, and permissions, and publishes a version. Flashduty keeps the credentials, and the detail page shows the App ID, the current version, and its status.
Feishu needs two admin approvals, one for the app and one for the configuration version. The detail page and the integration list show where it stands, such as Pending admin review (1/2), recheck every 10 seconds, and offer Copy message for admin to send the request to your Feishu admin.
An integration set up with manually entered credentials can switch with Switch to Flashduty-managed on its detail page. Lark, custom Feishu addresses, and on-premises deployments still use Enter credentials manually.
DingTalk and WeCom
- DingTalk: Create a DingTalk app by scanning (recommended) creates the app in Stream mode and the integration in one step.
- WeCom third-party app: Third-party app (scan to install) binds your enterprise by scan, whether or not it has already installed the Flashduty app.
- WeCom self-built app: enter your Access domain, and the detail page lists the DNS records to add. One record delegates certificate validation, so Flashduty issues and renews the HTTPS certificate for the domain. The other points the domain at Flashduty:
cn.wecom.flashduty.comfor mainland China orwecom.flashduty.comelsewhere, and either one is enough. Then Upload verification file to upload theWW_verify_xxx.txtfile from WeCom, and Flashduty serves it at the domain root. You don't need your own reverse proxy or certificate. A domain already used by a status page or another Flashduty account can't be hosted, and on-premises deployments keep their own setup.
Each integration's detail page lists the remaining setup in numbered steps, under Finish setup in Feishu, Finish setup in DingTalk, or Finish setup in WeCom.
Members link to IM accounts automatically
After a Feishu, DingTalk, or WeCom self-built integration is saved, Flashduty links members right away and then checks for new members every hour. It looks up each member's IM account by the verified phone number or email in their Flashduty profile: Feishu uses both, DingTalk uses the phone number, and WeCom tries the phone number first and then email. Members don't need to do anything. Try link on the detail page reruns it immediately. Feishu and DingTalk got this on October 16, and WeCom self-built apps on October 19.
Microsoft Teams page
The Teams integration page has a Notification targets card that lists the teams and chats receiving notifications. Each entry can be unlinked, and Unlink me removes your own link.
Get started
Go to Flashduty console → Integrations → Instant messages and add a Feishu, DingTalk, or WeCom integration.
Product docs: Feishu/Lark, DingTalk, WeCom, Microsoft Teams.