Communication integrations keep your team informed without requiring them to check the CauseFlow dashboard constantly. When incidents are created, investigations complete, or approvals are needed, CauseFlow sends notifications to your connected communication tools in real time. CauseFlow supports Slack and Microsoft Teams via OAuth through CauseFlow’s managed integration layer. Token lifecycle (authorization, refresh, and secure storage) is handled for you so delivery is always reliable.Documentation Index
Fetch the complete documentation index at: https://docs.causeflow.ai/llms.txt
Use this file to discover all available pages before exploring further.
Slack and Teams integrations support both directions: outbound notifications (incident alerts, investigation updates, approval requests) and inbound event triggers (messages that open or enrich incidents). Inbound triggers are in progress — outbound notifications are available today; inbound message-trigger support ships in a subsequent release.
How it works
Both integrations use a bot account that CauseFlow provisions in your workspace. The bot posts messages to the channels you designate for each notification type. You control which channel receives which notification type from the CauseFlow dashboard.Slack
How it works
CauseFlow connects to your Slack workspace via OAuth and provisions a CauseFlow bot. The bot posts notifications to channels you designate in the CauseFlow dashboard. You can route different notification types to different channels.Required information
| Item | Description |
|---|---|
| Slack workspace | The workspace where you want to receive notifications |
| Channel selection | Which channels receive each notification type |
Bot scopes requested
CauseFlow requests the minimum Slack bot scopes needed:| Scope | Used for |
|---|---|
chat:write | Posting incident and investigation notifications |
channels:read | Listing public channels for channel selection |
groups:read | Listing private channels for channel selection |
users:read | Resolving user mentions in notifications |
Steps to configure in CauseFlow
Authorize in Slack
You’ll be redirected to Slack. Select the workspace and click Allow to grant CauseFlow the bot permissions listed above.
Return to CauseFlow
You’ll be redirected back to CauseFlow with the Slack integration showing as connected.
Notification types
| Notification | When it fires |
|---|---|
| New incident | Alert received and triage complete |
| Investigation complete | Agents finish and a root cause is available |
| Pending approval | A remediation proposal is waiting for your review |
| Incident resolved | An incident is marked as resolved |
Troubleshooting
Bot not posting: Confirm the CauseFlow bot has been added to the target channel. In Slack, open the channel, click the channel name, go to Integrations > Bots, and add the CauseFlow app. Missing channels in the selector: If a private channel is not listed, invite the CauseFlow bot to that channel first, then return to the CauseFlow dashboard to refresh the channel list.Microsoft Teams
How it works
CauseFlow connects to your Microsoft Teams tenant via OAuth and provisions a CauseFlow bot that posts to the channels you select. The connection uses the Teams Bot Framework channel for message delivery.Required information
| Item | Description |
|---|---|
| Microsoft 365 tenant | The tenant where Teams is provisioned |
| Team and channel selection | Which Teams channel receives notifications |
| Admin consent | A Microsoft 365 admin must approve the app permissions during OAuth |
Bot scopes requested
| Scope | Used for |
|---|---|
ChannelMessage.Send | Posting incident and investigation notifications |
Channel.ReadBasic.All | Listing channels for channel selection |
Team.ReadBasic.All | Listing teams for team selection |
Steps to configure in CauseFlow
Sign in with Microsoft
You’ll be redirected to Microsoft’s authorization page. Sign in with an account that has permission to consent on behalf of your organization, or ask a Microsoft 365 admin to complete this step.
Grant admin consent
Microsoft 365 requires admin consent for bot message permissions. If you are not an admin, the page will prompt you to request admin approval.
Return to CauseFlow
You’ll be redirected back to CauseFlow with the Teams integration showing as connected.
Notification types
Teams receives the same notification types as Slack (new incident, investigation complete, pending approval, incident resolved).Troubleshooting
Admin consent required: If your Microsoft 365 tenant requires admin approval for third-party apps, ask your tenant admin to approve the CauseFlow app in the Microsoft Entra admin center under Enterprise applications. Bot not appearing in Teams: After the OAuth flow completes, the CauseFlow bot may take a few minutes to appear in Teams. If it does not appear after 5 minutes, disconnect and reconnect the integration from the CauseFlow dashboard.Integrations overview
See the full catalog of supported tools.
Integrations overview
See the full catalog of available integrations.
Security overview
Learn how CauseFlow stores and protects your communication credentials.
API reference
Manage notification settings programmatically.