WeCom Callback (Self-Built App)
WeCom Callback (Self-Built App)
Start with meaning, then move to detail.
This lesson explains WeCom Callback (Self-Built App) as part of getting started with Hermes correctly. You will learn what it does, when it matters, and the smallest safe test that proves it works.
If you are new, do not memorize names. Focus on three questions: what problem does this solve, what access does it need, and how can you verify the result?
For practice, inspect the first example, identify its effects, run it on test data, and compare the result with the source claim.
For advanced readers, inspect How It Works, Prerequisites, Setup, then verify failure modes and version compatibility.
No prior experience is required; follow the steps on a safe test setup first.
A clear outcome before you read.
- Understand WeCom Callback (Self-Built App) without assumed prior knowledge.
- Separate the source description from what still needs testing in your environment.
- Read the first command and identify its inputs and outputs before copying it.
Short definitions before the details.
- Gateway
- The process that connects Hermes to channels such as Telegram or Discord and routes messages.
What does the source say, and in what order?
- 01How It Works
Start here to understand the core idea or structure.
- 02Prerequisites
Read this after the foundation, then connect it to the previous step.
- 03Setup
Read this after the foundation, then connect it to the previous step.
- 041. Create a Self-Built App in WeCom
Read this after the foundation, then connect it to the previous step.
- 052. Configure Environment Variables
Read this after the foundation, then connect it to the previous step.
- 063. Start the Gateway
Read this after the foundation, then connect it to the previous step.
- 07Configuration Reference
Read this after the foundation, then connect it to the previous step.
- 08Multi-App Routing
Read this after the foundation, then connect it to the previous step.
- 09Access Control
Read this after the foundation, then connect it to the previous step.
- 10Endpoints
Finish here to verify the result and special cases.
Copy only after you understand the effect.
WECOM_CALLBACK_CORP_ID=your-corp-id
WECOM_CALLBACK_CORP_SECRET=your-corp-secret
WECOM_CALLBACK_AGENT_ID=1000002
WECOM_CALLBACK_TOKEN=your-callback-token
WECOM_CALLBACK_ENCODING_AES_KEY=your-43-char-aes-key
# Optional
# WECOM_CALLBACK_HOST= # optional pin; unset = dual-stack (all interfaces, IPv4+IPv6)
WECOM_CALLBACK_PORT=8645
WECOM_CALLBACK_ALLOWED_USERS=user1,user2hermes gatewayplatforms:
wecom_callback:
enabled: true
extra:
host: "0.0.0.0"
port: 8645
apps:
- name: "dept-a"
corp_id: "ww_corp_a"
corp_secret: "secret-a"
agent_id: "1000002"
token: "token-a"
encoding_aes_key: "key-a-43-chars..."
- name: "dept-b"
corp_id: "ww_corp_b"
corp_secret: "secret-b"
agent_id: "1000003"
token: "token-b"
encoding_aes_key: "key-b-43-chars..."Read the first command and identify its inputs and outputs before copying it.
Match every command to your installed Hermes version, review the files and accounts it can reach, and use non-sensitive data for the first test. If this explanation differs from the source, the official source wins.