Using legacy custom integrations is an outdated way for teams to integrate with Slack. Legacy custom integrations lack newer features and will be deprecated and possibly removed in the future. We do not recommend their use.

We recommend using their replacement: Slack apps. Slack apps can be built just for your own workspace or distributed through the App Directory, and they can use the latest and greatest APIs and UI features.

Legacy custom integations slash commands

Slash Commands let users trigger an interaction with your app directly from the message box in Slack.

Because we strongly recommend you do not use legacy custom integrations anymore, you should instead use the similar feature in Slack apps. Our guide to Getting Started with Slash Commands will walk you through the process of enabling this functionality in a Slack app.

Migrating from legacy Slash Commands

If you previously created any commands using legacy integrations, you should switch to using the same functionality with a Slack app instead. To do this you need to follow the Getting Started with Slash Commands guide and create new commands to replicate your existing ones.

The majority of your legacy code for handling and responding to Slash Commands should continue to work within a Slack app without much modification.

Legacy information

Though we recommend that all legacy custom integrations should migrate to Slack apps, we also understand that some will still need to maintain older integrations. This section contains any information about using Slash Commands that is specific to the legacy implementation.

Legacy management

If you need to configure your legacy integrations, you can access the Integrations management pages here.

Additional limitations

While you can respond to legacy Slash Commands to post messages in the same way as Slack Apps can, legacy integrations do not have access to interactive messages features. To make your messages interactive, you'll need to create a Slash Command with a Slack app instead.