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
| Condition | Answers Yes when | Timing |
|---|---|---|
| Has email address | The candidate has an email address | Checked right after the step before |
| Has LinkedIn URL | The candidate has a LinkedIn URL | Checked right after the step before |
| Is connected on LinkedIn | The person is already a connection of your LinkedIn account | Checked right after the step before |
| Has verified email address | The address is verified as deliverable (via Bouncer) | Checked right after the step before |
| Accepted invitation | The person accepts the invitation from the step before | Waits up to the chosen number of days |
| Opened email | The person opens an email this flow sent | Waits up to the chosen number of days |
| Clicked link in email | The person clicks a link in an email this flow sent | Waits 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?
Related articles
- HelpBuild an outreach sequenceCreate a flow in the visual builder: start from a template or from scratch, add steps and waits, write the messages and save.
- HelpReplies stop every sequence to that personWhen a candidate replies on LinkedIn or by email, Essentiq stops all sequences to them. What counts as a reply and what doesn't.
- GuideHow to build an outreach sequence, step by stepBuild a LinkedIn and email outreach sequence in Essentiq: templates, steps, conditions, timing and the checks to run before you add candidates.