AQI AIAQI AI Intelligence
⌕
Official documentationNot tested by AQI AI

WeCom capability map: mini programs, web and office

Choose by runtime; distinguish screenshot navigation, author examples and unverified API-specific permissions.

Last checked:
A quick glossary

Models generate and reason. Agents use tools to work on tasks. A harness manages an agent’s environment. MCP connects tools and data. Skills are reusable task guidance.

Implementation steps

  1. Mini programs: wx.qy and sessions

    Stage practice: WecomTeam examples cover login, user data, contacts/chat and NFC. Set a valid appid and select WeCom mode in developer tools. Relevant calls require wx.qy.login, a valid session_key and a member in app visibility. Obtain/cache production access_token server-side; do not copy the demo’s frontend token shortcut.

    Sources for this stage: WeCom · MiniProgramSample
  2. Web JS-SDK: identify the client environment

    Stage practice: User screenshots list ww.register/getSignature/checkJsApi, chat, sharing, files, audio, Wi-Fi/BLE and location. This verifies navigation only, not parameters, client versions, domain signing or permissions. Identify the actual WeCom runtime before checking an API; opening a chat does not imply reading history.

  3. Office AI: start with the official CLI

    Stage practice: The wecom-cli author lists messaging, mail, documents/tables, tasks, calendar, meetings, WeDrive and contacts, with interactive authentication. Start AI use with authorized reads and drafts, then enable writes individually. README features do not establish account rights; no installation, scan or write is performed here.

    Sources for this stage: WeCom · CLIWeCom · OpenClaw Plugin
  4. Customer contact, service and native apps: separate checks

    Stage practice: Screenshots also show customer groups/Moments, service, payments/refunds, approvals, school/government and live streams. Navigation does not prove unattended actions or customer-content access; certification, versions and quotas remain unverified. MobileSDK has native iOS/Android login/share examples, distinct from web JS-SDK; old samples are not current-version evidence.

    Sources for this stage: WeCom · MobileSDK

Validation checks

Recorded test results

Sources reviewed; no bot creation, message sending, enterprise authorization or end-to-end test performed.

Cost

Not verified

Price not verified; check software, model, API, hardware and hosting costs separately.

Original sources

  1. WeCom · MiniProgramSample ↗

    github.com · · Official documentation

  2. WeCom · CLI ↗

    github.com · · Official documentation

  3. WeCom · MobileSDK ↗

    github.com · · Official documentation

  4. WeCom · OpenClaw Plugin ↗

    github.com · · Official documentation

Connected resources

Chat platformsNot verified

WeChat AI integration: choose your route

WeCom AI bots, OpenClaw and public accounts are separate routes; author examples shorten the documentation search.

Community adaptation