Condition Step
Unlock the full potential of your workflow automation with the Condition step. Tailor your processes to respond dynamically based on specific criteria, ensuring your system operates efficiently and effectively. Whether you're tracking user activity, analysing data trends, or mana
Listen to an audio overview
A short, AI-generated podcast-style summary of this article.
Unlock the full potential of your workflow automation with the Condition step. Tailor your processes to respond dynamically based on specific criteria, ensuring your system operates efficiently and effectively. Whether you're tracking user activity, analysing data trends, or managing complex variables, the Condition step offers flexibility and precision to meet your unique needs.
Use Cases for Condition Step
Description of Condition Step
Additional Use Cases for Condition Step
Further Description and Use Cases for Condition Step
More Descriptions and Use Cases for Condition Step
The Condition step allows you to navigate to different steps or sub-flows based on specific conditions.
To set up a Condition step, click "+ Add Condition Group" to create at least one group of conditions. Note that an "Otherwise" group is always present.
You can create as many condition groups as needed. The system evaluates them from top to bottom, proceeding to the designated step when a group matches. If no groups match, the "Otherwise" group is activated. It's advisable to name a step in the "Otherwise" group, even if it's rarely used.
It's crucial to understand the distinction between "All conditions" and "Any conditions," which is located at the top right of each condition group.
When listing multiple conditions in a group, your choice between "All" and "Any" affects the outcome.
"All Condition" means every condition in the group must be met for the group to match.
Conversely, "Any Condition" requires only one condition in the group to be met for a match.
Tag & Sequence Conditions
For tag and sequence conditions, select "in" or "not in" from the "Operator". You can choose multiple tags or sequences.
Text Variable Conditions
Operators for text conditions include various options.
For all variable types, "has any value" and "is empty" work as follows: clearing a variable makes it empty, so "has any value" becomes false and "is empty" becomes true.
Number Variable Conditions
Operators for number conditions include a range of options.
DateTime Variable Conditions
Operators for DateTime conditions include several options.
Ensure "value" is always formatted as "yyyy-MM-dd HH:mm:ss", regardless of the displayed format for that variable.
Remember, "before/after" compares the entire datetime value, while "time before/after" only compares the time value.
New Date-Time Filter Conditions
New date-time conditions have been added for filtering:
After x days ago
Before x days ago
After x minutes ago
Before x minutes ago
These options enable users to filter data or users based on specific activity periods, simplifying the targeting of recent or past events for follow-ups or analysis.
1. After x Days Ago
Description
The "After x days ago" condition allows you to filter records or users based on activities occurring after a specified number of days. It's useful for retrieving records or users whose activities happened after a certain date relative to today.
How to Apply the After x Days Ago Condition
Navigate to the Flow and select the Condition Node.
Click on "Add Condition".
A popup will appear where you can select "last seen".
Upon clicking "Operator", you will see the "After x days ago" option.
Enter the desired value in the Value Field, and the condition will apply accordingly.
This condition checks if the user's "Last Seen" date is more than 30 days ago.
Use Cases
Recent Activity Tracking: Filter users or records that interacted with your system after a specified number of days.
Targeted Follow-ups: Identify users who haven't interacted recently for follow-up actions or campaigns.
2. Before x Days Ago
Description
The "Before x days ago" condition filters users or records based on activities that occurred before a specified number of days. This is ideal for tracking older interactions or analysing past behaviour within a set period.
How to Apply the Before x Days Ago Condition
In the "Last seen" actions, you will see:
Enter the desired value in the Value Field, and the condition will apply accordingly.
This condition checks if the user's "Last Seen" date is earlier than 10 days ago.
Use Cases
Historical Data Analysis: Analyse user or record data within a specific range of past activity.
Event Follow-up: Identify users or records with activities before a certain date for retrospective analysis.
3. After x Minutes Ago
Description
The "Before x Minutes ago" condition filters users or records based on activities before a specified number of minutes. It's ideal for tracking older interactions or analysing past behaviour over a defined period.
In the "Last seen" actions, you have "After x minutes ago".
Enter the desired value in the Value Field, and the condition will apply accordingly.
This condition checks if the user's "Last Seen" date is more than 30 minutes ago.
Use Cases
Historical Data Analysis: Analyse user or record data within a specific range of past activity.
Event Follow-up: Identify users or records with activities before a certain date for retrospective analysis.
4. Before x Minutes Ago
Description
The "Before x Minutes ago" condition filters users or records based on activities before a specified number of minutes. It's ideal for tracking older interactions or analysing past behaviour over a defined period.
Similar to the above "Last seen" actions, you have "After x minutes ago".
Enter the desired value in the Value Field, and the condition will apply accordingly.
This condition checks if the user's "Last Seen" date is earlier than 10 minutes ago.
Use Cases
Historical Data Analysis: Analyse user or record data within a specific range of past activity.
Event Follow-up: Identify users or records with activities before a certain date for retrospective analysis.
JSON Variable Conditions
Operators for JSON conditions include a variety of options.
Note: The last three operators, "has item matched with ...", require the JSON to be a list of variables, not a list of JSONs. These operators work if your JSON stores a list of normal variables but not if it stores a list of JSONs.
Custom Input
Custom input is designed to compare values in a JSON variable. Search for "custom input" in the if field:
Select a value from a JSON, then compare it as you would with a text variable condition.
Math Formula
This operation allows you to perform formula calculations directly in the Action Step - "Set Variable Value" and Condition Step - "Value".
Supported math operations and functions include:
+ (addition), - (subtraction), * (multiplication), e (Euler's number), pi (π), PI, abs() (absolute value), min() (minimum), max() (maximum), ceil() (ceiling), floor() (floor), log() (logarithm), pow() (power), round() (rounding), sqrt() (square root), sin() (sine), cos() (cosine), tan() (tangent)
Note: If the formula is invalid, the system returns 0 for number variables and empty for text variables.
Flexito OmniAI also offers system variables for use within the condition node.
Email Conditions
These relate to email nodes where specific emails are sent, delivered, or clicked.
Condition | Explanation |
|---|---|
Email Click | Whether a specific email is clicked |
Email Opened | Whether a specific email is opened |
Email Delivered | Whether a specific email is delivered |
Email Sent | Whether a specific email is marked sent |
Opted-In for Email | Whether a bot user has been opted-in for emails |
True/False Conditions (Boolean)
These refer to boolean variables indicating whether a condition or variable is true or false.
Condition | Explanation |
|---|---|
Subscribed to bot | Whether a bot user is subscribed to bot or isnt |
Has Interacted in last 24h | Whether a bot user has interacted in last 24 hours of the last interaction |
Is Guest User | Whether a user is a guest user |
Is Tester | Whether the user is a tester |
Is Admin | Whether the user is an admin |
Is assigned to agent | Whether the bot user has an assigned agent |
Has SSO user connected | Whether user has SSO connected |
Is Business Hours | Whether the time of interaction is within specified business hours |
Is assigned agent online | Whether the bot user’s assigned agent is online or not |
Has agents online | Checks if any live agent is assigned or not |
Integer/Numerical Conditions
Condition | Explanation |
|---|---|
Opted-In Date (minutes ago) | Represents minutes since the bot user has subscribed to bot |
Last seen (minutes ago) | Represents minutes since the bot user has last seen the message sent by the bot |
Last interaction (minutes ago) | Represents minutes since the bot user last interacted with the bot flow |
Last agent interaction (minutes ago) | Represents minutes since the live agent last interacted with the bot user |
Opted-In for Email (minutes ago) | Represents minutes since the bot user has been opted in for email |
Opted-In for SMS (minutes ago) | Represents minutes since the bot user has been opted in for SMS |
Shopping cart total price | Represents the total price of the cart present in ORDER JSON system,field |
Agent Id | System ID of the live agent |
Last FB Comment is existing user |
|
Last FB Comment total new tagged user |
|
Last FB Comment total tagged users |
|
Date/Time Conditions
Condition | Explanation |
|---|---|
Opted-In Date | Date of the user’s opt in |
Last Seen | Datetime field representing the last seen of the bot user |
BOT_CURRENT_TIME | Current time in present represented in workspace timezone |
Created At | Datetime field representing the timestamp the bot user was created |
Last Interaction | Datetime field representing the timestamp of the last interaction by the bot user |
NOW | Current time in present represented in UTC time |
Subscribed | Datetime representing the timestamp the bot user subscribed to the bot |
TODAY | Date field representing the date today |
System Fields Conditions
Condition | Explanation |
|---|---|
Agent Email | Represents the email of the assignedagent |
Agent Name | Represents the name of the assigned agent |
Browser | Represents the browser through which the user is interacting with the bot on web channel |
CRM Contact Id | Represents the unique Id assigned by the integrated CRM. (for eg GHL, Zoho etc) |
Channel | Represents the channel via which the bot user is interacting with bot |
City | Represents the city of the bot user |
Country | Represents the country of the bot user |
Department | Represents the department you want to assign the bot user |
Device | Represents the device via the bot user is interacting with the bot |
Represents the email of the bot user | |
First Name | Represents the first name of the user |
Flow Ns | Represents the the current mainflow Ns of the bot |
GMB Name | Name of the GMB Location |
GMB Place Id | Id of the GMB location |
GTAG Client Id |
|
GTAG Session Id |
|
Gender | Represents the gender of bot user |
IP | Represents the the IP of the bot user on web channel |
Instagram Id | Represents the Meta assigned unique ID of the bot user on Instagram |
Instagram User Name | Represents the Meta assigned user name of the bot user on Instagram channel |
Interest | Represents the interest of the bot user you cn assign |
Language | Represents the language of the bot user |
Last Button Title | Represents the last button the user clicked |
Last FB Comment | Represents the last comment made by the user on Facebook channel |
Last FB Comment Id | Represents the Id of the last comment made by the user |
Last FB Comment Post Id | Represents the Id of the post on which the last comment was made by the user |
Last Name | Represents the last name of the bot user |
Last Node Ns | Represents the Ns value of the node last visited by the bot user |
Last Text Input | Represents the last text input bot user entered |
Lead Source | Represents the source of the bot user you can assign |
Lead Status | Represents the status of the bot user you can assign |
Live Chat Url | Represents the URL link of the livechat of the bot user |
Locale | Represents the locale of the bot user |
Market | Represents the market of the bot user you can assign |
OpenAI Thread Id | Represents the current thread Id by the assistant run from OpenAI |
Page Id | Represents the Id of the facebook page |
Page Name | Represents the name of the facebook page integrated |
Page User Name | Represents the user name of the facebook page’s admin who integrated the page with Flexito OmniAI |
Platform | Represents the platform from which the bot user is interacting with the bot |
Profile Image | Represents the profile image of the bot user |
Region | Represents the region of the bot user |
SSO Url | This contains the SSO Url |
Sub Flow Ns | Represents the NS value of the subflow in which the bot user is currently in |
Timezone | Represents the timezone of the user |
User Id | Represents the User ID assigned by the system of the bot user |
User Name | Represents the username of the bot user |
User Ns | Represents the unique value assigned by Flexito OmniAI to every bot user |
System JSON Fields Conditions
Condition | Explanation |
|---|---|
CART | Represents the line items user has selected when using Flexito OmniAI native ecommerce |
Claude | Represents the chat history of the bot user when using Claude AI |
DialogFlow | Represents the chat history of the bot user when using DialogFlow |
Gemini | Represents the chat history of the bot user when using Gemini |
Last Error | Represents the Last error triggered by the bot user |
Last Message | Represents the last message the bot user went through |
ORDER | Represents the order placed by the bot user when using Flexito OmniAI native ecommerce |
OpenAI | Represents the chat history of the bot user when using OpenAI |
SELECT | Unique JSON that saves the key-value pair from the JSON the user has selected from the previous step. Is used widely in For Each option. |
SHOP | Contains the information regarding the user’s business |
User | Contains the complete information regarding the bot user |
Miscellaneous Conditions
Condition | Explanation |
|---|---|
Segments | Represents the segment the bot user belongs to |
Tag | Represents if the bot user has a certain tag or not |
Label | Represents if the bot user has a certain label or not |
Sequence Subscription | Represents if the bot user is subscribed to a sequence or not |
Closing Notes | Represents the closing notes assigned to the bot user |
Board | Represents the board the bot user currently is assigned to |
Notification Topic | Represents the notification topic assigned to the bot user |
Assigned Agent | Represents whether a certain agent assigned to the bot user |
Channel | Represents the channel the bot user belongs to |
Conversation Status | Represents the status of the bot user’s conversation (Done, Open, Pending etc) |
Custom Input | Allows the user to input custom inputs that doesnt necessarily fit into the various conditions provided by the user. For example using Custom JSON user fields. |