Slack action

The Slack action sends a message to a Slack channel. It can also send a direct message to a person by email. The action uses an organization Slack OAuth connection. It can use a supplied channel, a default channel, or the recipient information for a direct message. The Slack bot must have permission to post in the destination channel. A disconnected or expired connection stops the action from running.

Slack is a supported runtime action. The agent Actions page does not show it as a standard card, and it has no configuration form there. Do not tell teammates to enable a Slack card, because they cannot see one. Set up and maintain the organization connection through the relevant integration or channel workflow. Then check the behavior in the channel where you want to use it.

This action is the fire-and-forget outbound path. Slack Connect mode replaces it. When an agent runs in Connect mode, the dashboard disables outbound posting and shows a notice on the Outbound tab. The agent replies to customers in their shared channel instead, and it escalates through the Inbox. Do not plan an outbound notification for an agent that runs in Connect mode.

Slack is high risk. In widget chats with action approval enabled, the visitor must approve the action before a Slack tool call runs. The system does not automatically retry a failed message. This design avoids duplicate notifications, but a failed run needs investigation and a new attempt. Check the action log and the Slack connection state. Do not assume that the system delivered a message.