Track 2 — Builder 构建 · M7 · 40 min · Live today
Adapters and execution honesty
Telegram, Gmail, signed Webhooks (HMAC-SHA256), WeChat and BSC. With no live adapter, the run halts as BLOCKED — it never pretends.
Prerequisites: M6 · Dynamic tool registry + scope enforcement (W1/W2)
After this module you can…
- Connect one adapter and read a delivery log.
- Describe what happens when no live adapter exists.
Key points
- Every delivery attempt writes a log row with status and error text.
- Webhook payloads are signed with HMAC-SHA256 so receivers can verify origin.
Hands-on exercise: One real delivery
- Connect Telegram or Gmail with your own credentials.
- Run a skill that delivers, then open the delivery log.
- Disconnect it and re-run to see the BLOCKED halt.
Evidence of success: One successful log row and one BLOCKED run.
Knowledge check
Getting it wrong is fine — the explanation tells you why.
1. What happens with no live adapter configured?
2. How does a webhook receiver know the call is from AiXin?
Module 7 of 20 · progress is stored on this device.