Skip to main content

Build smarter LinkedIn sequences with the “Is in my LinkedIn Network” condition

Updated today

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 True/False paths, and manage daily checks safely using LinkedIn limits.

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 (no “dummy” invite steps) 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 where you’ll add the condition

Campaigns page with Create campaign button highlighted
  1. Go to Campaigns from the left sidebar, then click Create campaign.
    Why: The condition is added inside a sequence, so you’ll start from the Campaigns area.

Create manually option with Create manual campaign button highlighted
  1. Choose Create manually (Create manual campaign).
    Why: Manual creation gives you direct control to add a Condition step and design your branching logic.

Phase 2: Add the “Is in my LinkedIn Network” condition

Conditions tab and Check if user in my LinkedIn network condition highlighted
  1. In the sequence builder, open the Conditions tab.
    Why: Conditions are how you create decision branches (True/False paths) inside one sequence.

  2. Select Check if user in my LinkedIn network (LinkedIn).
    Why: This triggers a check to see whether you and the lead are already 1st-degree connections.

Phase 3: Design your True/False paths (what happens next)

  1. After adding the condition, build out both branches in the canvas: on the True path (Yes, already connected), add a LinkedIn message step; on the False path (No, not connected), add a LinkedIn invitation step. Then add a wait step (or any follow-up steps) on each branch as needed, and make sure the right-side panel shows the correct LinkedIn account used to execute this condition (and the daily limit notice).
    Why: You can message immediately when you’re already connected, and only send invitations when they’re actually needed.

    Sequence canvas showing Is in LinkedIn network condition branching to Yes/No paths, with LinkedIn account selection and daily limit notice in the right panel
  2. Click a step (for example, the Chat message) to edit its content in the right panel.
    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 True path

  • No → the lead follows the False path

Account Safety & Daily Limits (Important)

Checking LinkedIn relationships requires querying LinkedIn profiles. To keep activity safe and natural, this condition is subject to a daily limit:

  • 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

Best practice: Keep limits conservative, especially on newer LinkedIn accounts, and only use this condition where it meaningfully changes the flow.

Practical Application (Real-Life Example)

Here’s a common, clean branching setup that avoids unnecessary invites:

  • Condition: Is in my LinkedIn Network?

  • True path (already connected): Send a LinkedIn message → Wait 2 days → Send an email

  • False 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:

    • Wait for the next 24-hour window to reset.

    • Lower usage by placing the condition only where it’s truly needed.

    • If appropriate for your account health, adjust the limit in LinkedIn limits settings.

Issue: Worried about LinkedIn restrictions

  • Root cause: Excessive profile checks can appear suspicious.

  • Fix:

    • Keep the daily limit conservative (especially on new or recently warmed accounts).

    • Combine with safe outreach habits like working hours and gradual ramp-up.

Knowledge Check (Quick Quiz)

  • Where should you route leads who are already 1st-degree connections: the True path or the False path?

  • What action would you put on the False path to avoid messaging someone you’re not connected with yet?

  • If checks stop mid-day, what’s the first setting you should review?

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.

  • Stay safe by respecting the daily check limit (default: 30/24h) and using the condition only when it changes the outcome.

Did this answer your question?