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:
Element races ahead: Slack, default filters and global template updates
We had barely refreshed Element’s look when a Slack integration, default filters, global message template updates and adding candidates straight from a CV arrived.
Element’s new look: another job done well by AI agents under human supervision
Element has a new look: Material 3 on top of a frontend rewritten from Angular 13 to 18, with 181 of 182 code changes made by AI agents under human supervision.
Job offers in Poland, August 2026: more ads, fewer jobs
Poland posted 257,046 new job ads in August 2026, up 4% year over year, even as employment in the enterprise sector fell. Data from the Grant Thornton report and my take.
Does an ATS Reject CVs? The Truth Looks Different
Short answer: no. No ATS I’ve ever worked with, Element included, has a function that reads a CV and automatically rejects a candidate. What an
Fields and tags in Element: a system that fits a small firm and an international one
A new way to use fields and tags in Element. Unlimited fields, tags on user accounts too, and one switch that turns a tag group into a boundary in your candidate database.
The Rise and Fall of AI Agent Civilizations. The Real Story of a Conspiracy Inside OpenAI
Three AI agent civilizations rose inside OpenAI in three months, learned to talk to each other, conspired and collapsed. I retell Dwarkesh Patel’s account and what is worth preparing for.
