Integrating Openclaw with WeCom (Enterprise WeChat)

Feb 27, 2026 · 3 min read · 529 Words · -Views -Comments · AI Tutorials

At work we use WeCom (Enterprise WeChat), so I wanted to integrate Openclaw into it. For client-facing communication, regular WeChat is more common, but unfortunately WeChat itself doesn’t offer a bot mechanism. So for now I’m not considering external use — just internal efficiency first. WeCom does have both bot and app mechanisms, meaning you can configure various bots.

Installing Openclaw

This is still a one-liner — just make sure your Node version is 22+.

# nvm
curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.40.4/install.sh | bash

# Install Openclaw
curl -fsSL https://openclaw.ai/install.sh | bash

Openclaw WeCom Plugin

Someone in the community has already contributed a plugin, so just use it directly. Note that the official Openclaw site doesn’t have WeCom integration docs yet — I saw a related PR but it hasn’t been merged. So for now, just follow the plugin’s instructions.

openclaw-wecom-plugin

# Install the plugin
openclaw plugins install @creatoraris/openclaw-wecom

Plugin Configuration

{
  "plugins": {
    "entries": {
      "openclaw-wecom": {
        "enabled": true,
        "config": {
          "token": "your_token",
          "encodingAESKey": "your_encoding_aes_key",
          "corpId": "your_corp_id", // optional
          "port": 8788 // Openclaw default port
        }
      }
    }
  }
}

Note: You need to restart Openclaw for config changes to take effect. Use openclaw gateway restart.

WeCom Bot / App

The token and other parameters in the config above need to be obtained after creating a bot or app in the WeCom admin console. Here are the steps:

  1. You can create one directly within WeCom. But watch out — for example, if you try to create a bot under your company’s organization, you might get an error saying the callback URL must be an intranet domain. In other words, the bot address is restricted by the admin. Keep this in mind.
  2. Fill in the required callback URL and bot information as needed.

Complex Deployment — One-Click Deploy?

The deployment above can be somewhat complex. If you don’t want to handle it yourself, consider some turnkey deployment options from Chinese cloud providers. They’re basic but functional. For example, Tencent Cloud, or Alibaba Cloud which offers similar products.

Pros and Cons of Bots

Here are the downsides of WeCom bots I’ve noticed so far:

  1. No slash command support
  2. No support for rich text like images — text only, which is quite limited.

On the plus side, bots can be added to group chats, making it convenient to interact with multiple bots in one group.

Pros and Cons of Apps

I haven’t had the need to use apps yet, but here’s what I’ve learned. The downside of apps is they can’t be added to groups — only direct messages. The upside is they support some rich text message formats like images. Also, you can connect WeChat to communicate with individual users via WeCom Admin Console -> My Enterprise -> WeChat Plugin -> Scan QR with personal WeChat. Give it a try if you’re interested.

Final Thoughts

Overall, using Openclaw with WeCom works, though the experience is just okay. The core really comes down to the AI model. I’d recommend connecting GPT, or at minimum try MiniMax. As for Tencent’s Yuanbao — not great. Lastly, neither WeCom bots nor apps support slash commands, which feels a bit behind. Hopefully future updates will address this.

Authors
Developer, digital product enthusiast, tinkerer, sharer, open source lover