Slack
Source-reviewed capability blueprint for Slack: Send workflow updates from Hoop to people or channels in a connected Slack workspace. Confirm Hoop availability before setup.
This source-reviewed capability blueprint describes expected behavior and vendor requirements. It does not confirm that Hoop has enabled this connection for your account.
Overview
This profile describes the expected connection path if it is enabled in Hoop. A Hoop workflow can send a direct message or post to a public or private Slack channel. The documented connection is outbound, so Slack activity does not automatically update Hoop.
Expected data flow
Hoop workflow to Slack
Expected when enabled: A workflow event can send a direct message or post to the selected public or private Slack channel.
Expected capabilities
- Expected when enabled: Send direct messages from workflows
- Expected when enabled: Post alerts to public channels
- Expected when enabled: Post operational updates to approved private channels
Expected setup
- 01
Expected setup step when enabled: A Slack workspace
- 02
Expected setup step when enabled: Permission to connect the workspace
- 03
Expected setup step when enabled: A selected recipient or channel in the workflow action
Expected requirements and limits
- Expected constraint for this path: No inbound Slack event flow is documented for this action.
- Expected constraint for this path: This is documented as a Premium Workflow Action, so execution charges can apply.
- Expected constraint for this path: Private channel access depends on the permissions granted to the connection.
- Authentication
- Expected authentication if this path is enabled: Connect the Slack workspace and approve the workspace permissions requested during setup.
- Account requirements
- Setup assumptions only; confirm Hoop access first. A Hoop plan that includes the Slack workflow action. Usage charges can apply to premium workflow executions.
Sources
The linked sources and profile copy were reviewed on Aug 9, 2026. These sources document the connected service's rules and APIs; they do not confirm that the connection is enabled in Hoop or in a particular account. The next source review is due Nov 9, 2026.
