In September 2023, following the release of the new version of Workflow Builder, we announced the deprecation of the legacy version of Workflow Builder. As part of this deprecation, you’ll no longer be able to create legacy workflows, use legacy templates or copy existing legacy workflows as of 24th June 2024. We’ll migrate your eligible legacy workflows to the new version of Workflow Builder, and deprecate them entirely, starting 26th September 2024. Read on to learn more about the deprecation and migration process, and the steps that you can take if some of your workflows cannot be migrated.

Deprecation and migration timeline

Date	What to expect
September 2023 through July 2024	We'll attempt to migrate your existing workflows, including workflows with Google Sheets steps from apps. The timing of the migration for your workspace or org’s workflows will depend on the types of steps they contain and how many total workflows have been created.
24 June 2024	You’ll no longer be able to create new legacy workflows, use legacy templates or copy existing legacy workflows. You’ll be able to use, edit and re-publish existing legacy workflows until they are fully deprecated.
1 August 2024	Workflow migrations are complete. Any workflows still listed in the All published legacy workflows tab could not be migrated and will need to be rebuilt with the new version of Workflow Builder.
26 September 2024	Starting on this date, unmigrated workflows will stop running and you won’t be able to view, edit or re-publish them. Access to legacy workflow management will disappear and you'll need to rebuild any remaining workflows with the new version of Workflow Builder.

 

Note: Once a workflow is migrated, the Last edited date will reflect the date of the migration (if the workflow hasn’t been edited since).

Understand your unmigrated workflows

There are a few types of workflows we’re not able to migrate to the new version of Workflow Builder. Here’s what you can do:

• Workflows with steps from apps (other than Google Sheets)
  We recommend recreating these workflows with the new version of Workflow Builder. To see a full list of steps that you can use to integrate workflows with other services, open Workflow Builder and click Create workflow. Choose how you’d like your workflow to start, then browse the list of available steps.
• Workflows with steps for Google Sheets used in Slack Connect
  To protect your organisation, there are some limitations on workflows in Slack Connect conversations. Legacy workflows with Google Sheets steps from apps that are used in Slack Connect conversations will not be migrated. You can recreate the workflow, but external people won’t be able to use it.
• Unpublished workflows
  To use these workflows again, you can recreate them with the new version (or delete them if you no longer need them). If you publish an unpublished workflow after your migration is complete, it will not be automatically moved over.
• Workflows in archived channels
  Delete these workflows if you won’t need to use them in the future. Otherwise, you can rebuild them with the new Workflow Builder.
• Workflows where managers are deactivated or can't access private channels
  A workflow with a deactivated creator and no active workflow managers won’t be migrated. Workspace and Org Owners can add themselves as a manager from the All published legacy workflows tab in Workflow Builder, but in cases where the workflow manager does not have access to private channels or other resources used in the workflow, it can't be migrated.

Note: If one or more of your workflows weren’t migrated and do not meet the criteria above, let our Support team know so that we can help out.

Special considerations

Activity logs

Activity logs for legacy workflows will not be migrated. Once a workflow is migrated, subsequent activity will be captured.

Workflow buttons

If a user starts a legacy workflow with a button step but does not complete it before the workflow is migrated, after migration, the button will not work when clicked. The workflow will return an error and won't progress to the next step. Users will have to restart the workflow in the updated system.

Custom steps

Custom steps from apps and legacy custom steps aren’t supported in the new version of Workflow Builder. Instead, you’ll need to rebuild legacy steps as custom functions using the Slack-hosted automation platform, or host on your own infrastructure with our custom function development (beta) in our Bolt for Python and Bolt for JavaScript SDKs. We expect this to become generally available by the end of August 2024.

Once you've created and deployed a coded function, you’ll need to recreate any workflows with legacy steps your team used. You can do this using the new version of Workflow Builder, or by building your workflows in code and deploying them with the Slack CLI.

 

FAQ

How can I rebuild workflows that were deprecated?

To rebuild your workflows, you'll need to use the new version of Workflow Builder. To help you get started, we've created the following guides for rebuilding legacy workflows: 

• Rebuilding legacy workflows in the new version of Workflow Builder
• Rebuild a workflow that started with a shortcut trigger
• Rebuild a workflow with third-party steps

How can I rebuild workflows that have Steps from apps?

As an alternative to legacy Steps from apps, Slack built a variety of connectors for Workflow Builder. Connectors allow you to add steps to your workflows that will take an action in a third-party service. If none of our existing connectors meet your needs, you can build a custom function. Custom functions are built with the Slack Deno SDK and can be used directly with Workflow Builder. You can get started with custom functions here: https://api.slack.com/automation/quickstart.