Who this is for: Recruiters on the Custom Plan who want to route recipients to different channels automatically based on their LinkedIn connection status.

What branching does

Conditional branching lets a sequence take two different paths depending on whether a condition is met for a recipient. Instead of treating every recipient the same, branching routes each person through the steps most likely to get a response from them.

The most common use case: send a LinkedIn message to candidates you're already connected with, and fall back to email for everyone else automatically, with no manual sorting.

Branching is available on the AIRA Plan only. On other plans, the branching option is visible in the builder but greyed out with an upgrade prompt.

How it works

A branch is a decision point in the sequence. When a recipient reaches it, Recruiterflow evaluates the condition and routes them down one of two paths:

Yes path — taken when the condition is met
No path — taken when the condition is not met

Each path can have its own steps, delays, and even further branches. After both paths complete, the sequence can continue with shared steps, or end independently per path.

Available branch conditions

Currently, two conditions are supported:

Is LinkedIn connection

Evaluates whether the sender and recipient are already first-degree connections on social media at the time the branch is reached.

Yes path: sender and recipient are connected on social media
No path: they are not connected

Typical setup: Yes path → social media message step. No path → Automated Email step.

Accepted LinkedIn connection

Evaluates whether the recipient accepted a social connection request that was sent earlier in the sequence, within a configurable number of days.

Yes path: connection request was accepted within the specified window
No path: request was not accepted (pending, declined, or no request was sent)

Typical setup: Add a Social Connection Request step → branch on "Accepted LinkedIn connection" → Yes path sends a Social Message, No path sends an email.

When configuring this condition, set the check window: the number of days after the connection request was sent during which Recruiterflow watches for acceptance. If the recipient accepts within this window, they go down the Yes path. If they haven't accepted by the end of the window, they go down the No path.

How to add a branch to your sequence

In the sequence builder, click the + button between steps where you want to insert the branch
Select Conditions from the top-right step type options
Choose your condition from the dropdown
If using "Accepted LinkedIn connection", set the check window in days
Add steps to the Yes path and the No path independently using the + buttons on each arm
Save each step as you build

Rules and constraints

A sequence cannot end on a branch. Both the Yes and No paths must contain at least one step each. If either path is empty at launch time, the sequence will fail validation and the Launch button stays disabled.
Both paths are evaluated independently. Recipients on the Yes path don't skip No path steps, they simply never reach them.
Branches can be nested. You can add another branch inside the Yes or No path of an existing branch.
The branches-count shown in analytics counts the total number of branch nodes in the sequence, not the number of paths.
Branching requires Social integration to be connected for the relevant senders when using Social-based conditions. Recipients whose sender doesn't have Social connected will error out at the branch evaluation point.

Example: Connection-first outreach flow

Here's a practical sequence structure using branching:

Step 1 — Automated Email (Day 0): Initial outreach email
Step 2 — LinkedIn Connection Request (Day 2): Send connection request with a short note
Branch (Day 5): "Accepted LinkedIn connection" within 3 days?
- Yes path — Social Message (Day 0 from branch): Follow up with a direct message
- No path — Automated Email (Day 0 from branch): Follow up via email instead
Step after branch — Task: Call (Day 3): Both paths converge to a manual call task