How many LinkedIn connection requests per week is safe?
About 100 a week, 15–20 a day on a warmed account. What LinkedIn says, why acceptance rate matters more, and how to ramp a new account.
Plan for about 100 connection requests per week, and spread them across working days: 15 to 20 a day on an account that has been in normal use for a while, 5 to 10 a day on a new or long-dormant one. LinkedIn does not publish an exact number, but 100 per rolling seven days is where most people who send invitations for a living say the cap sits in 2026. Paying for Premium or Sales Navigator does not reliably raise it.
The more useful question is not "how many can I send" but "how many can I send without hurting the account". Those are different numbers, and the second one depends mostly on how people respond to you.
What LinkedIn actually says
LinkedIn's own help pages are vague about the number and specific about the behaviour. Here is what is on the record:
- On types of restrictions, LinkedIn lists three reasons an account gets restricted from sending invitations: you sent many invitations in a short time; many of your invitations were ignored, left pending or marked as spam; or you sent an excessive number and they suspect an automation tool.
- On reaching the limit, the restriction "typically lasts one week", support cannot shorten it, and withdrawing pending invitations does not remove it.
- On withdrawing an invitation, you cannot re-invite the same person for up to three weeks.
- On personalised invitations, a note is up to 200 characters, and a free account can add a note to only three requests per month.
Notice what is missing: no number. The weekly figure everyone quotes comes from observation, not from a policy page. That matters, because it means the limit is not a fixed quota you are entitled to. It moves with your account's standing.
The numbers people work with in 2026
- invitations per rolling 7 days, the commonly observed cap
- ~100
- a day on a warmed, normally used account
- 15–20
- a day on a new or dormant account
- 5–10
- characters max in a connection note
- 200
The weekly window is rolling, not reset on Monday. If you send 60 on Tuesday, those 60 count against you until the following Tuesday. Bunching the whole week into one morning is the fastest way to trip the "many invitations in a short time" rule, even if the weekly total looks fine.
Vendor guides also mention two thresholds that LinkedIn does not confirm but that match what most outbound teams see. Accounts with an acceptance rate under roughly 20% get throttled hardest, and sitting on 500 or more unanswered requests drags your standing down (Salesforge). Treat both as rules of thumb, not law.
Acceptance rate is the real limit
Re-read LinkedIn's second reason: invitations that are "ignored, left pending, or marked as spam". Every request you send to someone who has no reason to accept it costs you twice. It uses up part of the week, and it lowers the ratio LinkedIn watches.
So the practical ceiling is set by targeting, not by the counter. An account sending 80 requests a week to people who mostly accept will run for years. An account sending 40 a week to a scraped list where nobody knows who you are will hit a restriction sooner.
What moves acceptance rate in the right direction:
- A profile that explains itself. The person decides in two seconds from your photo, headline and current role. "Founder at Acme, we help logistics teams cut empty miles" beats "Helping businesses grow".
- Second-degree connections and shared groups first. Mutual connections are the cheapest trust signal on the platform.
- People who already touched you. Profile viewers, people who commented on your posts or a post you commented on, event attendees.
- A reason in the note, or no note at all. A sales pitch inside the invitation reads as spam and gets the "I don't know this person" treatment. A plain request from a relevant profile often does better than a weak note.
Two examples of notes that fit in 200 characters and don't sell anything:
Saw your comment on Marta's post about carrier onboarding. We run into the same problem with mid-size fleets. Would be glad to connect.
We're both in the Ops Leaders group and I liked your thread on WMS migrations. Connecting to follow your posts.
Clean up pending invitations
Old pending requests count against you even though nothing is happening with them. Once a request has sat for two to three weeks without an answer, it is unlikely to be accepted.
A weekly LinkedIn invitation routine
- Monday: check last weekCount sent vs accepted. Under 20% accepted means fix the list before sending more.
- Monday: withdraw stale requestsWithdraw anything pending longer than three weeks. You cannot re-invite them for up to three weeks, so don't.
- Tuesday to Friday: send in small batches15–20 a day at irregular times, from a list you built by hand or filtered tightly.
- Every day: message new connectionsReply within a day to people who accept. That's where conversations start, not in the invite.
- On a warning: stop for the weekIf LinkedIn asks for verification or shows a limit, send nothing until the rolling week passes.
One caveat: withdrawing does not give you invitations back. It protects the ratio, it does not refill the week.
New or quiet accounts need a ramp
An account that has been idle for months and suddenly sends 100 invitations looks exactly like an account someone just bought. The usual approach is to start low and raise the daily number slowly while the account also does normal things: accepts incoming requests, views profiles, replies to messages, posts or comments now and then.
A ramp that most outbound teams would accept as safe for a new account:
Invitations per working day, new account
The first few days are for setting up the profile and normal browsing, with no outreach at all. If the account hits a warning at any step, hold the number where it was for another week instead of pushing through. Don't send on weekends at first; a steady seven-day pattern is one of the things that makes activity look scripted.
Does Sales Navigator or Premium raise the limit?
Not in any way you can count on. The 100-per-week figure is reported across Free, Premium and Sales Navigator accounts. Some long-standing Sales Navigator accounts with strong acceptance rates report more, but that is the account's history at work, not the subscription. What paid plans do give you is better filtering (so your acceptance rate goes up) and InMail credits, which reach people without a connection request at all.
Automation tools and the account risk
LinkedIn names suspected automation as a reason for restriction, and its User Agreement prohibits bots and unauthorized automated methods to access the service, add contacts or send messages. Every tool that sends invitations for you is operating in that grey zone, and no tool can promise an account will never be restricted.
If you use one anyway, the safe settings are the same as the manual ones above: daily numbers well under the weekly cap, random gaps between actions, working hours in the account owner's time zone, a slow ramp for new accounts, and a stop the moment LinkedIn shows a warning. A tool that offers "200 invitations a week, guaranteed safe" is selling you the restriction.
This is also how Nitrino handles LinkedIn in its outreach campaigns: a new account starts at five invitations a day and climbs slowly, and the ramp freezes when the account runs into a limit instead of trying to push through it. Replies from people who accept are handled in the same inbox as Telegram, WhatsApp and email, so the conversation doesn't stall after the connection is made.
The short answer
- About 100 invitations per rolling week, 15–20 per working day on a healthy account.
- 5–10 per day on a new or dormant one, raised over three to four weeks.
- Keep acceptance above 20% and pending requests well under 500.
- Withdraw anything pending longer than three weeks.
- On a warning, stop for seven days. Support can't lift it faster.
The counter is not the thing to optimise. Send fewer requests to people with a reason to say yes, and the limit stops being the problem.