LinkedIn new invitation limit: what changed and how to work around it
LinkedIn is capping connection invitations at 100 per week. Some accounts are already hit by this, though I haven’t found any official announcement explaining whether it’s a permanent change or just a test rolling out gradually.
What’s stranger is that some accounts get blocked after just 70 invitations, not 100. Nobody seems to know the exact rules. People who rely on invitations for outreach are understandably frustrated.
Can you still send invitations after hitting the limit?
Yes. But you need the email address of the person you want to connect with.
If you have their email, here’s what you do:
- Log into LinkedIn and go to https://www.linkedin.com/mynetwork/import-contacts/iwe/
- Enter the email addresses of everyone you want to invite, separated by commas
- Click continue. Done.
You can check all sent invitations at https://www.linkedin.com/mynetwork/invitation-manager/sent/
I use the free version of Snov.io. You plug in someone’s name and their employer’s domain, and it tries to figure out the email address. Simple enough.
It doesn’t always work, but the results surprised me. Out of 59 addresses I looked up, 21 came back confirmed and another 22 were “unverified” — meaning Snov.io found a probable address but couldn’t guarantee it was correct. Not bad for a free tool.
What about GDPR?
This is the part where things get murky. Tools like Snov.io claim they handle data in a regulation-compliant way. I couldn’t find a clear explanation on Snov.io’s site, but Lusha has a dedicated page: https://www.lusha.com/legal/gdpr/ — their argument boils down to this:
The biggest myth about the GDPR is that consent is the ONLY way to lawfully process personal information concerning EU data subjects. While consent is one basis for lawful processing, it is not the only one.
Lusha’s lawful basis for processing is its legitimate interest in providing its services to its users, for more information please contact our Privacy Team.
Whether “legitimate interest” actually holds up under scrutiny is a whole separate conversation. I’ll write about the GDPR side of this another time.
DISCOVER ELEMENT!
Maciej Michalewski
CEO @ Element. Recruitment Automation Software
Recent posts:
The autonomous company: how Replit does it with AI agents, and how to do it yourself
Replit built an autonomous company: a fleet of AI agents where people choose the goals and automations handle the steps. I break down the pattern and how to run it yourself.
How to reject a candidate without ghosting: Glen Cathey’s playbook
Ghosting applicants isn’t a volume problem, it’s a priority problem. I walk through Glen Cathey’s rejection playbook: 6 rules, 7 templates and ATS setup.
Poland’s job market turns positive: 259,000 postings, all ten cities growing
Poland posted 259,000 job ads in June 2026, the first positive year-over-year reading in more than a year. The Grant Thornton and Element report reads it as a cautious but real turnaround.
What’s new in Element: a month of concrete improvements for recruiters
A roundup of what’s new in Element this month: saved filters, GDPR and consent tracking, candidate SMS, a new public API, and stronger data security.
Career in the age of AI agents: what really counts, per Phil Chen
Phil Chen (Helm AI, Scale, OpenAI, DeepMind) argues that in the age of AI agents, finding problems, the last mile and reputation matter more than solving tasks. A summary plus my HR take.
AI isn’t taking jobs. Companies that invest in it hire more
A Ramp study of 21,599 US firms finds that companies investing seriously in AI grow headcount 10.2% in two years, including entry-level roles. The data pushes back on AI job-loss panic.
