# How to Use Conditions in ZazzyAgent Flow Builder

A condition lets your automation make a decision.

Instead of sending every customer through the same path, you can check information and choose what happens next.

For example:

> If customer budget is above ₹50,000 → Premium path.

> Otherwise → Standard path.

Conditions are one of the most useful tools for building personalized automation.

## What is a condition?

A condition checks whether information meets a rule.

Example:

**City = Mumbai**

If true:

> Send Mumbai-specific information.

If false:

> Continue with the standard flow.

## What can a condition check?

Depending on the available configuration, conditions can use information such as:

*   System fields
    
*   Custom fields
    
*   Customer information
    
*   Other supported subscriber data
    

The current Flow Builder condition system supports multiple conditions and operators such as equals, contains, starts with and numerical/date comparisons.

## Create a condition

Open your Flow Builder flow.

Add a Condition node at the point where you want the automation to make a decision.

Select the field you want to evaluate.

Choose an operator.

Enter the value to compare.

## Equals

Example:

**Customer Type = VIP**

If the customer is marked as VIP, continue down the matching path.

## Contains

Useful for text that may contain additional words.

Example:

**Product Interest contains shoes**

A value such as:

> Running Shoes

could match.

## Starts With

Useful when values follow a predictable structure.

Example:

**Order Number starts with ORD**

## Number comparisons

You can compare numerical values.

Example:

**Budget > 50000**

This lets you create different paths based on customer budgets or other numerical information.

## Date comparisons

Date-based conditions can be useful when comparing dates stored in supported fields.

Examples:

*   Appointment date
    
*   Subscription date
    
*   Customer date
    
*   Other stored dates
    

## Multiple conditions

You can combine multiple rules within a condition.

Example:

**Customer Type = VIP**

AND

**City = Mumbai**

Only customers matching both conditions follow that branch.

## AND vs OR

### AND

Every condition must be true.

> VIP AND Mumbai

The customer must satisfy both.

### OR

At least one condition must be true.

> Mumbai OR Delhi

The customer can match either.

Use the logic that matches the business rule you're trying to create.

## Example: Lead qualification

Suppose you collect:

**Budget**

**Product Interest**

Then you can create:

**Budget ≥ ₹50,000**

AND

**Product Interest = Enterprise**

↓

High-value lead

Otherwise:

↓

Standard lead

## Conditions with User Input

This is one of the most useful combinations.

Example:

User Input asks:

> What's your budget?

Customer:

> 60000

Save:

**Budget = 60000**

Then:

**Condition**

> Budget >= 50000

↓

Send premium product options.

The User Input collects the data.

The Custom Field stores it.

The Condition decides what happens.

## Conditions with labels

If your automation uses labels, conditions can also help route customers based on supported subscriber information.

Example:

> VIP customer

→ VIP support flow

Otherwise:

→ Standard support flow

## Conditions with sequences

Where supported, sequence-related customer state can be used to create different automation paths.

Example:

> Customer already in follow-up sequence

→ Don't start another duplicate sequence.

## Create a True and False path

A typical condition produces two logical outcomes:

**True**

The rule matched.

**False**

The rule didn't match.

Example:

> Customer Type = Business

**True → Business flow**

**False → Consumer flow**

## Why isn't my condition working?

Check the value being tested.

Suppose your field contains:

> Mumbai

but your condition checks:

> mumbai

Depending on the comparison behavior, capitalization or formatting may matter.

Also check:

*   Correct field selected
    
*   Correct operator selected
    
*   Correct comparison value
    
*   Field actually contains a value
    
*   Previous flow step successfully saved the data
    
*   Correct TRUE/FALSE path is connected
    

## Don't create conditions before collecting the data

A condition can't make a useful decision if the information it needs hasn't been collected.

Bad flow:

**Condition**

> Budget > ₹50,000

before asking for budget.

Better:

**Ask Budget**

↓

**Save Budget**

↓

**Check Budget**

↓

**Choose path**

## Keep conditions understandable

A flow with dozens of nested conditions can become difficult to maintain.

Break complicated logic into smaller sections where possible.

For example:

**Lead Qualification**

↓

Budget Check

↓

Product Check

↓

Location Check

This is easier to understand than one giant decision node.

## A practical formula

A useful automation pattern is:

**Collect**

→ **Save**

→ **Check**

→ **Branch**

→ **Act**

Example:

**What product are you interested in?**

↓

Save Product Interest

↓

**Product Interest = Enterprise**

↓

Enterprise Flow

This simple pattern can power a surprisingly large number of business automations.

[zazzyagent.com](http://zazzyagent.com)