Channels

Connect WeCom

Connect WeCom with a Smart Bot or a hosted account, choosing the method that fits your conversations.

Give your team an AI teammate inside WeCom. Buda connects through WeCom's Smart Bot over a long connection — employees message the bot in WeCom and Buda replies automatically, with no public webhook to host.

Choose a connection method

In Channels, click Add Channel and select WeCom. Under Connection method, choose:

  • Smart Bot to create a bot that members can message in WeCom. Use Scan to connect to create and connect the bot, or Enter manually for an existing bot.
  • Hosted Account to use a hosted WeCom account to participate in internal and external group conversations. Enter the App Key, App Secret, and account instance as described in the hosted account guide.

Connect the bot manually

Create a bot

In WeCom, tap Workbench, then open Smart Bot.

Open Smart Bot

Tap Create Bot → Manual Creation. On the creation page, scroll down and click Create in API Mode.

Switch to API mode

Configure the connection and copy credentials

On the API configuration page:

  1. Select Use Long Connection as the connection method.
  2. Copy the Bot ID.
  3. Click Click to Get to reveal and copy the Secret.
  4. Fill in the bot name, avatar, and visibility scope, then Save.

Configure connection and copy credentials

The Bot ID and Secret can be viewed again at any time — they aren't one-time values.

Add the channel in Buda

Open Settings → Channels, click Add Channel, and select WeCom. Choose Smart Bot under Connection method, then select Enter manually. Enter the Bot ID and Secret, optionally set a label and target agent, then click Connect.

Test it

Back in WeCom, find the bot you just created and send Hi. Once Buda replies, you're connected.

Smart Bot troubleshooting

SymptomFix
Bot not respondingRe-copy the Bot ID and Secret (watch for stray spaces); confirm the channel shows Active
Connection never establishesMake sure you selected Use Long Connection, not Use URL Callback
Secret compromisedRegenerate the Secret in the WeCom admin console, then update it in Buda's channel settings

Connect a hosted account

Use a dedicated WeCom account to send and receive messages as that account and participate in internal or external groups it is allowed to join. You or an authorized group member must invite the account first.

Contact us

Contact Buda to arrange your hosted account purchase and activation. Contact us to obtain an App Key, App Secret, and an available account instance.

Email hi@buda.im with your WeCom account and how you plan to use direct messages or groups.

Set up the hosted account

  1. Open your space's Channels settings and click Add Channel.
  2. Select WeCom, then choose Hosted Account under Connection method.
  3. Enter the App Key and App Secret provided by Buda. Click Verify and list accounts, then choose an Account instance and the target Agent.
  4. Click Connect and open Manage account connection to check the status. For an offline account, generate a login QR code, scan it with the matching account, and confirm login.
  5. Once Account connected appears, send a direct text message from another account and confirm you receive an Agent reply. To test a group, explicitly @mention the connected account.

Hosted account group conversations

Select the connected account from WeCom’s @mention picker and send text. Buda keeps the sender identity and returns the Agent's reply to the original group, without automatically @mentioning the sender.

Mentioning everyone, mentioning another member, or typing a nickname as plain text does not trigger a reply. Group messages without the account's mention are ignored and do not appear in the Buda session. Different groups and direct conversations have separate sessions.

Direct text and group text mentions are supported. Images, files, voice, contact management, and bulk messaging are currently unsupported.

Hosted account status and recovery

  • Expired QR code or offline account: generate a new QR code in Manage account connection and confirm login.
  • Missing account instances, invalid credentials, or a connection needing attention: contact us with the error shown in Buda.
  • Connected but no reply: check that the message is direct text or explicitly mentions the account in a group, then check the Buda conversation.
  • Unlinking removes the Buda connection and does not automatically log out the account. Contact us if you need to restore its other message receiver settings.

On this page