Human-Like Behavior
How Human-Like Behavior Works in Salesflow
Salesflow enforces rate limits and smart delays on all LinkedIn actions to simulate human behavior, ensure account safety, and comply with LinkedIn’s usage policies.
Daily Action Limits
Each LinkedIn account connected to Salesflow is subject to the following default daily limits:
|
Action Type |
Default Limit (per day) |
|---|---|
|
Invitations (without note) |
15 |
|
Invitations with note |
15 |
|
Follow-ups |
20 |
|
Open InMails |
20 |
|
Profile Views |
20 |
|
Withdraw Invitations |
40 |
Recommendations:
All limits are account dependent and it is recommended to start on lower end
|
Action Type |
Recommended |
|---|---|
|
Invitations (without note) |
100/week |
|
Invitations with note |
• Basic license: up to 30/week |
|
Follow-ups |
100/day |
|
Open InMails |
• Basic: up to 30/day |
|
Profile Views |
• Basic: up to 50/day |
|
Withdraw Invitations |
50 - 100 /day |
Once a daily limit is reached, no further actions will be executed until the next day Salesflow automatically enforces a cool-down period and a Retry-After header.
Custom Limits Available
Upon request, these limits can be increased or fully removed for specific accounts. This is typically granted to old and well performed LinkedIn Accounts.
Please contact your Salesflow Support Representative (Intercom) to request a custom limit configuration.
Self-Serve Limits (Coming soon)
What you’ll get
-
See current limits per action and how many actions remain today.
-
Update limits per action at any time (changes apply immediately).
-
Works per connected LinkedIn account.
Why this matters
-
Safe onboarding with conservative defaults.
-
Fast adjustments when an account proves stable.
-
No waiting on Support.
Endpoints (preview)
-
GET
/accounts/{accountId}/limits
Returns current per-action limits and today’s remaining counts. -
PUT
/accounts/{accountId}/limits
Increase or decrease limits per action (set the numbers you want).
Action Delays
To mimic natural behavior and avoid detection by LinkedIn, 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 |
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 Profile A
-
Invite to Profile C → delay (10 + 0-10 secs) from Invite to Profile 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 Profile A
-
Open InMail to Profile B → delay (20 + 0-10 secs) from Open InMail to Profile A
Rate-Limit Handling
When LinkedIn returns a "429 Too Many Requests" response, Salesflow automatically enforces a cool-down period and a Retry-After header will be included in the response, indicating how many seconds to wait before retrying.:
|
Rate Limit Triggered |
Pause Duration |
|---|---|
|
Too many Open InMails |
24 hours (1440 min) |
|
Too many Invitations |
24 hours (1440 min) |
Actions of that type will be paused during this period to prevent further blocks or restrictions.
Tips
-
Avoid sending too many queued actions in bulk within a short timeframe.
-
Send Request only in Working hours to simulate Human Behavior