LinkedIn connection request limits and a sending schedule that survives them

LinkedIn does not publish a number. What it publishes is a warning, usually after a burst of connection requests from an account that never sent many before, and the restriction that follows lasts days to weeks. Every outreach tool that runs from a real account therefore chooses its own ceiling, and the honest ones print it. This post prints ours and explains the reasoning behind each figure, because the figures on this page are read from the same constants the sending worker enforces.

What LinkedIn restricts on

Three patterns account for most restrictions we have seen or read about:

• Volume that jumps. An account that sent five invitations a week and suddenly sends forty a day.
• A pending queue that never drains. Hundreds of invitations nobody accepted, sitting in the sent list for months. LinkedIn reads that as spam, whatever the note said.
• A flat rhythm. The same count at the same minute every day is a machine, and LinkedIn is good at spotting machines.

A safe schedule addresses all three: a cap that rises slowly, invites that are withdrawn when they go unanswered, and a daily count that varies.

The caps Slicegraph enforces

Each sender picks a safety preset. The preset fixes a range, and the worker samples a fresh value inside that range every day, so the count is never flat.

Preset	Invites per day	Invites per week	Messages per day
Conservative	up to 10	up to 50	up to 30
Balanced	up to 15	up to 75	up to 50
Faster	up to 20	up to 100	up to 70

A custom preset can go higher, but never past 30 invites a day or 150 a week; those are hard bounds in the code, not settings. The weekly cap matters more than the daily one: LinkedIn's own guidance talks about weekly invitation volume, and a sender that hits its daily cap five days running still stays under the week.

Caps are counted from the audit log. Every sent invite and message is an event, and the day's remaining budget is what is left after counting those events, so the accounting can never disagree with what actually went out.

Warmup

A newly connected account starts at 5 invites a day and adds 5 each weekday until it reaches the preset's cap. On Balanced that is two weeks to full volume. Skipping warmup is the single most common way to get a fresh account restricted, which is why there is no switch to skip it.

Pacing inside the day

Sending runs on weekdays between 09:00 and 17:00 in the sender's time zone, with the window's start and end shifted by up to half an hour each day. Inside the window, what remains of the day's budget is spread over what remains of the day: a sender on Balanced sends an invite roughly every half hour rather than fifteen in the first hour. The gap between two actions is never shorter than the preset's minimum.

Withdrawing what nobody answered

An invitation that has sat unanswered for 21 days is withdrawn automatically, a handful per pass, so the pending list never grows into the second pattern above. In a workflow, the withdraw step can also be explicit: after two weeks of silence, withdraw and reach the person by InMail instead. The outreach page shows that template.

When LinkedIn pushes back anyway

A rate limit freezes the sender for two hours. When LinkedIn asks the account to slow down, the freeze is 24 hours. Nothing retries into that wall, and the reason is written to the sender's record so you can see it in the console rather than discover it from a silent week.

What this costs

One plan, €29 per sender per month, every preset included. If you are comparing against a tool that allows more per day, the Dripify comparison puts the numbers side by side. If the audience should come from a company event rather than a search, start with the live permit feed for Amsterdam and read how signal-led outreach starts a sequence from it.