This guide shows you how to use the Is in my LinkedIn Network condition in lemlist to branch your sequence based on whether a lead is already a 1st-degree LinkedIn connection, without sending an invitation first.
Learning Objective
By the end of this tutorial, you’ll know how to add the Is in my LinkedIn Network condition to a sequence, route leads through Yes/No paths, and manage the daily check limit so your sequence keeps running.
Why This Matters
In real outreach, some prospects are already in your LinkedIn network, others need an invite, and some accept invites outside of lemlist. This condition lets you adapt your outreach to the existing relationship, keeping your sequences clean and your messaging more relevant from the first touch.
Prerequisites
You should already have your LinkedIn account connected to lemlist.
You should already know the basics of creating and editing a campaign/sequence.
Your leads should ideally include a valid LinkedIn URL so lemlist can check the relationship.
Core Lesson — Step-by-Step Workflow
Phase 1: Open or create a campaign
Go to Campaigns from the left sidebar, then click Create to start a new campaign, or open an existing draft campaign where you want to add the condition.
Why: The condition is added inside the sequence builder.
Phase 2: Add the “Is in my LinkedIn Network” condition
In the sequence builder, click Add step, open the Conditions tab, and select Is in LinkedIn network.
Why: This adds a decision point that checks whether the lead is already a 1st-degree LinkedIn connection.
Phase 3: Build the Yes/No paths
After adding the condition, build out both branches in the canvas. On the Yes path (already connected), add a LinkedIn message step. On the No path (not connected), add a LinkedIn invitation step. Then add waits or follow-up steps on each branch as needed.
Why: You can message leads immediately when you’re already connected, and only send invitations when they’re actually needed.Click any step to edit it in the right panel. For example, you can click the Invitation step to write the invite note and premium message.
Why: Each branch can use tailored messaging based on whether you’re already connected.
How the Condition Works
When the condition runs, lemlist checks whether you and the lead are already first-degree connections on LinkedIn:
Yes → the lead follows the Yes path
No → the lead follows the No path
The Daily Network Check Limit
Checking LinkedIn relationships uses a network check, which has its own daily limit in lemlist:
Default limit: 30 checks per 24 hours
You can adjust this in your LinkedIn limits settings
When the limit is reached, lemlist pauses further checks until the next 24-hour window
Network checks are cheap. They are not one of the actions that put your account at risk, and you don't need to count them against your daily LinkedIn action budget. Treat this limit as an execution throttle — if it's set too low, connection-dependent steps stall — rather than as a safety setting. If your sequence relies on this condition, raise the limit so the steps can actually run.
Practical Application (Real-Life Example)
Here’s a common, clean branching setup that avoids unnecessary invites:
Condition: Is in my LinkedIn Network?
Yes path (already connected): Send a LinkedIn message → Wait 2 days → Send an email
No path (not connected): Send LinkedIn invitation → Wait 3–5 days → If no response, send an email (or a second LinkedIn touch, depending on your strategy)
This approach keeps your outreach relevant while preventing invites from being sent to people who are already connected.
Troubleshooting & Pitfalls
Issue: Leads don’t seem to branch as expected
Root cause: Missing or incorrect LinkedIn URLs can prevent accurate checks.
Fix:
Verify your leads have the correct LinkedIn URL field populated.
Test with a small set of leads you know are already 1st-degree connections.
Issue: The condition stops running for some leads
Root cause: You hit the daily check limit.
Fix:
Raise the limit in LinkedIn limits settings — network checks are low-risk, so this is usually the right fix.
Or wait for the next 24-hour window to reset.
Place the condition only where it actually changes the flow, so you're not spending checks unnecessarily.
Issue: Worried about LinkedIn restrictions
Root cause: Restrictions come from your invite, message, and engagement volume — not from network checks.
Fix:
Review the actions that do carry risk: invites, messages, comments, and likes. See Set account limits.
Combine with safe outreach habits like working hours and gradual ramp-up.
In Short
Use Is in my LinkedIn Network to personalize flows based on real LinkedIn relationships.
Avoid unnecessary invitation steps and keep sequences logically clean.
Set the daily check limit high enough that connection-dependent steps aren't blocked — network checks don't put your account at risk.