FAQ
How to Connect WinNexo with WeCom Channel Bot
Connecting WinNexo to a WeCom channel bot takes 3 steps and requires admin privileges:
Step 1: Enter Channel Management in WinNexo
Go to Agent → Channel Management, select WeCom from the IM system list, and click "Configure".
Step 2: Create a Self-built App in WeCom Admin Console
Follow the on-screen guide to the WeCom admin console (work.weixin.qq.com):
- App Management → Self-built → Create App — fill in app name (recommend using the same name as the agent), logo, and visibility scope
- Record the following credentials and fill them back in the WinNexo configuration dialog:
- Corp ID
- App AgentId
- App Secret
- Trusted IP (fill in WinNexo's outbound IP list)
- In the "Receive Messages" panel, configure Callback URL / Token / EncodingAESKey (auto-generated and displayed by WinNexo's config page)
- Enable permissions in WeCom admin console: "Send Messages", "Get Member Info", "Access Contact List"
Step 3: Complete the Binding
Return to the WinNexo configuration dialog and click "OK". The platform will verify the CorpId/Secret validity. Once verified, the Agent ↔ WeCom App one-to-one binding is complete.
User-side Pairing (each user needs to do this once on first use)
- WinNexo Personal Center → Channels → select "WeCom", the page displays a 6-digit pairing code (valid for 5 minutes)
- Open the corresponding self-built app chat in WeCom and send the pairing code as a message
- After successful pairing, the WeCom chat returns a "Binding Successful" card
If WeCom has "Only allow members to join via QR code" enabled, the pairing code page also provides a QR code — scan it to complete pairing.
Note: Each agent corresponds to one WeCom self-built app (one-to-one relationship), consistent with the DingTalk logic of "one agent corresponds to one bot".
WinNexo IM Channel Bot, IM Mobile Access, and IM Account Linking: Capabilities and Relationships
Here's a user-facing capability overview that explains the three features separately and clarifies their relationships:
WinNexo × WeCom: Three Capabilities, Don't Confuse Them
WinNexo's integration with WeCom is actually three independent things, each solving different problems. They can be used separately or in combination.
1. IM Account Linking (Solves "Who Can Log In")
In one sentence: Lets WeCom users log into WinNexo directly by scanning a code, without separate registration.
- Admin connects WeCom account system in WinNexo backend
- WeCom org structure can be synced to WinNexo user groups with one click, personnel changes auto-sync
- Users scan WeCom QR code to enter WinNexo, no extra password needed
Solves the identity authentication problem — "who are you, can you get in."
2. IM Mobile Access (Solves "Where to Use It")
In one sentence: Open WinNexo pages directly within WeCom, usable on mobile.
Two access methods (choose either):
| Method | Description | Best For |
|---|---|---|
| WeCom Mini App | Configure a mini app in WeCom admin pointing to WinNexo's URL; users click in the workbench to open | Unified entry point, feels like a native WeCom feature |
| Direct Browser Access | Click a WinNexo link in WeCom chat to open the H5-adapted page | Quick experience, no mini app configuration needed |
Solves the access entry problem — "which door to enter." Once opened, it's the full WinNexo mobile experience.
3. IM Channel Bot (Solves "Proactive Reach + Chat Anytime")
In one sentence: Each agent becomes a WeCom bot — you can chat with it directly in WeCom, and it can proactively push messages to you.
This capability includes two directions:
- Passive (Chat Entry): Send messages to the bot in WeCom, messages pass through to the WinNexo agent — essentially embedding WinNexo's conversation capability into the WeCom chat window. One agent corresponds to one WeCom bot.
- Active (Message Push): Scheduled task results, report outputs, etc. can be proactively pushed to WeCom conversations via the bot — no need to log into the web to receive notifications.
Binding Process: Admin goes to WinNexo "Agent → Channel Management", selects WeCom, follows the guide to create a self-built app in WeCom admin and fill in credentials. Once verification passes, the binding is complete. Users need to pair once on first use (send a 6-digit code) to establish the WinNexo User ID ↔ WeCom User ID mapping.
Solves the interaction method problem — "use it and receive results without opening the WinNexo page."
How They Relate
WinNexo × WeCom Integration
| Account Linking (Identity Layer) | Mobile Access (Entry Layer) | Channel Bot (Interaction Layer) | |
|---|---|---|---|
| Problem Solved | "Who are you" | "Where to enter" | "How to interact" |
| Specific Capabilities | WeCom QR login, org sync | Mini app/H5 pages, mobile adaptation | Bot chat, proactive push |
- Account Linking is the foundation: If WeCom users want to use the channel bot, they must first be identifiable — "which WinNexo user does this WeCom user correspond to." With account linking, this mapping exists naturally; without it, manual pairing is needed.
- Mobile Access and Channel Bot are independent: One opens a WinNexo webpage within WeCom (full functionality), the other chats directly with the agent in the WeCom chat window (lightweight interaction). You can use just one or both.
- All three configured = best experience: WeCom QR login → one-click mini app entry from workbench → daily conversations with bots and receiving push notifications in WeCom, forming a complete loop.
A Common Point of Confusion
"I can already open WinNexo in WeCom, why do I still need to set up a channel bot?"
Because these are two different usage patterns:
- Mobile Access = embedded a WinNexo webpage in WeCom, same functionality as the PC version, suitable for complex operations and viewing full reports
- Channel Bot = chat directly in the WeCom chat window, suitable for quick questions and receiving push notifications, without opening any page
Simply put: One is "moving WinNexo into WeCom," the other is "having the agent live in WeCom chat."
For the capability differences and limits across IM channels in channel conversations, Knowledge Base collection, and app connections, see IM Capability Comparison.