What problem does it solve?
Setting up the awada channel so an external-facing crew (like sales-cs) can communicate with outside users as a WeCom (Enterprise WeChat) contact involves editing openclaw.json, installing dependencies, and restarting the Gateway correctly. This Skill turns that into a repeatable SOP, avoiding misconfiguration and routing-cache pitfalls.
Core Features & Use Cases
- Guided SOP: Step-by-step procedure covering dependency checks, config merging, Gateway restart, and verification.
- Automated Config Merge: A script merges the awada channel and customerDB hook into ~/.openclaw/openclaw.json with atomic writes and timestamped backups.
- Troubleshooting Checklist: Covers common failures such as missing 'ws' module, 401 relay errors, lane mismatches, and binding routing issues.
- Use Case: When a user asks to enable sales-cs for external customer contact, run this Skill to prompt for the awadaKey, write the config, restart the Gateway, and verify message flow end to end.
Quick Start
Ask the agent to enable the awada channel for sales-cs and follow the prompts to enter your awadaKey, then approve the Gateway restart.