> For the complete documentation index, see [llms.txt](https://doc.duaer.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.duaer.com/integrations/builtin/credentials/wecom.md).

# WeCom credentials

Configure WeCom credentials in Duaer: self-built app API keys, group-bot Webhooks, and Token / EncodingAESKey for message receive.
## WeCom API (app messages, contacts, and more)

1. Open the [WeCom admin console](https://work.weixin.qq.com/) → My Company and copy Corp ID.
2. Open your self-built app under Apps, copy AgentId, then view and copy Secret.
3. In Duaer Credentials, create a WeCom API credential with Corp ID, Agent ID, and Secret. Requests go to qyapi.weixin.qq.com by default; set API Base URL only if you need a proxy.

Use this credential with [WeCom Base](/integrations/builtin/app-nodes/duaer-nodes-wecom.wecombase.md) for app messages, contacts, and media.

## Group bot Webhook

1. Add a group bot in a WeCom group and copy the Webhook URL.
2. In Duaer, create a WeCom group-bot Webhook credential and paste that URL.

## Message receive (triggers)

1. Enable API message receive on the self-built app and set Token and EncodingAESKey.
2. In Duaer, create a WeCom receive credential with Corp ID, Token, and EncodingAESKey.
3. Paste the trigger Webhook URL back into the WeCom admin receive URL. The Duaer instance must be reachable from the internet.

Refer to [WeCom message receive trigger](/integrations/builtin/trigger-nodes/duaer-nodes-wecom.wecomtrigger.md).
## Questions

### Where does Duaer store WeCom credentials?

In instance Credentials. Digital organizations reference the credential and do not embed the Secret in node parameters.

### When do I set API Base URL?

Leave it empty for the official API. Set it only when you reach WeCom through a proxy or private link.