Skip to main content
A condition splits a sequence into a Yes path and a No path, based on a fact about the contact or something that already happened. Insert one anywhere on the canvas, the same way you insert a step.
A condition node reading Replied? with a within 5 days field, its Yes edge running to one step and its No edge to another, each edge labelled with how many contacts took it.

A condition on the canvas, branching into Yes and No.

Insert a condition

1

Open the step picker

Point at the gap between two steps, click Add a step here, and scroll to Then check….
2

Pick the question

Choose from Has an email address?, Has a LinkedIn URL?, Already connected?, Email bounced?, Replied? and Has an open profile?.
3

Set the window

Time-bound conditions ask within how many days to decide. Both branches then keep running on their own.

Read the branches

Each branch is named Yes or No, and once the sequence has run, with how many contacts took it. A condition with nothing to check yet is greyed out in the step picker. Email bounced?, for example, needs an email step earlier in the path.

Good to know

When the condition answers. After Replied? within 5 days, a step that waits 2 days goes out 7 days after the email. A condition with no window answers the moment a contact reaches it.
They keep going down whatever is connected there. If nothing is, the sequence ends for them. Add a step there later, and they go on to it.
It needs an earlier step it can check against. The greyed-out row names exactly what is missing.
Already connected? answers yes when the sender’s LinkedIn account is connected to the contact and Oneprofile has seen it. That means an accepted connection request, or an earlier LinkedIn step that found them connected on their profile.A conversation alone doesn’t count, and a connection no step has seen reads as no.
Has an open profile? looks for a free-to-message LinkedIn Premium profile. When that is not already known, a profile view checks it first.
Yes, by dragging each of its steps onto Move here on the other side. A condition or a connection request brings its branches with it. See Build a sequence.
Yes. Deleting a condition keeps the branch that has steps on it, joined to whatever came before. When both branches have steps, it asks which one carries on, and the other goes with the condition. Deleting a Send connection request asks the same way. See LinkedIn steps.
A Send connection request step answers that question itself now. It branches on the person’s answer, into Connected and Not accepted, so the check left the Then check… group.Sequences that already have the check keep it, and it keeps working. A check placed right after its request is now part of that request. See LinkedIn steps.

Next steps

Build a sequence

Add steps and conditions to the canvas.

LinkedIn steps

Branch on the answer to a connection request.

Tasks

Approve the steps a sequence holds for a person.