Channels and Integrations
Request-path behavior for inbound messaging plus the documented Slack scope diagnosis rules.
Inbound processing
The runtime is built around inbound signals landing on the webhook path, being verified, persisted, and processed immediately.
Key implication: if a user reports that "the agent did nothing," inspect the webhook path first, not only the UI.
Slack scope diagnosis
When Slack attachment ingestion or private file download fails, the first response should not be generic implementation advice. The diagnosis should map directly to missing scopes.
Scope guidance
| Failure mode | Scope to suggest first |
|---|---|
| Private file metadata or downloads fail | files:read |
| Assistant thread title or status features fail | assistant:write |
Only suggest extra scopes when the product already uses the corresponding capability.
Operational stance
- Keep request-path logs concise.
- Tie every scope recommendation to a concrete missing capability.
- Prefer explicit failure explanations over speculative code changes.
Integration checklist
- Verify the webhook endpoint is reachable.
- Confirm auth headers and signatures are present.
- Check whether the failure is metadata access, file download, or a capability-specific action.
- Suggest the minimal Slack scope that matches the actual missing permission.