Skip to content
Essentiq

Sequences & outreach

Conditions and branching in a flow

How the seven conditions work, how Yes and No branches run and how long waiting conditions wait before they answer No.

Updated 2 min read

A condition splits a flow into two branches, Yes and No, and each branch continues with its own steps. Some conditions are checked right away, others wait up to a number of days for something the person does. Add one with Add step → Conditions.

The seven conditions

ConditionAnswers Yes whenTiming
Has email addressThe candidate has an email addressChecked right after the step before
Has LinkedIn URLThe candidate has a LinkedIn URLChecked right after the step before
Is connected on LinkedInThe person is already a connection of your LinkedIn accountChecked right after the step before
Has verified email addressThe address is verified as deliverable (via Bouncer)Checked right after the step before
Accepted invitationThe person accepts the invitation from the step beforeWaits up to the chosen number of days
Opened emailThe person opens an email this flow sentWaits up to the chosen number of days
Clicked link in emailThe person clicks a link in an email this flow sentWaits up to the chosen number of days

Waiting conditions

For Accepted invitation, Opened email and Clicked link in email you set Wait up to a number of days: 7 by default, at most 60. If it happens sooner, the flow continues on Yes right away. Otherwise it continues on No when the time is up.

A few things to know:

  • Opened email is measured with an invisible image. Some email apps (such as Apple Mail) can count as opened, and apps that block images never do. Emails in the flow are sent with tracking when this condition is used.
  • Clicked link in email sends links through a tracking address when the condition is used.
  • Has verified email address answers No if the address is missing, bounces, is risky or can't be checked. Each address is checked at most once every 90 days. Turn on Count catch-all domains as verified only if you accept the extra risk; it is off by default.

Rules the builder enforces

The builder knows what each path already knows. It won't let you send a LinkedIn message unless the step sits under Accepted invitation → Yes or Is connected on LinkedIn → Yes, invite someone you're already connected to, or add a condition whose answer is already known on that path. Steps that break a rule are marked so you can fix them before saving.

You don't need a "has replied" condition: a reply on LinkedIn or by email stops the sequence automatically.

Was this article helpful?