Skip to main content

Migrate from the legacy Slack notifications app to the new Slack integration

Learn how to switch to the new Slack integration and keep your workflow notifications running smoothly.

Beth-Ann Sher avatar
Written by Beth-Ann Sher
Updated yesterday

Intercom is upgrading all Slack notification functionality to the new, native Slack integration. This gives you a more reliable, scalable way to connect Intercom with Slack and unlocks additional Slack features going forward.

Since you’re using the legacy Slack notifications app, this guide explains what steps you need to take, how to migrate, and what changes after you install the new Slack integration.

Key benefits

  • Manage everything in one place: View and manage all connected Slack workspaces and channels in a unified integration.

  • Connect multiple Slack workspaces: Set up Slack notifications wherever your teammates work.

  • Unlock new Slack features: Use Intercom features like Fin over Slack, conversations, tickets, and broadcasts.

  • Get ongoing updates: New features and bug fixes are only supported in the new Slack integration.


What you need to do

If you already use the new Slack integration

If you only use the legacy Slack notifications app

  • Slack notifications in existing workflows will continue to work.

  • From December 4, 2025, you must install the new Slack integration to configure notifications in new workflows, otherwise you'll see the warning: “No channels available".

  • Install the new integration before February 9, 2026 to avoid interruptions.

  • Migration runs automatically as soon as you install the new integration (public channels migrate; private channels must be added manually).

If your workspace is not actively sending Slack notifications

  • No immediate action is required.

  • If you install the new Slack integration later, migration will run automatically for any workflows that include Slack notifications (even inactive ones).


How to migrate to the new Slack integration

To install the new Slack integration:

  1. Click Connect workspace and authorize Slack.

  2. You can skip optional setup if you're only migrating notifications.

Migration begins immediately after installation. Existing workflows update to use channels connected in the new Slack integration.


What changes after you install the new Slack integration

Notifications come from a new bot

Once you install the new integration, we’ll migrate your Notify Slack step in workflows to be powered by the new integration instead.

The Slack notifications will come from the @Intercom app instead of the old @Intercom Notifications app once you’ve migrated.

Old Intercom Notifications Bot

New Intercom Bot

Note:

  • The legacy app will no longer appear in the App Store once a workspace is migrated.

  • In Workflows, the Notify Slack step will only show channels connected in the new integration, and the channel purpose must be set to Post Slack notifications only.

Public channels migrate automatically

  • The new Intercom bot is automatically added to all public channels used in your existing notification steps.

  • Notifications will thread under the new Intercom bot going forward.

  • Slack automatically displays a disclaimer message when the bot is added. This does not create conversations in Intercom.

Private channels must be connected manually

Slack does not allow apps to auto-join private channels.

To connect a private channel:

  1. In Slack, open the private channel.

  2. Add @Intercom to the channel.

  3. Open Settings > Channels > Slack in Intercom to confirm the channel appears.

  4. Set the channel purpose to Post Slack notifications only.


FAQs

Will my existing Slack notifications stop before I migrate?

No. Your Slack notifications continue working through the legacy app until you install the new integration. After installation, notifications move to the new Intercom app.

Why do I see “No channels available” in my workflow?

This appears when the new Slack integration has not been installed yet. Install it to restore your channel list.

Why are Slack notifications appearing as new threads?

Once migrated, Slack notifications from the new Intercom bot always appear as a new thread. The new bot cannot reply inside threads created by the legacy bot.

Do I need to migrate private Slack channels myself?

Yes. Slack permissions prevent apps from auto-joining private channels. Add the @Intercom bot to each private channel manually, then set the channel purpose to Post Slack notifications only in Intercom settings.

How can I see which private Slack channels were used previously?

Open the configuration for the legacy Intercom Notifications app in Slack. You’ll see:

  • All public channels where the legacy bot is installed.

  • Only the private channels you are a member of.

This helps you identify which ones to reconnect.


💡Tip

Need more help? Get support from our Community Forum
Find answers and get help from Intercom Support and Community Experts


Did this answer your question?