Designing Flow with Conditions

A condition is a question your sequence asks about a contact at a specific point in the flow. Each condition produces two outcomes — Yes (condition is true) or No (condition is false) — enabling sequences to route contacts differently based on their profile and engagement.

Available condition categories

Email conditions

• Has Email Address
• Opened Email
• Clicked Email Link
• Unsubscribed from Email
• Replied to Email

LinkedIn conditions

• Has LinkedIn URL
• Has LinkedIn Connection
• Accepted LinkedIn Invitation
• Opened LinkedIn Message
• Replied to LinkedIn Message

WhatsApp conditions

• Has Phone Number
• Replied to WhatsApp Message
• Opened WhatsApp Message

User actions

• Created Calendar Event

Why conditions matter

Conditions enable intelligent and respectful messaging by:

• Preventing failed message attempts — avoid sending WhatsApp messages to contacts without phone numbers
• Respecting preferences — route unsubscribed contacts away from email steps
• Routing engaged prospects — move contacts to your sales team immediately when they reply
• Testing approaches — send different message versions based on engagement signals

How to add a condition

1. In the sequence Editor, click the + button between two steps
2. Select Condition from the panel
3. Choose the condition type (e.g., "Has LinkedIn URL?")
4. Configure the evaluation window if applicable (e.g., "Opened Email within 3 days")
5. Connect the Yes branch to one set of steps and the No branch to another

Example: channel-aware routing

Condition: Has LinkedIn URL?
  → Yes: View LinkedIn Profile → LinkedIn Message
  → No: Send Email instead

This ensures contacts only receive messages through channels where they can actually be reached.

Example: engagement-based branching

Step 1: Send Email
Wait 3 days
Condition: Opened Email?
  → Yes: Send LinkedIn Message (warm follow-up)
  → No: Send follow-up email (cold reminder)

Best practices

• Test logic before publishing — use the Preview tab to trace paths for multiple contact scenarios
• Avoid over-complicating — limit nesting to 2–3 levels of conditions
• Always handle both branches — never leave a Yes or No path without a next step (even if it just ends the sequence)
• Use timeframe conditions carefully — "Opened Email within 3 days" is more precise than "Opened Email" which evaluates any prior open