--- title: Slack integration description: Connect Coralogix Cases to your Slack workspace. Send Case notifications to Slack channels, sync Slack thread replies back into the Case timeline, and surface rich previews of Coralogix Case URLs in Slack. url: https://coralogix.com/docs/integrations/pull/slack/ product: ingress feature: Slack Ingress feature_id: logs.slack-ingress feature_identifier: ingress/logs.slack-ingress last_updated: '2026-11-09' --- # Slack integration The Coralogix Slack integration connects Coralogix Cases to your Slack workspace, so on-call teams can triage and resolve incidents in the channels they already work in. On v0.1.0, Case notifications post to Slack, replies in the thread flow back into the Case timeline, and pasting a Coralogix Case URL into any channel where the bot is present renders a rich preview with status and priority. This page is the setup hub for the integration. Two adjacent pages own the rest: * [Working with Cases](https://coralogix.com/docs/user-guides/cases/working-with-cases.md) covers the Case-side experience: what Slack notifications look like in a Case, how synced comments appear in the timeline, and per-Case controls. * [Slack connector configuration](https://coralogix.com/docs/user-guides/notification-center/destination-types/slack/connector-config.md) covers channel routing, dynamic templating, and fallback channels for anything Coralogix sends to Slack, including Case notifications. ## Why v0.1.0 v0.1.0 is in public preview and is the default version for new Slack integrations. It brings Cases capabilities that earlier versions cannot offer, along with operational improvements that apply to every notification flow: * **Act on a Case from the Slack message.** A Case notification carries **Acknowledge**, **Resolve** and **Close** actions, so the first responder can move the Case on without leaving the channel. * **Two-way comment sync with Cases.** Slack replies on a Case notification become comments in the matching Case timeline, so the conversation that resolved the incident is preserved with the incident itself. * **Choice of reply mode for Case updates.** Post each Case update as a new message in the channel or as a reply in the existing notification thread, configured per Case. * **Rich link previews for Coralogix Case URLs.** Any time a Case URL is shared in a channel where the bot is present, Slack renders the Case status and priority inline so context follows the link. * **Higher Slack delivery throughput.** The new app has better rate limits with Slack, which reduces throttling on busy workspaces. * **Installable without Slack admin scope.** Workspace members without Slack admin permissions can install the app. * **Same Slack delivery for everything else.** Anything Notification Center sends to Slack, including alert notifications, continues to flow through this integration. No change to existing routing rules or connectors. To start using v0.1.0, add a new integration on v0.1.0. Your earlier-version Slack integration keeps running, and you can migrate each Notification Center connector to v0.1.0 one at a time. Both versions can run in parallel during the cutover. ### Coming soon * Alert evaluation chart visible directly in the Slack notification (optional). ### Slack Marketplace certification The app is certified by Slack and listed in the [Slack Marketplace](https://slack.com/marketplace/A0ASWNFGNGL-coralogix). Certification is a Slack-side review of the app listing, so it does not change how the integration behaves in your workspace: * Routing rules, connectors, and delivery are unchanged. * The app remains the default for new Slack integrations. Note The integration supports commercial Slack only. GovSlack is not supported yet. ## Prerequisites To configure this integration in Coralogix, ensure you have: | Resource | Action | Description | | -------------- | ------------ | -------------------------------------------- | | `integrations` | `ReadConfig` | View deployed integrations. | | `integrations` | `Manage` | Add, remove, or update integration packages. | Learn more about Coralogix roles and permissions in [Access control permissions](https://coralogix.com/docs/user-guides/aaa/access-control/permissions.md). To install the Coralogix Slack app in your workspace, you also need permission to authorize Slack apps in that workspace. ## Set up the integration ### Add a new Slack integration 1. From the Coralogix toolbar, go to **Integrations**, then **Integrations**. 2. Select **Slack**. 3. Select **Add New**. The current version is shown on the button, for example **Add New (v0.1.0)**. 4. In **Settings**: * Enter an **Integration name**. * Under **Application functionality**, select **Send notifications**. To also collect Slack access logs, see [Slack access logs](https://coralogix.com/docs/integrations/pull/slack-access-logs.md); it uses the same integration and requires the Slack `admin` scope. * When **Send notifications** is selected, the **Notification settings** section appears. Select **Two-way comment sync** to enable replies on a Slack thread to flow back into the Coralogix Case timeline. * Confirm **Consent to U.S. data transfer**. * Select **Create**. 5. In **Install the Coralogix Application**: * Select **Authorize**. * On the Slack authorization page, review the scopes and select **Allow**. See [OAuth scopes](#oauth-scopes) for what is requested and why. * Select **Close**. 6. In **Application Setup**: * Select **Create New Connector** to add the first Slack connector. The connector defines the destination channel and routing behavior; for the full field reference, see [Slack connector configuration](https://coralogix.com/docs/user-guides/notification-center/destination-types/slack/connector-config.md). * Select **Save**. The integration is now installed and ready to be referenced from Case notification settings and Notification Center routing rules. ### Migrate existing connectors to v0.1.0 v0.1.0 is a new integration that runs alongside any earlier-version Slack integration you already have. Each Notification Center connector references one integration, so the cutover is per-connector. Migrate one connector at a time with no downtime. 1. [Add a new Slack integration](#add-a-new-slack-integration) on v0.1.0. The earlier-version integration keeps delivering notifications through every connector that still references it. 2. In Notification Center, open a Slack connector that references the earlier-version integration. 3. In the connector's **Integration** field, select the new v0.1.0 integration. 4. (Optional) Run **Send test notification** to confirm the connector delivers through the new integration. 5. Save the connector. Repeat for each Slack connector. Connectors not yet migrated continue to deliver through the earlier-version integration, so both versions run in parallel during the cutover. Once every connector is on v0.1.0, you can remove the earlier-version integration. ## OAuth scopes The Coralogix Slack app requests these scopes from Slack based on the features you enable. It does not request the `admin` or `openid` scope. These scopes are always requested when installing the Coralogix Slack app for Cases and Notification Center: | Scope | Reason | | --------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------- | | [`chat:write`](https://api.slack.com/scopes/chat:write) | Post notification messages to configured Slack channels. | | [`chat:write.customize`](https://api.slack.com/scopes/chat:write.customize) | Customize message appearance (avatar, name) when posting. | | [`chat:write.public`](https://api.slack.com/scopes/chat:write.public) | Send notifications to channels without requiring the bot to be invited first. | | [`users:read`](https://api.slack.com/scopes/users:read) | Resolve Slack user identity when a user interacts with a Case notification. | | [`users:read.email`](https://api.slack.com/scopes/users:read.email) | Match the Slack user's email to their Coralogix account for permission checks on Case interactions. | These scopes are requested per feature when configuring Cases or Notification Center. Each is optional and used only when you enable the corresponding feature. | Scope | Feature | Reason | | ------------------------------------------------------------------- | -------------------- | -------------------------------------------------------------------------------------------------------------------------- | | [`channels:join`](https://api.slack.com/scopes/channels:join) | Two-way comment sync | After posting a notification to a public channel, the bot joins the channel to read thread replies. | | [`channels:history`](https://api.slack.com/scopes/channels:history) | Two-way comment sync | Read thread replies on Coralogix notification messages in public channels to surface them in the Coralogix Case timeline. | | [`groups:history`](https://api.slack.com/scopes/groups:history) | Two-way comment sync | Read thread replies on Coralogix notification messages in private channels to surface them in the Coralogix Case timeline. | | [`links:read`](https://api.slack.com/scopes/links:read) | Rich link previews | Detect Coralogix Case URLs shared in Slack to trigger preview generation. | | [`links:write`](https://api.slack.com/scopes/links:write) | Rich link previews | Display a rich preview when a Coralogix Case URL is shared in Slack, showing Case status and details inline. | To collect Slack access logs, which uses the same integration and requires the `admin` scope, see [Slack access logs](https://coralogix.com/docs/integrations/pull/slack-access-logs.md). ## AI-generated content Some content that the Coralogix Slack app shows in Slack is generated by AI: * Investigation summaries, likely root causes, and remediation recommendations in Case notifications. * The AI summary in the Case details view opened from a Coralogix Case URL preview. Warning AI can make mistakes. AI-generated content may be inaccurate, incomplete, or out of date. Always verify AI-generated insights against your underlying observability data before you act on them, especially before you make changes to production systems. ## Data and privacy For how Coralogix collects, processes, and stores your data, see the [Coralogix Privacy Policy](https://coralogix.com/privacy-policy/). ## What the integration unlocks The integration is the workspace connection; the user-facing behavior lives in the product that consumes it. ### Case notifications in Slack Once the integration is live and a connector is configured, Case notifications post to Slack from the channels you defined in the connector. For per-Case notification settings and how Case events map to Slack messages, see [Working with Cases](https://coralogix.com/docs/user-guides/cases/working-with-cases.md). Each notification carries **Acknowledge**, **Resolve** and **Close** actions. Selecting one updates the Case in Coralogix, so a responder can take the Case without switching tools, and the change appears in the Case timeline like any other status change. When AI analysis is available for a Case, its notifications can include an AI-generated investigation summary, likely root cause, and remediation recommendations. See [AI-generated content](#ai-generated-content). ### Two-way Case comment sync (v0.1.0) When **Two-way comment sync** is enabled on a v0.1.0 integration, the Coralogix Slack app subscribes to thread events on the messages it posted and writes replies into the matching Case timeline. The integration handles the Slack-side requirements: * The bot joins public channels automatically the first time it posts there, using the `channels:join` scope. * For private channels, invite the Coralogix Slack app to the channel before sending notifications there. * Slack users are mapped to Coralogix users by email when the Slack email matches a Coralogix account. How synced comments appear in a Case timeline, and the controls for muting or unmuting sync per Case, are documented in [Working with Cases](https://coralogix.com/docs/user-guides/cases/working-with-cases.md). ### Rich Coralogix Case URL previews in Slack (v0.1.0) When a Coralogix Case URL is shared in any Slack channel where the bot is present, Slack renders a rich preview with the Case status, priority, and a short summary. The preview updates when the Case status changes. No per-Case configuration is required; the capability is active as long as the app is installed with `links:read` and `links:write` granted. Opening the Case details from the preview also shows an AI-generated summary of the Case when one is available. See [AI-generated content](#ai-generated-content). ### Alerts and other Notification Center routing Notification Center routing rules that target Slack go through the same integration. Channel routing, dynamic templating, and fallback behavior for alert notifications and any other Notification Center traffic are configured in [Slack connector configuration](https://coralogix.com/docs/user-guides/notification-center/destination-types/slack/connector-config.md). See [Notification Center overview](https://coralogix.com/docs/user-guides/notification-center/introduction.md) for routing rule setup. ## Manage your integrations Each row in the Slack integrations list shows the **Integration Name**, **Status** (**Active**, **Pending**, or **Failing**), **Integration Version**, **Application Functionality**, the number of **Connectors**, **Last Updated**, and **Actions**. Versions earlier than v0.1.0 are shown alongside v0.1.0 in the list, so a workspace can run a mix of versions during a migration window. Update integrations to v0.1.0 when you are ready; integrations on older versions continue to deliver outbound notifications but cannot offer two-way Case comment sync or rich Case URL previews. To edit an integration, use the pencil icon. To remove it, use the trash icon. Removing an integration also removes its connectors, and Case notification settings or Notification Center routing rules that referenced those connectors stop delivering until they are reconfigured. ## Troubleshooting | Symptom | Cause | Resolution | | -------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Status shows **Failing** in the integrations list | The app token was revoked or the workspace removed the Coralogix Slack app. | Open the integration and reinstall the app. | | No Case timeline updates from Slack replies | The integration is on a version earlier than v0.1.0, **Two-way comment sync** was not enabled at install, or the bot is not a member of the channel. | Update the integration to v0.1.0 and enable **Two-way comment sync**. For private channels, invite the bot to the channel. | | Coralogix Case URLs do not preview in Slack | The integration is on a version earlier than v0.1.0, or `links:read` and `links:write` were declined during install. | Update to v0.1.0 and reauthorize the Slack app. | | Case notifications post to the wrong Slack channel | The connector is routing to a different channel than expected. | Review the connector. See [Slack connector configuration](https://coralogix.com/docs/user-guides/notification-center/destination-types/slack/connector-config.md) for channel routing and dynamic templating. | | Banner says v0.1.0 is pending certification | Slack Marketplace certification is in progress. | The integration is available for production use; no action required. | For Case-side notification configuration issues, see [Working with Cases](https://coralogix.com/docs/user-guides/cases/working-with-cases.md). ## Related resources * [Working with Cases](https://coralogix.com/docs/user-guides/cases/working-with-cases.md) * [Slack connector configuration](https://coralogix.com/docs/user-guides/notification-center/destination-types/slack/connector-config.md) * [Slack connector schema structure](https://coralogix.com/docs/user-guides/notification-center/destination-types/slack/schema-structure.md) * [Notification Center overview](https://coralogix.com/docs/user-guides/notification-center/introduction.md) * [Dynamic templating](https://coralogix.com/docs/user-guides/notification-center/dynamic-templating.md) * [Coralogix Privacy Policy](https://coralogix.com/privacy-policy/)