Branch Out Your Slack Workflows with Conditional Logic

What you need to know: 

• Workflow Builder now includes conditional branching, allowing users to create complex, multi-branched automated workflows without a line of code.
• Integrate Slack workflows with over 70 apps, including Salesforce, centralizing automation across your existing tools.

Repetitive tasks, constant app-switching, and the struggle to find information consume valuable time and cognitive energy. Automating your work is essential but can be complicated, requiring specialized tools or IT support. Slack offers a simple, non-technical way to create workflows and automate tasks across your tech stack, all from a single place.

Thanks to the valuable feedback from our community, Slack’s Workflow Builder now offers conditional, multi-branched workflows! You can quickly create and manage two layers of multi-branched workflows directly in Slack, and connect them to your tools — without needing to write code — streamlining processes and freeing up your time.

Automation with conditional branching

With the recent addition of conditional branching to Workflow Builder, you can create complex, multi-branched processes with a few clicks that adapt the workflow based on specific conditions. Today, this feature supports up to 15 conditions, with a second layer of branching that allows for up to 5 additional conditions. This enables a wide range of use cases, such as:

• Triaging incidents based on their criticality.
• Routing requests to the appropriate team, department, or region.

Multi-level approval workflows.

New Workflow Builder features include:

• Conditional branching: Create dynamic workflows in minutes that adapt based on specific criteria. For example, you could configure a workflow to direct support requests to specific channels depending on the issue type, or to automate approval processes by assigning different approvers based on regions or teams.
• Automation that integrates with all your tools: Connect with Salesforce and more than 70 app connectors so you can build workflows with conditional logic across your apps, data, and processes within Slack. For example, you can integrate with your project management tools, CRM, and other essential apps to centralize all your workflows in one place.
• Enhanced compatibility: Workflow Builder integrates across the entire Slack work operating system, including channels, forms, lists, and canvas, ensuring smooth automation and improving workflow versatility. For example, you can use a form to collect time-off requests, send the request to a manager for first-level approval, then to procurement for final approval, and finally notify the requester of approval or denial. All data can be recorded in a canvas or list for tracking.
• Enhanced workflow interactivity: You can now configure up to five continuation buttons, each mapping to a different branch in your workflow. This allows for more controlled workflows with built-in execution data. For instance, you could create a message with “Approve,” “Reject,” or “Escalate” buttons, with each button leading to a specific workflow branch.

Example: Automating a support request workflow

With Workflow Builder, you can set up a workflow that automates support requests to the right team.

Here’s how it works: Users can submit a request for support via the #help-desk workflow when they’re having an issue. Immediately, an automated message is sent to the user acknowledging their request and providing a ticket number.

To gather more details, a Slack form pops up, prompting the user to provide information about the nature of their issue and their contact information.

Now, based on the input:

• If the issue is technical, the request is routed to the #tech-support channel and @ mentions the on-call engineer for follow-up support.
• If the issue is billing-related, the request is routed to the #billing-support channel, and a task is created in the project management tool for the billing team.
• If the issue is equipment, the request is routed to the #equipment-support channel, and the support manager is notified.

Once the request is routed, the user will receive a follow-up message letting them know who will handle their request and the estimated response time.

Throughout the process, the progress of the support request is tracked, and the user receives updates. Finally, when their issue is resolved, they receive a final message confirming the resolution and are prompted to provide feedback.

Example: Automating a multi-layered expense approval workflow

With Workflow Builder, the #finance-requests channel can set up a workflow that automates two-tiered approval for a company expense or purchase order.

Users submit an approval request via the workflow for the purchase order or company expense. Immediately, an automated message is sent to the user acknowledging their request and providing a tracking ID.

To gather more details, a Slack form pops up, prompting the user to provide the requested item, its cost, and the business justification.

First, the workflow routes the request to the user’s direct manager for initial Layer 1 approval. A message with an approval button is sent to the manager.

Now, based on the input the approval workflow further routes the request:

• If the direct manager approves: The request is automatically routed to the Finance Director for final Layer 2 budget approval. A message with a final approval button is sent to the director.
  • If the finance director approves: The request is routed to the #procurement channel, and a task is created in the project management tool for the procurement team.
  • If the finance director rejects: The user receives a message letting them know the request was rejected at Layer 2 with the reason provided.
• If the direct manager rejects: The workflow terminates. The user receives a message letting them know the request was rejected at Layer 1.

Once the request is fully approved, the user will receive a follow-up message letting them know who will handle the purchase and the estimated timeline. Throughout the process, the user receives updates on which layer of approval the request is currently in.

How to create your first workflow with conditional branching

1. Create the workflow: Choose the starting action “From a link in Slack.” Users will click a button to start your workflow.
2. Add initial steps: Use Slack’s no-code interface to add steps like acknowledging the request, gathering information through forms, and notifying relevant team members.
3. Implement conditional branching: Set up conditional logic to route the workflow based on specific criteria. For example, you can route a support request to different channels based on the type of issue or severity, or automatically send requests to the correct region or department based on custom rules that you define.
4. Follow-up and resolution: Configure steps to notify the user of the workflow’s progress, track the task’s status, and confirm resolution once the process is complete.
5. When you are finished, name the workflow and add it to the channel’s workflow tab. You can also feature the workflow in the channel, making it even easier for your users to find.

Learn more about branching in our Guide to Workflow Builder.

Automate workflows, right in the flow of work 

With Slack’s Workflow Builder, you can now create complex, multi-step automated processes that adapt based on your needs. This makes it easier for anyone to build and manage sophisticated workflows quickly, directly within Slack, so you can simplify your tasks and focus on the important stuff.

Whether you’re handling basic to-dos or intricate projects, Workflow Builder provides the easiest and most effective way to automate your work in the place you already collaborate.

Why not give it a try? Happy automating! 🚀 [# /]