Make decisions in Flows by Condition Node
This tutorial explains how the Condition Node works in Elpidan and how it is used to control the path of a flow. It helps you build automations that react differently based on user tags, stored field values, or follower status.
****Here : movie 07****
The Condition Node allows you to make decisions inside a flow.
It checks whether one or more conditions are true or not and then routes the user to the appropriate path. It is used whenever you need logic-based decisions inside an automation.
Unlike the Instagram Node (which only sends content), the Condition Node controls logic.
When you click on it, you can define one or multiple conditions.
Conditions can be based on:
• User tags
• User Custom Fields
• Function
What are Tags and Fields in Elpidan
Before using the Condition Node, it is helpful to understand what tags and fields are.
Tags are simple labels used to group and segment users based on status, behavior, interests, or actions. Fields are used to store actual user data, such as name, email, phone number, score, or any other value you want to save for later use in your flows.
👉If you want to create and manage your tags, go to the Tags Menu.
👉If you want to review the available fields or create additional custom fields, go to the Custom Fields Menu
User Tag:
You can check whether a user has a specific tag, such as “Lead”
User Custom Fields:
For example, you can check whether “contest_score” is greater than 50,
or whether “total_purchases_count” is equal to or greater than 1,
or whether the user’s “gender” field is equal to “Male.”
Function:
In the Function section, you can check whether the user is currently a follower of your Instagram page and route the flow accordingly.
This is especially useful if you want to create a follow-required flow.
You can send some initial information first
and then check if the user is a follower.
If the user is not following the page, you can ask them to follow before continuing.
ALL / ANY Logic
If you add more than one condition, you must define the logic type.
There are two options:
All – all conditions must be true
Any – at least one condition must be true
If the defined logic is satisfied, the flow continues through the “True” path, which is shown in green.
If not, it continues through the “False” path, which is shown in red.
This is how you create multi-branch and intelligent automation flows.
👉To explore the Condition Node options in more detail, read the Condition Node guide
Was this article helpful?
Didn't find your answer?
Contact us