If/Else action
Using Includes/Does Not Include as a Condition
Section titled “Using Includes/Does Not Include as a Condition”When setting up conditions in Stack’s Workflow Builder, you can specify “Includes” or “Does Not Include” for certain fields like Tags and multi-option custom fields (e.g., checkboxes, dropdowns).
Creating an And Condition
Section titled “Creating an And Condition”To create an “AND” condition, ensure that multiple criteria are met simultaneously. For example, if you want to check that a contact does NOT have both the ‘consultation_booked’ and ‘consultation_confirmed’ tags, use the AND condition. The contact will only proceed down the “YES” path if neither tag is present.
Creating an Or Condition
Section titled “Creating an Or Condition”For an “OR” condition, separate the criteria into individual checks. This setup allows the condition to be true if at least one of the criteria is met. For instance, if a contact has either the ‘consultation_booked’ or ‘consultation_confirmed’ tag, they will proceed down the “YES” path.
If/Else Branches
Section titled “If/Else Branches”In Stack, If/Else branches can support up to 10 different outcomes for a single event, allowing for complex decision-making processes within your workflows.
Handling Multiple True Branches
Section titled “Handling Multiple True Branches”If multiple branches evaluate to true, Stack will direct the contact down the first true path as per the order you’ve set up. The system processes conditions from top to bottom.
Time Comparison Operators
Section titled “Time Comparison Operators”Time Comparison Operators are crucial for automating decisions based on date and time. You can compare units like the current day, month, year, or hour with specific values.
The “Is” Operator
Section titled “The “Is” Operator”This operator checks if a date unit matches a specified value. For example, “Current Day of the Week Is Monday” is true only on Mondays.
The “Is Not” Operator
Section titled “The “Is Not” Operator”This operator verifies that a date unit does not match a specified value. For example, “Current Day of the Week Is Not Saturday” is true on any day except Saturday.
The “Is After” Operator
Section titled “The “Is After” Operator”The “Is After” operator checks if a date unit is later than a specified value. For hours, it considers the next full hour. For example, “Current Hour Is After 6 PM” is true from 7:00 PM onwards.
The “Is on or After” Operator
Section titled “The “Is on or After” Operator”This operator checks if a date unit is on or after a specified value. For hours, it includes the entire specified hour. For example, “Current Hour Is On or After 6 PM” is true from 6:00 PM onwards.
The “Is Before” Operator
Section titled “The “Is Before” Operator”The “Is Before” operator checks if a date unit is earlier than a specified value. For example, “Current Month Is Before June” is true for all months before June.
The “Is on or Before” Operator
Section titled “The “Is on or Before” Operator”This operator checks if a date unit is on or before a specified value. For hours, it includes the entire specified hour. For example, “Current Hour Is On or Before 6 PM” is true up to 6:59 PM.
The “Is Not Empty” or “Is Empty” Operator
Section titled “The “Is Not Empty” or “Is Empty” Operator”These operators check whether a field has a value (“Is Not Empty”) or lacks a value (“Is Empty”), ensuring valid input for your workflow automation.
Troubleshooting
Section titled “Troubleshooting”For issues with If/Else conditions, especially with AND or OR logic, review your setup to ensure conditions are correctly configured and ordered.
Overview
Section titled “Overview”The If/Else Condition action in your Stack automation workflow is a powerful tool that allows you to direct contacts through different paths based on specific conditions. This feature is essential for crafting personalized and dynamic workflows that respond to your contact’s behaviors.
Action Name
Section titled “Action Name”If/Else Condition
Action Description
Section titled “Action Description”The If/Else Condition action evaluates a specified condition and guides the contact down different branches depending on whether the condition is met. This allows you to customize subsequent actions based on the contact’s engagement or characteristics.
Action Details
Section titled “Action Details”| Value Name | Description | Mandatory |
|---|---|---|
| Action Name | The name you assign to this action for easy identification in your workflow. | Yes |
| Condition | The specific condition that is evaluated (e.g., if an email was opened, if a form was submitted). | Yes |
| Branches | The paths that the contact will take based on the condition’s outcome (e.g., Yes, No). | Yes |
Example: Follow-Up Based on Email Engagement
Section titled “Example: Follow-Up Based on Email Engagement”Scenario
Section titled “Scenario”Imagine your business sends a promotional email to customers, and you want to follow up differently based on whether they opened the email or not.
Solution Using the If/Else Condition
Section titled “Solution Using the If/Else Condition”-
Trigger: The workflow begins when a promotional email is sent.
-
Action 1: Use the If/Else Condition to check if the email was opened.
-
Condition: Email Event is Opened.
-
Yes Branch: If the email was opened, send a thank-you email with a special offer.
-
No Branch: If the email was not opened, resend the promotional email with a different subject line.
-
Steps to Implement
Section titled “Steps to Implement”- Add the If/Else Condition action to your workflow after sending the promotional email.
- Set the Condition to “Email Event is Opened”.
- Configure the Yes Branch to follow up with a thank-you email and a special offer.
- Configure the No Branch to resend the promotional email with a different subject line.
By using this approach, you can ensure that you engage customers based on their interaction with your initial email, making your follow-up more relevant and effective.
Upgrades
Section titled “Upgrades”Introducing Scenario Recipes
Section titled “Introducing Scenario Recipes”We’ve reimagined the setup process for If/Else conditions with Scenario Recipes. These pre-built templates simplify your workflow configuration:
- Select a Recipe: Choose from our selection of 10 pre-built recipes or create your own.
- Pre-requisites: Recipes will indicate any pre-requisites needed before use, ensuring a smooth setup.
Enhanced Branch Functionality
Section titled “Enhanced Branch Functionality”The If/Else branches have received a major upgrade:
- Concise Summaries: Each branch now displays a concise text summary, allowing you to quickly understand the conditions.
- Multiple Conditions: For branches with multiple conditions, click “+x more conditions” to view a complete list in a pop-up window.
- Focused Editing: Click on any branch to isolate it for editing, collapsing others for a focused workflow.
“Time of the Day” Condition
Section titled ““Time of the Day” Condition”We’ve expanded the “Current Hour” condition type with a new “Time of the Day” option:
- Granular Control: Select specific times down to 15-minute intervals for more precise control.
- Descriptive Values: Descriptions of selected values help you understand when conditions will be true.
UI Upgrade
Section titled “UI Upgrade”Enjoy a refreshed and streamlined UI for the If/Else action:
- Branch Configuration: The screen has been simplified for ease of use.
- Condition Dropdown: A new dropdown makes it easier to search and select specific conditions.
- Drag and Drop: Easily rearrange branches by dragging and dropping them within the UI.
What is If/Else?
Section titled “What is If/Else?”The If/Else feature in Stack allows you to create sophisticated workflows that perform different actions based on specific conditions. This feature uses conditional logic: if a particular event occurs in your trigger app, then one action happens; if another event occurs, a different action takes place.
New Features
Section titled “New Features”1. Duplicate Branch
Section titled “1. Duplicate Branch”Save time and effort by easily copying existing branches without starting from scratch.
- How to Duplicate a Branch:
- Click the three dots menu on the branch you wish to duplicate.
- Select “Duplicate Branch.”
- The duplicated branch will appear below the original, with “(copy)” added to its name. Feel free to rename it as needed.
2. Reorder Any Branch
Section titled “2. Reorder Any Branch”Organize your workflow visually by rearranging branches through a simple drag-and-drop interface.
- How to Reorder Branches:
- Click the “Reorder Branches” icon.
- Drag and drop branches to your desired order.
- Note: The “None” branch cannot be reordered, but all other branches can be moved freely.
3. Rename None Branch
Section titled “3. Rename None Branch”For better organization, you can now rename the “None” branch.
- How to Rename the None Branch:
- Click on the branch name.
- Type in your desired name. Ensure the branch name is not left empty.