Slack troubleshooting

The test message fails

Send test message (or the MCP tool test_slack) sends a direct message to the Slack account with your FlowState email address. It never posts to a channel, so channel membership does not matter here. The page shows Slack’s error:

1. Could not find Slack user for <email> — nobody in the connected Slack workspace has that exact email address. Your FlowState and Slack email addresses must match.
2. Could not open DM — the Slack app is missing the im:write scope, or your Slack account does not accept direct messages from apps. See Missing scopes.
3. A connection error — try again. If it continues, check Slack’s status page.

Missing scopes

Symptom: Slack reports missing_scope when FlowState sends the test message or lists channels.

Cause: the Slack app is missing one of the six bot scopes: chat:write, channels:read, groups:read, im:write, users:read, users:read.email.

Fix:

1. On api.slack.com/apps, open your app → OAuth & Permissions → Scopes → Bot Token Scopes, and add the missing scopes.
2. In FlowState, click Disconnect on Settings → Integrations → Slack, turn Slack on again, and click Connect to Slack.

If your workspace limits which scopes apps may request, ask a Slack Workspace Owner or App Manager to allow the six scopes.

Deal alerts do not arrive

Symptom: the test message works, but overdue-deal alerts or the weekly digest do not arrive where you expect them.

Check, in this order:

1. Where the alert type goes. Open Where should alerts go? on Settings → Integrations → Slack. Off sends nothing. People sends direct messages to the deal owners, not to a channel. Channel posts to the channel shown.
2. Channel: FlowState is in the channel. Someone may have removed it. Type /invite @FlowState in the channel.
3. People: FlowState can find the owner. The deal owner’s HubSpot email address must be their Slack email address. If FlowState cannot find the owner, the message goes to the fallback channel, or is skipped when there is none. The owner may also have turned off Slack: overdue deal alerts or Slack: weekly deal digest in their notification preferences.
4. There is something to report. Overdue alerts are only for open deals past their close date, and the same deal is alerted at most once in 7 days. The digest is sent on Mondays, only to owners with stalled or inconsistent deals.
5. The daily sync runs. Alerts come from the daily pipeline sync, which runs only when the AI agent or Goals feature is on.

FlowState was removed from Slack

Symptom: the test message, the channel list or saving Where should alerts go? fails, although the page still shows Slack as connected.

Cause: someone removed the app in Slack. FlowState notices this only when a Slack request fails.

Fix:

1. Click Disconnect on Settings → Integrations → Slack.
2. Turn Slack on again and click Connect to Slack. Your saved app credentials are used.
3. Click Send test message.

You moved to a different Slack workspace

FlowState’s access works only in the workspace you connected. Disconnect, create the Slack app in the new workspace if it does not exist there, and connect again. Then invite FlowState to your alert channels in the new workspace and check Where should alerts go?.