awada-channel-setup

Configures the awada channel in openclaw.json to connect external-facing crews via WeCom contacts.

8.5k|1.4k|Updated Apr 24, 2024
One-click install
npx skills add https://github.com/TeamWiseFlow/wiseflow --skill awada-channel-setup
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: awada-channel-setup
Source: https://github.com/TeamWiseFlow/wiseflow/tree/main/crews/it-engineer/skills/awada-channel-setup
Command: npx skills add https://github.com/TeamWiseFlow/wiseflow --skill awada-channel-setup

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires ws, zod, and includes scripts (resource) components.

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.

Frequently Asked Questions about awada-channel-setup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enable the awada channel for sales-cs in OpenClaw?

Run the awada-channel-setup script, which reads the sample config, prompts for your awadaKey and optional lane, and merges the channel and customerDB plugin settings into ~/.openclaw/openclaw.json. Then restart the Gateway to apply routing changes.

How do I configure WeCom contact messaging for an external-facing crew?

Use the awada channel, which lets a crew like sales-cs appear as a WeCom contact to external users. The setup script writes the channel config with your relay-issued awadaKey and enables the customerDB hook to log customer visits automatically.

Why do I get 'Cannot find module ws' when starting the awada plugin?

This error means the awada runtime dependencies (ws and zod) were not installed. Fix it by running pnpm install --prod inside the awada directory of your wiseflow project root, then restart the Gateway.

Why are messages still routed to the default agent after configuring a binding?

Binding entries must include an accountId field, using "*" as a wildcard. Also, hot-reload does not reset routing caches, so a full Gateway restart is required after changing bindings or channel routes.

What credentials does the awada channel need?

The client only needs an awadaKey issued by the relay admin with the awada:lane:<laneId> scope. The relayBaseUrl defaults to the official relay domain, and the platform is bound by the lane on the relay side, so the client does not send it.