Human-Like Behavior
What this page covers
How Salesflow spaces out LinkedIn actions to simulate human behavior and protect accounts.
This page is only about timing/pacing. Daily caps live on the LinkedIn Limits page.
How Human-Like Pacing Works
-
Per-action minimum gap. Each action type has a base delay between consecutive sends from the same account.
-
Randomized buffer (jitter). We add a small extra delay to avoid robotic, fixed intervals.
-
Seconds-based retry signal. If a request arrives too soon, we return HTTP 429 with
Retry-After: <seconds>.
This value is always a number of seconds and relates only to pacing, not to daily caps.
If you ever see Retry-After as a date/time, that’s not pacing — see LinkedIn Limits (daily caps & protective cooldowns).
Action Delays
To mimic natural behavior and avoid detection, all actions are processed with a base delay + randomized buffer:
|
Action Type |
Base Delay (sec) |
Random Buffer (sec) |
|---|---|---|
|
Invitation |
10 |
+0–10 |
|
Invitation with note |
20 |
+0–10 |
|
Follow-up |
20 |
+0–10 |
|
Open InMail |
20 |
+0–10 |
|
Profile View |
20 |
+0–10 |
|
Withdraw Invitation |
1 |
+0–10 |
How to read this: The first action has no wait; each subsequent action of the same type & account waits base delay + random buffer from the last send of that type.
Examples of Action Delays
Scenario 1 – Same action type to multiple profiles
-
Invite to Profile A → no delay
-
Invite to Profile B → delay
(10 + 0–10 secs)from Invite to A -
Invite to Profile C → delay
(10 + 0–10 secs)from Invite to B
Scenario 2 – Different action types to the same profile
-
Invite to Profile A → no delay
-
Open InMail to Profile A → no delay
-
Follow-up to Profile A → no delay
Scenario 3 – Mixed actions to multiple profiles
-
Invite to Profile A → no delay
-
Open InMail to Profile A → no delay
-
Invite to Profile B → delay
(10 + 0–10 secs)from Invite to A -
Open InMail to Profile B → delay
(20 + 0–10 secs)from previous InMail
Client Handling (pacing)
-
On 429, read
Retry-After(seconds). -
Wait that many seconds, then retry the same request.
-
Keep retries idempotent; avoid blasting parallel actions for the same account/action type.
Tips
-
Avoid sending too many queued actions in bulk within a short timeframe.
-
Send Request only in Working hours to simulate Human Behavior
See also: LinkedIn Limits (per-account daily caps, self-serve limits, date-based retry)