The short answer
LinkedIn limits most accounts to about 100 invitations a week, and hitting LinkedIn's limit blocks invitations for about a week. Divide that across a working week and you get a daily number in the teens. The plan here sends at most 20 a day and 100 in any 7 days, and you can set a run lower than that, never higher.
If that sounds small next to the numbers some tools advertise, it is. It is also the number that lets an account keep going month after month.
Why there is a daily cap and a weekly one
The weekly cap is the one that matches LinkedIn. The daily cap is there so you don't spend the whole week's allowance on Monday and then have nothing to send until the window moves on. Spreading requests across days also gives people time to accept before the next batch, so Message Sender has someone to message.
| Limit | The plan |
|---|---|
| Connection requests a day | 20 |
| Connection requests in any 7 days | 100 |
| Messages a day | 30 |
| Likes a day | 50 |
A new or quiet account
An account that has never sent many invitations, or has been idle for months, should not start at the cap. Set the Daily limit on Auto Connect to a fraction of it, choose Slow pace, keep the lead list short and well matched, and raise the limit a little each week while nothing odd happens. If LinkedIn shows a security check, drop back and wait.
There is no magic starting number. Lower is safer than higher, and a smaller list of the right people beats a bigger list of roughly the right people.
The gap between requests matters too
Twenty requests in two minutes and twenty requests across a quarter of an hour are not the same thing to LinkedIn. Auto Connect waits a random gap after each request: Normal is 30 to 60 seconds, Slow is 90 to 180 seconds, Fast is 5 to 15 seconds. Normal suits most accounts, Slow is the careful choice, Fast is for a handful of requests at a time.
Requests are not the only cap
Messages and likes have caps of their own: 30 messages and 50 likes a day. They are separate because they are different things: a message goes to someone who has already accepted you, and a like is the lightest touch there is. Sequences and Message Sender share the message cap; Auto Liker has the likes to itself.
A week that uses all of them looks like this:
| Day | Requests | Messages | Likes |
|---|---|---|---|
| Monday to Friday | up to 20 | up to 30 | up to 50 |
| Saturday and Sunday | none from the tool | a few, by hand | up to 50 |
Five working days at the request cap is 100, which is where the 7-day cap sits. Taking the weekend off from requests is not a rule; it is just how the arithmetic falls, and it leaves room for the few you send by hand.
If you also send requests by hand
LinkedIn counts every invitation from your account, whoever clicked. Our counters only count what we sent. If you send a few by hand each day, set the run's daily limit lower by about that many, so the two together stay under the weekly figure.
What it looks like in practice
A list of a hundred people takes a working week at the daily cap. Each run stops when it reaches the cap, and the daily Telegram report shows the day's count next to the cap, so you can see at a glance how the week is going. Counters reset at midnight India time; the 7-day cap simply counts the last 7 days.
If a run stops before the cap because LinkedIn refused an invite, don't restart it that day. Wait until the next day at least, and take it as a sign to slow down.