Slack 自动回复 missing_recipient_team_id：先验证入站上下文再放量
问题/场景：Slack 手动发送正常，但入站消息自动回复失败并报 `missing_recipient_team_id`。前置：已配置 Slack bot/app token，且有频道权限。实施步骤：先用最小配置验证自动回复路径，再检查事件来源上下文字段是否完整，最后恢复生产配置。关键命令：`openclaw gateway status`、`openclaw logs --follow`。验证：入站消息能稳定触发自动回复。风险：仅验证“可发消息”不足以代表“可自动回复”。来源：GitHub issue + Slack 集成经验归纳。
GITHUBDiscovered 2026-02-20Author AndyPorkbelly
Prerequisites
- Slack bot token, app-level token, and event subscriptions are enabled.
- You can observe gateway logs in real time.
Steps
- Create a minimal Slack test channel and send one inbound message to isolate variables.
- Tail logs and verify whether inbound event contains team/workspace identifiers expected by reply path.
- If missing, re-check Slack app scopes/events and reconnect integration, then restart gateway.
- Run 3-5 inbound message tests (DM + channel) before restoring full automation.
Commands
openclaw gateway statusopenclaw logs --followopenclaw gateway restartVerify
Inbound Slack messages consistently receive auto-replies without `missing_recipient_team_id` errors.
Caveats
- Socket mode and webhook mode can behave differently; test both if you use both.
- The exact missing field path depends on provider payload version（需验证）.
Source attribution
This tip is aggregated from community/public sources and preserved with attribution.
Open original source ↗