WeCom CLI tutorial: track a support follow-up as a todo
Check authorization and create/read back one fictional support follow-up in WeCom.
Use caseClassify support messages, route reviews, and hand off tickets
Use the WeCom team CLI to create a follow-up after an internal support request is confirmed. Check account access first; the CLI does not monitor WeChat or read customer chats.
Source · WecomTeam / wecom-cli · Open-source walkthrough
Problem
Section titled “Problem”A repair request or internal support task can disappear in a busy group. The WeCom CLI exposes enterprise todo and other authorized operations to an agent. Start by turning one sanitized example into a task with an owner and due date.
Before you begin
Section titled “Before you begin”- Windows, macOS or Linux, Node.js 18+, a WeCom Bot and the required permissions. The official CLI is MIT-licensed.
- Company size and admin grants affect available operations. Check current project notices and the account scope; do not pass customer chats directly to the CLI or an external model.
Sources
Section titled “Sources”
Documentary-style scene of a support teammate checking one follow-up task; GPT-generated with a blurred generic screen, not a WeCom screenshot.
1. Install the official CLI and Skill
Section titled “1. Install the official CLI and Skill”Follow the official README to install @wecom/cli, then install the wecomcli-todo Skill in a compatible agent.
2. Run the Skill’s authorization checks first
Section titled “2. Run the Skill’s authorization checks first”Use the Skill to complete its shared prerequisite and authorization checks. Before any todo action, read its full references/todo-create.md guide and confirm what this account can access.
3. Create a fictional follow-up
Section titled “3. Create a fictional follow-up”Give the agent a fictional, sanitized test task with an owner and due date. Let the Skill follow the documented parameters; review the proposed details before confirming the write.
4. Read it back before daily use
Section titled “4. Read it back before daily use”Query the new todo and verify its title, owner, due date and status. Only then consider internal use. Redact customer details and have an employee confirm them first.
Check the result
Section titled “Check the result”Check authorization and create/read back one fictional support follow-up in WeCom.
- The authorized account and its enabled scopes are clear.
- A fictional todo can be created and read back with the expected owner and date.
- Customer chats are not sent to an external service without redaction and approval.