Overview
The Branch step lets you create different paths within your workflow, depending on certain conditions. It chooses the best route based on the situation.
Create Branches
Start by setting up a trigger for your automation.
Add the Branch action to the automation flow.
Define the conditions that will trigger each path.
Within each path, click ➕ Add Step to specify what happens next.
You can either finish the automation here or continue with additional actions.
Branching Settings
Connector options give you full control over the Filter Data automation:
🏷️ Field | 🔤 Description |
DATA | Choose the input data. |
CONDITION | Specify conditions for the data filter. |
VALUE | Enter the value to compare against. |
💡 Note: Click ➕Add to add more conditions that must all be true for the automation to proceed. Click ➕ Or add an alternative condition, meaning that either the first set of conditions or the new set can trigger the automation.
Fallback
The fallback option ensures that your automation continues even if no conditions are met. If none of the defined paths match, the workflow will follow a fallback route.
Set up a fallback path:
Add the Branch action to your automation.
Define conditions for each path.
In the last branch, Path Condition Type to Fallback.
💡 Note: The Branch action supports up to 7 paths, but you can add more by setting the last path’s Condition Type to Fallback and adding another Branch action after it. Repeat this process to build more advanced automation flows.
Use Cases
Not sure how to use the Branch action? Here are a few ideas:
🪄 Use Case | 🔤 Description |
Task prioritization | Automatically route tasks to different workflows based on priority levels (e.g., High Priority goes to urgent queue, Low Priority to a regular queue). |
Project status updates | Depending on project status (e.g., "In Progress," "Completed"), trigger different actions like notifying stakeholders or archiving completed tasks. |
Client communication | Direct client inquiries to different paths based on urgency or type (e.g., support requests go to customer service, while sales inquiries go to sales team). |
Client onboarding | Customize the onboarding process for new clients by branching the workflow based on client type (e.g., small business vs. enterprise). |
Approval processes | Route tasks through different approval paths depending on the task's nature (e.g., financial approvals vs. content approvals). |
😊 Helpful Links
Download our apps: taskade.com/downloads
Leave feedback: taskade.com/feedback
Changelog: taskade.com/blog/updates
Watch tutorials: youtube.com/taskade
Contact us: taskade.com/contact
🤖 Taskade AI Essentials