Slack

The Slack plugin lets automations post messages to Slack channels, such as a daily catalog-quality summary or an alert when an order needs attention. It delivers messages only; the agent cannot read Slack conversations through it.

Connect

A project owner or developer connects Slack once for the project.

1. In Studio, open AI → Plugins and select Slack.
2. Choose Connect and sign in to the Slack workspace in the popup.
3. Review the requested permissions and approve them.
4. Confirm the Slack workspace under Connected accounts. Connect another account to deliver to a second Slack workspace.

Slack connections are project accounts; there is no personal Slack connection. Owners and developers can disable the plugin or revoke a connection in Dashboard → project → Integrations. See govern plugins.

Deliver from an automation

1. Open the automation and find Tools → Send to Slack.
2. Choose Add. If no account is connected yet, choose Connect there instead. Choose the Workspace when more than one is connected; otherwise the primary account is used.
3. Under Channels, select one or more channels.
4. Say in the instructions what to post and when, for example “post a summary of the records you changed”.
5. Run the automation manually against a test channel and check the message and the run details.

A connected account confirms authorization, not that every channel accepts messages. Channel membership and Slack policy can still block delivery.

Identity and access

A Slack identity and a Flexkit account are different identities. Membership in the Slack workspace does not grant access to project data, and channel members see only what the automation posts. Inspect roles and spaces when a Flexkit request is denied.

Troubleshooting

Check the connected Slack workspace, the channel’s access, the automation’s delivery settings and the run details. When the account shows Needs reconnect, choose Reconnect in AI → Plugins → Slack. Review dependent automations before disconnecting an account.

Keep provider tokens and customer conversations out of public support reports. To send data to your own receiver instead, use outgoing webhooks.