Ir al contenido
Comma Compliance Docs

WeChat and WeCom (WeChat Work) - Beta

Esta página aún no está disponible en tu idioma.

WeChat is two products. WeChat consumer is what individuals use. WeCom (WeChat Work) is the enterprise edition Tencent built for business communication, which has a server-side archive API and is what most regulated firms actually need to capture. Comma supports both, with WeCom as the primary integration path.

This integration is currently in Beta. The capture pipeline is shipped and validated with early customers; self-serve onboarding lands as we move out of beta.

What Comma captures from WeCom

Section titled “What Comma captures from WeCom”
  • 1:1 chats and group chats among enterprise users
  • File and image attachments
  • Reactions and edits where the WeCom API exposes them
  • External (consumer-WeChat) messages routed through the WeCom external contacts feature
  • Full metadata (sender, timestamps, conversation context)

How the WeCom integration works

Section titled “How the WeCom integration works”

WeCom’s archive API uses RSA-encrypted server-to-server message envelopes. Comma’s WecomConnection:

  • Stores per-team enterprise credentials (corp ID, secret, agent ID) encrypted at rest
  • Generates and stores a versioned RSA key pair for decrypting the WeCom envelope
  • Polls the WeCom server-side message API on a schedule and decrypts envelopes in place
  • Captures messages directly into the Comma archive without a third-party relay

Per-team scoping means each Comma tenant has its own credentials and its own key versions - no cross-tenant key sharing.

Setup steps (beta)

Section titled “Setup steps (beta)”

While we’re in beta, setup is a Comma-side concierge step:

  1. Confirm your firm has an active WeCom enterprise tenant with archive-API access
  2. Open the WeChat card under Integrations > Organizational Integrations in your Comma dashboard
  3. Click Request setup to start the beta onboarding conversation with the Comma team
  4. Provide your WeCom corp ID, agent ID, and secret (transmitted via Comma’s secure key-exchange flow)
  5. Comma generates the RSA key pair and provisions the connection
  6. Capture begins; you can rotate the RSA key from the integration card

Roadmap

Section titled “Roadmap”

Once the team-scoped self-serve onboarding flow is fully shipped, you’ll be able to provision the WeCom integration end-to-end from the dashboard without the concierge step. Existing beta tenants will migrate seamlessly.

WeChat consumer

Section titled “WeChat consumer”

For consumer WeChat capture (regulated employees with personal WeChat accounts used for business), the path is BYOD device archival rather than the server-side WeCom API. Contact us to scope.

What’s next

Section titled “What’s next”