If/Else Statement

• Only update high-value deals
• Skip contacts without email addresses
• Route based on deal stage
• Check if variables exist before using them
• Different actions for different scenarios

​

What This Does (The Simple Version)

​

How It Works

• Actions immediately after the If Condition run
• Continues until it reaches an Else Condition or End Condition

• Actions after the If Condition are skipped
• Jumps to Else Condition (if present) or End Condition

​

Setting It Up

​

Step 1: Add If Condition Action

​

Step 2: Write Your Condition

The deal amount is greater than 10000

The contact email is not empty

The last contact date was within the last 7 days

The search results variable is not empty

The contact lifecycle stage equals "salesqualifiedlead"

[deal amount] > 50000

​

Step 3: Add Actions to Run If True

1. If Condition - Check if deal amount greater than 10000
2. Update HubSpot Object - Update to VIP status (runs if TRUE)
3. Send Email - Notify sales director (runs if TRUE)
4. End Condition - Marks end of if block

​

Step 4: Add Else Condition (Optional)

1. If Condition - Check if contact has email
2. Send Email - (runs if TRUE)
3. Else Condition
4. Create Task - Manually find email (runs if FALSE)
5. End Condition

​

Step 5: Close with End Condition

​

Condition Examples

​

Numeric Comparisons

[deal amount] > 10000
[relevance_score] >= 8
[contact_count] < 5

​

String Comparisons

[contact lifecycle_stage] equals "lead"
[deal stage] is "closedwon"
[company industry] contains "technology"

​

Empty/Exists Checks

[contact email] is not empty
[search_results] has items
[timeline_events] is empty
The contact has a phone number

​

Date Comparisons

[deal closedate] is in the future
[contact lastmodifieddate] is within last 30 days
The last activity was more than 7 days ago

​

Boolean Checks

[enrichment_complete] is true
[contact emailoptout] equals false
The contact has not unsubscribed

​

Complex Conditions

The deal amount is greater than 50000 AND the deal stage is "presentationscheduled"
The contact has an email OR a phone number
The lifecycle stage is "lead" or "marketingqualifiedlead"

​

Common Workflows

​

Only Update High-Value Deals

1. Lookup HubSpot Object (V2)
   • Get deal details
   • Output Variable: deal
2. If Condition
   • Condition: [deal amount] > 50000
3. Update HubSpot Object (V2) (inside if block)
   • Update priority to “High”
4. End Condition

​

Skip Contacts Without Email

1. Search HubSpot (V2)
   • Find contacts
   • Output Variable: contacts
2. For Loop
   • Loop through: contacts
   • Current item: current_contact
3. If Condition (inside loop)
   • Condition: [current contact email] is not empty
4. Send Email (inside if block)
   • Send to: [current contact email]
5. End Condition
6. End Loop

​

Route by Deal Stage

1. Lookup HubSpot Object (V2)
   • Get deal
   • Output Variable: deal
2. If Condition
   • Condition: [deal stage] equals "closedwon"
3. Create Timeline Event (if won)
   • Log onboarding kickoff
4. Else Condition
5. Update HubSpot Object (if not won)
   • Update follow-up date
6. End Condition

​

Check Before Using Variable

1. Search HubSpot (V2)
   • Search for deals
   • Output Variable: deals
2. If Condition
   • Condition: [deals] is not empty
3. For Loop (inside if block)
   • Loop through deals
4. Process each deal…
5. End Loop
6. End Condition

​

Real Examples

​

Lead Qualification

[contact company] is not empty AND [contact jobtitle] contains "Director" or "VP" or "C-level"

• Update lifecycle stage to “salesqualifiedlead”
• Assign to senior sales rep
• Send immediate notification

• Keep as “lead”
• Add to nurture sequence

​

Deal Health Check

The last activity was more than 14 days ago

• Update deal property status to “stale”
• Create task for owner to follow up

​

Conditional Enrichment

[contact company] is not empty AND [contact lifecycle_stage] equals "salesqualifiedlead"

• Run web search for company
• AI enrichment analysis
• Update contact with insights

• Log that contact wasn’t enriched
• Add to later enrichment queue

​

If/Else Patterns

​

Simple If (No Else)

1. If Condition
2. Action (runs if true)
3. Action (runs if true)
4. End Condition
5. Action (always runs)

​

If/Else

1. If Condition
2. Action (runs if true)
3. Else Condition
4. Action (runs if false)
5. End Condition
6. Action (always runs)

​

Multiple Conditions (Nested)

1. If Condition - Check A
2.   If Condition - Check B (nested)
3.     Action (runs if both A and B are true)
4.   End Condition
5. End Condition

​

Sequential Checks

1. If Condition - Check if deal > 10000
2.   Update to "High Priority"
3. End Condition

4. If Condition - Check if deal > 50000
5.   Notify VP Sales
6. End Condition

​

Troubleshooting

​

Condition Always TRUE (or Always FALSE)

1. Condition is written incorrectly
2. Variable doesn’t exist
3. Variable has unexpected value

1. Check execution log - what did the AI evaluate?
2. Test condition with known values first
3. Use simple conditions initially (e.g., 5 > 3 should always be true)
4. Make sure variables exist before referencing them
5. Check variable values in execution log

​

Can’t Access Variables

1. Variable doesn’t exist (action before if condition failed)
2. Variable name spelled wrong
3. Wrong path to nested property

1. Check execution log - does the variable exist?
2. Verify variable name matches output from previous action
3. For nested properties: [contact email] not [contact.email]

​

Actions After If Condition Not Running

1. Condition evaluated to FALSE
2. Missing End Condition
3. Error inside if block

1. Check execution log - what was the condition result (true/false)?
2. Add End Condition after if block
3. Look for errors in actions inside the if block

​

Else Block Not Running

1. Missing Else Condition action
2. Else Condition in wrong place
3. Missing End Condition

1. Structure must be: If Condition → [true actions] → Else Condition → [false actions] → End Condition
2. Make sure Else Condition is before End Condition
3. Check execution log to see execution path

​

Tips & Best Practices

• Write conditions in plain English (AI evaluates them)
• Use clear, simple conditions when possible
• Always add End Condition to close if blocks
• Test conditions with known values first
• Check execution log to see true/false result
• Use variables by clicking {} button for accuracy
• Add Else Condition for “if false” actions

• Forget to add End Condition (required)
• Reference variables that might not exist without checking first
• Write overly complex conditions (break into multiple if statements)
• Assume condition will always evaluate as expected (test it)
• Nest too many if conditions (hard to debug)

• Clear: “The deal amount is greater than 10000”
• Specific: “The contact lifecycle stage equals ‘salesqualifiedlead’”
• Testable: Use values you can verify
• Safe: Check if variable exists first if unsure

• Conditions evaluate quickly (less than 1 second)
• Simple conditions faster than complex
• Avoid unnecessary nesting

​

Related Actions

• End Condition - Required to close if blocks (can close If, For, or If/Else)
• Set Variable - Often used inside if blocks

• Use inside For Loop to conditionally process items
• Use with Update HubSpot Object (V2) to conditionally update

• Variable System - Using variables in conditions