WeCom Approval Assistant

Problem

WeCom approval forms often combine templates, control types, required fields, and strict value formats. Manually collecting user input from chat and assembling it into a valid API payload is easy to get wrong, especially for time ranges, control values, and missing required fields. This skill helps OpenClaw turn natural-language requests such as 'submit a leave request' or 'file an expense claim' into validated, formatted approval data.

How It Works

The skill builds a structured workflow around the WeCom approval endpoints:

• Template discovery: uses list_templates and get_template to inspect available approval templates and field details.
• Control parsing: identifies control types such as Vacation, Money, Selector, Contact, File, and RelatedApproval, then extracts required fields.
• Natural language submission: extracts fields like leave type, time range, expense amount, and reason from a single user message.
• Value formatting: converts human-readable inputs such as 'from 8:00 to 17:00' or date ranges into the control values and timestamps expected by the API.
• Submission and lookup: calls submit_approval to create the approval request and get_approval_detail to query the result.

Boundaries And Notes

It requires a WeCom self-built app with valid credentials, visible scope, and configured approval templates. Different templates have different control types, which affects parsing and validation. Complex controls such as contacts, files, related approvals, and formulas should be checked carefully to ensure the submitted field values match WeCom's expected format.