Condition Node

Condition Node Overview

What the Condition Node does

• Evaluates user data (tags, fields, follower status)
• Splits the flow into different paths
• Ensures users receive relevant messages, not generic ones

Typical uses:

• Check if a user is already tagged
• Check if a field has a value
• Check if a user follows your Instagram account
• Route users based on previous answers

Where to use a Condition Node

• After a Trigger (to route users immediately)
• After a User Input Node (to evaluate answers)
• Before sending offers, links, or gated content
• At any point in a flow to check whether the user is a follower and prompt them to follow if needed

How Condition paths work

A Condition Node always evaluates to either true or false.

• If the condition is true, the flow continues through the green handler
• If the condition is false, the flow continues through the red handler

Each handler represents a different path in the flow and must be connected to the next appropriate node.

Important notes:

• Only one path is taken when the condition is evaluated
• Every Condition Node should have both handlers connected to avoid broken flows
• Clear labeling of each path helps prevent logic errors

This visual separation makes it easy to understand and control how users move through different scenarios in the flow.

Using Tags, Fields and Function in Conditions

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

Using Tags in conditions

Tags represent boolean state (present or not present). Tag conditions check whether a contact has one or more specific tags. Tags are commonly used to track user behavior or status.

Common tag-based checks:

• Has tag lead
• Does not have tag customer
• Has participated in a campaign
• Has already received a discount

Example logic:

• If user has tag “VIP” → show VIP message
• Else → show standard message

Tags are ideal when you only need yes/no logic

 Using Fields in conditions

Fields store values, not just state.

Fields can be:

• Text
• Number
• Date
• Boolean

Examples of field-based checks:

• Field city equals “London”
• Field age greater than 18
• Field email is not empty

Fields are ideal when:

• You need comparisons
• You store user answers
• You need more detailed routing

Combining Tags and Fields

In many flows, you’ll use both:

• Tags to represent state
• Fields to  check stored values

Example:

• If user has tag “lead” AND field “budget” > 100
  → send premium offer

This keeps flows readable and scalable.

Using Function in conditions

Follower Check & Smart Follow Logic

The Follower Check is a special type of condition that verifies whether a user currently follows your Instagram account.

What follower check does

• Checks real-time follow status
• Routes users based on whether they follow or not
• Enables “follow-gated” automations

Typical outputs:

• Follower = Yes
• Follower = No

Smart Follow Logic (best practice)

Instead of asking users to follow immediately, a smart approach is:

1. Provide value first (info, preview, benefit)
2. Check follower status
3. If not a follower:
4. • Ask them to follow to continue
4. If already a follower:
5. • Continue without interruption

This approach:

• Feels more natural
• Converts better
• Reduces friction

⚠️ Important notes:

• Follower status can change at any time
• Always design a fallback path
• Do not loop endlessly asking users to follow

ALL / ANY Logic Explained with Examples

When using multiple conditions inside a Condition Node, you must choose how they are evaluated.

ALL logic (ALL conditions must be true)

ALL logic means:

• Every condition must be met
• If even one fails, the path is false

Example:

• Has tag lead
• AND field country equals “US”
• AND follower = yes

Only users who meet all three conditions go down the “true” path.

Use AND when:

• You need strict qualification
• You want precise targeting

ANY logic (ANY condition can be true)

ANY logic means:

• At least one condition must be met
• If one is true, the path is true

Example:

• Has tag VIP
• OR field purchase_count > 3

Use OR when:

• You want broader inclusion
• Multiple criteria lead to the same outcome

Best practice:

• Keep conditions readable
• Split complex logic into multiple Condition Nodes
• Name branches clearly