What this page covers
Per-account daily caps for LinkedIn actions, how to read/update them, and how to react when a cap (or LinkedIn’s own protections) is hit.
Pacing/timing lives on Human-Like Behavior.

What Is LinkedIn Limits?

LinkedIn limits are daily/weekly restrictions that control how many actions (e.g., connection requests, messages, profile views) a user can perform within a period. They exist to prevent spam/abuse and to keep accounts healthy.

What Happens If You Hit the Limits?

• Actions may fail silently or return errors.

• The account can be temporarily restricted.

• CAPTCHA, email verification, or 2FA challenges may be triggered.

How Salesflow Handles Limits

Salesflow uses:

• Daily limiting per action, per account (configurable).

• Protective cooldowns after LinkedIn “too many requests” responses.

This combination maximizes throughput without putting your account at risk.

Default Daily 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. We recommend starting on the lower end and adjusting upward only when the account proves stable.

Action Type	Recommended
Invitations (without note)	100/week
Invitations with note	• Basic: up to 30/week • Premium / Sales Nav: 100/week
Follow-ups	100/day
Open InMails	• Basic: up to 30/day • Sales Nav: 50/day
Profile Views	• Basic: up to 50/day • Sales Nav: up to 100/day
Withdraw Invitations	50–100/day

Self-Serve Limits

Manage limits per account through our API. Changes apply immediately.

What you can do

• Read current caps and today’s remaining counts per action.

• Update selected caps at any time.

API Reference

• GET /api/v1/accounts/{accountId}/limits — Account Limits: Get
  Link

• PATCH /api/v1/accounts/{accountId}/limits — Account Limits: Patch
  Link

Important

• ignoreLimits = true disables server-side enforcement entirely for that account — both daily caps and pacing. Use with care.

Response Behavior (cap reached or LinkedIn push-back)

• We return HTTP 429 with Retry-After: <RFC1123 date/time> — wait until that time, then retry.
  You’ll see this date-based Retry-After when:

  • the account reached its daily cap for the action, or

  • LinkedIn returned “too many requests”, and we applied a protective cooldown for that action.

• If you raise a limit via API, the new cap is used immediately for subsequent sends.

• If you lower a limit and today’s usage already exceeds it, we’ll pause further sends of that action until allowed again.

Best Practices

• Start conservative for new/cold accounts; increase gradually as they prove stable.

• Avoid large jumps; monitor delivery results and webhook activity.

• Don’t build your own throttling on top — simply honor our Retry-After signals.

Developer Checklist (limits + pacing together)

• Always handle 429:

  • Retry-After: <seconds> → short delay → wait seconds and retry.

  • Retry-After: <date/time> → cooldown until that time → schedule retry, not before.

• Keep requests idempotent; dedupe your own retries.

• Avoid parallel bursts for the same account/action type.

See also: Human-Like Behavior (pacing rules & seconds-based retry) • API Reference → Account Limits (GET/PATCH)