Skip to content
AP3K
docs
Flow Builder/Conditions Node: Branch a Flow with Yes and No Paths

Conditions Node: Branch a Flow with Yes and No Paths

On this pageSetupAvailable condition typesCollect the data firstExample

A Conditions node checks a value and sends the contact down one of two paths: Yes when it matches, or No when it does not.

Setup

Add a Conditions step, choose the condition type, select a comparison and enter a value where required. Wire both branches to their next steps.

Available condition types

  • If user followed me.
  • If business follows user.
  • Verified on Instagram.
  • Followers count.
  • Opened a tracked link.
  • Contact email or phone.
  • A custom field.

Comparisons include Equals, Does not equal, Contains, Greater than, Less than and Has a value. Choose one that fits the data being checked.

Collect the data first

Email, phone and custom fields should be collected or set before the check. Use Has a value when you want to skip a collection prompt for someone whose information is already stored.

Instagram profile conditions are verified when the step runs. Unavailable profile data does not qualify, so provide a useful fallback path.

Example

Trigger → Conditions: Contact email has a value → Yes: send the resource → No: collect email, then send the resource.

An unwired branch ends the path. Test both outcomes so a missing field does not silently strand a contact.

Was this page helpful?