Slack overview

With Slack connected, FlowState sends deal alerts from its daily pipeline sync:

Overdue deal alerts — a message for each open deal that is past its close date.
Weekly digest — every Monday, one message per deal owner that lists their stalled or inconsistent deals.

For each alert type you choose where it goes: to the deal owners as direct messages (the default), to one channel, or nowhere. See Slack notifications.

FlowState also sends one direct message to the person who connected HubSpot when the first HubSpot sync finishes, and a test message when you click Send test message.

What Slack does not do

Slack only receives messages. You cannot ask FlowState questions in Slack, and FlowState does not respond to slash commands. To ask questions in plain language, use an AI assistant through MCP.
FlowState does not read Slack messages, reactions or files.
Account, billing, membership and APN notices are sent by email only. See Notifications.

Your own Slack app

FlowState uses a bring-your-own-app model. You create a small Slack app in your own workspace from settings FlowState gives you, enter its Client ID and Client Secret in FlowState, and approve it in Slack. See Connect Slack.

Permissions in Slack

The Slack app asks for these bot scopes:

Scope	Used for
`chat:write`	Posting the test message and the deal alerts.
`channels:read`	Listing public channels in the channel picker, and checking a channel when you save it.
`groups:read`	The same for private channels that FlowState was invited to.
`im:write`	Sending direct messages.
`users:read`	Requested with the app; FlowState does not use it today.
`users:read.email`	Finding a person in Slack by email address: you for the test message, deal owners for their alerts, and the person who connected HubSpot.

FlowState can post to a channel only after it has been invited there: in the channel, type /invite @FlowState.