WeChat Integration

This document explains how to complete WeChat channel connection and verification in the Flocks WebUI through iLink Bot QR-code login.

Procedure

1. Open the WeChat Integration Page

Go to "Messaging Integrations -> WeChat" in the Flocks WebUI.

2. Log In Through QR Code

In the "Account Credentials" area, click Scan QR Code to Log In to WeChat:

• The page generates a QR code.
• Scan the QR code with WeChat.
• After confirming login on the phone, Flocks automatically fills in the following fields:
  • Token
  • Account ID
  • baseUrl (also filled automatically if the account is routed to a regional node)

If the QR code expires, click "Refresh QR Code" to get a new one.

3. Save and Enable the Channel

After scanning succeeds, the WebUI automatically saves the credentials and enables the WeChat channel. Usually you do not need to manually copy and paste Token / Account ID.

If you fill in the configuration manually, make sure at least these fields exist:

• Token: iLink Bot Token
• Account ID: iLink Bot Account ID, usually in the form xxx@im.bot

4. Configure Message Policies

Adjust the following configuration items as needed:

• Default Agent: which Agent is used when not explicitly specified
• Direct message policy:
  • Open: all direct messages can trigger the bot
  • Allowlist: only specified user_id values are allowed
  • Disabled: direct messages are not processed
• Group chat policy:
  • All: process all group messages
  • Allowlist: process only specified group / room IDs
  • Disabled: group messages are not processed

When a policy is set to allowlist mode, add:

• Allowed user IDs
• Allowed group IDs

5. Verify the Connection

After saving, verify it in one of these ways:

1. Send a direct message to the bot in WeChat.
2. Or send a triggerable message in an allowed group chat.
3. If Flocks replies normally, the WeChat channel is connected successfully.

Additional Notes

• To proactively send messages to WeChat from a Flocks page, Task Center, or Workflow, first establish a conversation binding and specify the target session_id.
• If QR-code login succeeds but messages cannot be sent or received, first check whether Token, Account ID, and baseUrl were saved correctly.
• In advanced configuration, sendChunkDelay controls the interval for sending long messages in chunks, and dataDir stores state files and media cache.

---

Related Resources: Messaging and alerting integrations overview | WeCom integration | Feishu integration | DingTalk integration | Slack integration | Telegram integration | WhatsApp integration | Email integration configuration