The “If profile connected” condition checks whether you are already connected with a prospect on LinkedIn and routes them through your workflow accordingly. Understanding how this condition’s monitoring timeframe works is key to avoiding unexpected delays.
This article explains how the condition behaves, common mistakes, and best-practice setups.
What the “If Profile Connected” condition does
This condition evaluates whether the prospect is a 1st-degree LinkedIn connection at the moment the condition is checked.
It has two possible paths:
Yes path → The profile is already connected
No path → The profile is not connected
Understanding the timeframe (monitoring window)
The timeframe you select is not a delay timer in the traditional sense — it is a monitoring period.
Here’s how it works:
During the selected timeframe, the system checks the condition every day
If the condition becomes true at any point, the workflow:
Immediately proceeds down the Yes path
If the condition is never met, the workflow:
Waits until the timeframe ends
Then proceeds down the No path
Example
If “If profile connected” is set to 7 days:
If the prospect accepts your connection on day 2 → workflow continues immediately
If they never accept → workflow waits the full 7 days, then follows the No path
Why workflows sometimes feel “stuck”
A common issue is placing “If profile connected” with a multi-day timeframe at the very beginning of a workflow.
When this happens:
The system waits for the entire monitoring period before taking any action
This can look like the workflow is paused or delayed
Best-practice workflow placement
When checking for accepted connection requests
Use this setup:
Invite to connect
If profile connected (7-day monitoring window)
This allows the system to wait for the connection request to be accepted, then immediately continue once it happens.
Important recommendation for prioritizing 1st degree connections
If you have “If profile connected” conditions set at the start of a workflow to prioritize actions on first degree connections, they should almost always be set to No delay.
This allows the workflow to route immediately without waiting.
Summary
The timeframe on “If profile connected” is a monitoring period, not a fixed delay
The workflow proceeds immediately once the condition is met
If the condition is never met, the workflow waits for the full timeframe before continuing
Use 7-day monitoring only when waiting for a connection invite to be accepted
Use No delay when checking existing connections
Following these guidelines will keep your workflows fast, predictable, and running exactly as intended.