Use when installing or configuring OpenClaw with DingTalk, Feishu, Discord, and additional channels with Bailian/DashScope models on Linux hosts. Use when provisioning a new OpenClaw node, troubleshooting gateway/channel startup, standardizing openclaw.json mapping, or automatically discovering extra channels from https://docs.openclaw.ai/channels.
Deploy OpenClaw on Linux, enable DingTalk, Feishu, Discord, or other documented channels, and verify gateway health.
Run this sequence in order:
~/.openclaw/openclaw.json.AppKey, AppSecret) for the official connector, or Feishu app credentials (App ID, App Secret), or Discord bot token.ssh root@<server>
curl -fsSL https://deb.nodesource.com/setup_20.x | bash -
apt-get install -y nodejs
node --version
npm --version
npm install -g openclaw@latest
openclaw --version
# DingTalk official connector
openclaw plugins install @dingtalk-real-ai/dingtalk-connector --pin
# or install from official GitHub repo
openclaw plugins install https://github.com/DingTalk-Real-AI/dingtalk-openclaw-connector.git
openclaw plugins list | grep dingtalk
# Feishu channel
openclaw plugins install @openclaw/feishu
openclaw plugins list | grep feishu
# Discord channel (built-in, no extra plugin needed)
# Configure token in Step 3 and start gateway in Step 4
If upgrading from old DingTalk plugins, uninstall legacy plugin IDs first and keep only the official connector in plugins.allow.
When user asks for any extra channel beyond current setup, do this first:
https://docs.openclaw.ai/channels/index.~/.openclaw/openclaw.json.Use the exact workflow in references/channel-discovery.md.
openclaw.jsonCreate or update ~/.openclaw/openclaw.json with:
models.providers.bailian for DashScope endpoint and models.agents.defaults.model.primary in provider/model format, default to bailian/glm-5.models.providers.bailian.models ordered as:
qwen3-plusglm-5minimax-m2.5kimi-k2.5agents.defaults.model.fallbacks ordered as:
bailian/qwen3-plusbailian/minimax-m2.5bailian/kimi-k2.5channels.dingtalk-connector, channels.feishu, or channels.discord credentials and policy.plugins.allow including installed channel plugins.Important:
~/.openclaw/agents/main/agent/models.json can override ~/.openclaw/openclaw.json.api: openai-completions -> use https://dashscope.aliyuncs.com/compatible-mode/v1api: openai-responses -> use https://dashscope.aliyuncs.com/api/v2/apps/protocols/compatible-mode/v1Use the full template in references/config.md. Use DingTalk field mapping in references/dingtalk-setup.md. Use Feishu setup and field mapping in references/feishu-setup.md. Use Discord setup and field mapping in references/discord-setup.md. Use channel discovery workflow in references/channel-discovery.md.
openclaw gateway install
openclaw gateway start
openclaw gateway status
If running with user-level systemd, reload after config changes:
systemctl --user import-environment DASHSCOPE_API_KEY
systemctl --user daemon-reload
systemctl --user restart openclaw-gateway
openclaw doctor
openclaw gateway status
openclaw gateway logs -f
Common failures:
plugins.allow.agents.defaults.model.primary format (provider/model-id).models.providers.bailian.apiKey and DASHSCOPE_API_KEY imported in systemd.~/.openclaw/agents/main/agent/models.json.openai-completions vs openai-responses) and clear stale session if needed.openclaw logs --follow and check gateway/channels/dingtalk-connector lines for stream reconnect or credential issues.mkdir -p output/aliyun-openclaw-setup
echo "validation_placeholder" > output/aliyun-openclaw-setup/validate.txt
Pass criteria: command exits 0 and output/aliyun-openclaw-setup/validate.txt is generated.
output/aliyun-openclaw-setup/.