Slack notifications

FlowState sends two kinds of deal alerts to Slack. Both come from the daily pipeline sync.

Alert	When	Content
Overdue deal alert	Each day, for each open deal that is past its close date. The same deal is alerted at most once in 7 days.	Deal name with a link to HubSpot, owner, the missed close date, amount, and days since the last activity.
Weekly digest	Mondays, one message per deal owner with stalled or inconsistent deals. At most one per owner per week.	For each deal: name and link, amount, stage, close date, days inactive, the issues found and, where available, FlowState’s AI summary of what to do.

Slack is the only place these two alerts go; there is no email version.

Choose where alerts go

Open Settings → Integrations → Slack.

Under Where should alerts go?, choose one option for each alert type:

Option	What happens
People (default)	Each deal owner gets a direct message. You can also choose a Fallback channel (optional).
Channel	All messages of this type go to one channel.
Off	FlowState sends nothing for this alert type.

Click Save.

Result: the page shows Saved. If FlowState is not a member of a channel you chose, the save fails and tells you to invite it: in that channel, type /invite @FlowState. Only an owner or admin can change these settings.

With an AI assistant, use the MCP tools get_slack_notification_routing and set_slack_notification_routing. The alert types are deals.outdated (overdue deals) and deals.weekly_digest (weekly digest); the modes are people, channel and off; a channel is given by its Slack channel ID (for example C0123456789), not its name.

People: direct messages to deal owners

FlowState finds each deal owner in Slack by the email address of their HubSpot user. That address must also be their email address in your Slack workspace.
When FlowState cannot find the owner — the deal has no owner, the owner has no email address, or nobody in Slack has that address — it posts to the fallback channel. Without a fallback channel, it skips the message. A skipped overdue alert is tried again the next day; a skipped digest waits for the next Monday.
If Slack has a temporary problem with one person, FlowState skips only that person’s message.
Opting out. A deal owner who is also a FlowState user can turn the direct messages off in their notification preferences: Slack: overdue deal alerts and Slack: weekly deal digest. Then FlowState sends them no direct message and does not post their deals to the fallback channel either. The one-click unsubscribe in a mail app, which turns off every optional category, also turns these two off. Owners without a FlowState account cannot opt out in FlowState.

Channel: one shared channel

Every message of that alert type goes to the channel you chose. Personal opt-outs do not apply.
FlowState must be a member of the channel, public or private: type /invite @FlowState in the channel. A private channel is not visible to FlowState until you invite it.
The messages contain deal names, amounts and activity gaps. Choose a channel where everyone may see that data.

First HubSpot sync

When the tenant’s first HubSpot sync finishes or fails, the person who connected HubSpot gets an email and, when Slack is on and connected, a direct message with the same text: the number of deals imported, or the reason it failed.

This message always goes to that one person, never to a channel. The settings above do not apply.
FlowState finds the person in Slack by their FlowState email address. If nobody in Slack has that address, only the email is sent.
If the person turned off Your first HubSpot sync finished, FlowState sends neither the email nor the direct message.