Conditions Node: Branch a Flow with Yes and No Paths

This is where flows get smart. A Conditions node checks something about the user or contact, then sends them down one of two paths:

• Yes — the condition matched
• Doesn’t match any — it didn’t

Each is its own handle on the right edge of the node, so the flow physically forks on the canvas.

Setup

Add the node → pick a condition type → set the value → wire up both the Yes and Doesn’t-match paths.

Available condition types

Condition	Checks	Use this for
If User Followed Me	Whether they follow you	Gating exclusive content to followers
If Business Follows User	Whether you follow them back	VIP-style flows for accounts you already follow
Verified on Instagram	Whether their account is verified	Routing verified users to a dedicated path
Followers Count	Their follower count, with > / < / =	Offering partnerships to accounts over a threshold
Contact Email	Whether you already have their email saved	Skipping the ask if you already have it
Contact Phone	Whether you already have their phone saved	Same idea, for phone number
Custom Field	Any custom value you’ve stored on the contact	Branching by language, membership tier, etc.

Collect the data first

Email, phone and custom fields only work once they’ve been collected — usually via a Collect user info block earlier in the flow, or a Set user field action. With nothing stored, the check has nothing to match and everyone takes the Doesn’t-match path.

Example

Trigger
  ↓
Conditions: If user followed me
  ├── Yes → Send welcome message
  └── Doesn't match any → Ask them to follow first

Both paths need somewhere to go. An unwired branch is a dead end — the flow simply stops for anyone who lands on it.

Pro Tip

Conditions pair naturally with the Action node: branch on whether someone follows you, then set a field or add a tag on each path, and you’ve classified every contact who comes through the flow.