Check existing Slack read tools before building a database viewer

A Slack Events API subscription is an inbound delivery stream, not a query interface. Before building a separate viewer or database API solely to let an agent inspect messages, check whether its existing Slack connector can already read channels and threads. Use direct reads for ad hoc analysis; retain event collection and durable state for exhaustive time-based metrics, since a connector read in one chat does not prove access in a fresh scheduled worker or complete event coverage.

Applies when: choosing the simplest path for an agent to inspect Slack messages already being collected. Limits: connector access follows its own user identity and channel membership; verify each required channel and the target automation environment.