WeChat Work Approval Notification Automation

Problem

WeChat Work approval workflows often get stuck on who should be notified, how timeout escalation works, and what happens when an integration fails. If these rules only exist in chat history, message templates and exception handling are hard to review or reuse. This skill targets office-efficiency scenarios in the China market and turns approvals, reminders, CCs, and external notifications into an actionable design.

How It Works

It starts with the initiator, approvers, CC recipients, and timeout escalation owner, then makes assumptions about available APIs or bot capabilities. It maps the full initiate, approve, reject, pass, and timeout state flow, defines trigger conditions, recipients, and message templates for each state, and marks actions that require human confirmation, such as writes, deletions, or external commitments. It also specifies idempotency, retry, deduplication, logging, and test cases for normal, rejected, timed-out, and API failure paths.

Boundaries

When business details are missing, it lists gaps first and avoids inventing platform capabilities, metrics, or qualifications. Actions involving account writes, publishing, deletion, charges, or external commitments require explicit confirmation. The output is closer to workflow design and acceptance criteria, not a WeChat Work API implementation.