Skip to content

Create a Data Collector ​

How It Works ​

The backend Data Connectors page (under the "Platform Management" group) lists all current connectors. Each connector has:

  • Connector Type: Currently only supports "WeCom Conversation Archive"
  • Status: Running / Syncing / Error
  • Last Sync: Time of last successful pull

Click to enter the detail page with four tabs:

TabContent
ConfigurationConnector's basic parameters (credentials encrypted, displayed as ●●●●●●)
Run LogsEach sync's time, trigger method (manual/scheduled), status, messages pulled, new groups, new members, duration
Group Chat ListAll synced group names + group conversation IDs + last update time
User ListAll synced member names + user IDs + last update time

Creating a WeCom Conversation Archive Connector ​

You need two sets of credentials—one for pulling messages, one for retrieving group names/contacts:

Create Wecom Collector
Basic Information

Choose an easily identifiable connector name (e.g., "Sales Customer Group Archive") + optional description.

Session Archive Credentials

Get the "Corp ID" from WeCom Admin Console → My Enterprise → Enterprise Info;
Get the "Conversation Archive Secret" from Admin Tools → Conversation Content Archive, configure public key to get "Public Key Version" and your maintained "RSA Private Key."
This credential set can only decrypt pulled conversation content—it cannot look up group names or member names.

Group Chat and User Information Credentials

Create a self-built app in WeCom → get the Secret from app details → authorize the app in "Customers & Partners → Customer Contact → API."
This Secret is used to get "external customer group names, owners, member lists" and "enterprise directory."
If not filled, message parsing can only retrieve group IDs and user IDs (numeric strings), without displaying group names and member names.

Synchronization Schedule

WeCom conversation archive uses "full pull"—the first sync automatically captures all external customer group IDs + group names + directory members. Subsequent syncs follow the system's default incremental schedule.

i
Why two credential sets: WeCom separates "conversation content" and "directory information" across different APIs with separate permission models. The Conversation Archive Secret is an enterprise-level dedicated key, independent of regular app Secrets. Missing either one means incomplete functionality.