How to Fix the "Email Needed to Add This Person" Error in LinkedIn Connection Requests

Sophie
Sophie This badge shows you’re hearing straight from the source! Team members are here to share insider tips, answer questions, and guide you through PhantomBuster with expert knowledge. They’re dedicated to helping you succeed and making sure your automation journey feels easy and exciting. PhantomBuster Official
  • Updated

If your LinkedIn Phantom returns an "Email needed to add this person" error, it means the target person's LinkedIn settings only allow connection requests from people who already know their email address. This is a LinkedIn privacy control that can't be bypassed, not by Phantoms, and not even by manual requests without providing the email. The Phantom will skip these profiles and continue processing the rest of your list.

If your connection requests are failing for other reasons, see How to Fix LinkedIn Connection Requests Not Being Sent. If you're running out of invite credits, see How to Fix the "No remaining invite credits" Error.

Why you're seeing this

This error appears when the person's LinkedIn settings only allow connection requests from people who already know their email address.

It's a privacy control managed by LinkedIn, Phantoms and even manual requests can't bypass it.

PhantomBuster log showing the Email needed to add this person error message from LinkedIn

How to fix it

Filter these profiles out of your input list

If you're hitting this error frequently, pre-screen your input. Unfortunately there's no way to detect this setting in bulk before launching, but you can clean your list after the first run by removing any profiles that returned this error and relaunching with the filtered list.

Send a manual invitation with their email

If you know the person's email address, go to their LinkedIn profile, click Connect, and enter their email when prompted. This is the only way to connect with someone who has this setting enabled.

Reach out through other channels

If you don't have their email, try reaching out via email (if you can find it through other means), through a mutual connection who can introduce you, or on another platform where they're active.

Use InMail to message without connecting

If you have a Sales Navigator account, you can bypass the connection step entirely and message the person directly using InMail through the Sales Navigator Message Sender. This doesn't solve the connection request, but it gets your message through.

Frequently asked questions

Can I provide the email address in the Phantom input?

No. The LinkedIn Auto Connect and Outreach Phantoms don't support providing email addresses as part of the connection request. If someone requires an email to connect, you'll need to send that request manually.

Will the Phantom skip these profiles or stop entirely?

It skips them. The Phantom logs the error for that profile and continues processing the rest of your input list.

How do I know which profiles require an email before launching?

You can't. This setting isn't visible on the profile page or detectable through scraping. You'll only find out when the connection request fails.

Is this the same as being out of network?

No. "Out of network" means the profile isn't visible to you at all. "Email needed" means you can see the profile, but the person has restricted who can send them connection requests.

Does Sales Navigator bypass this restriction?

Not for connection requests. But Sales Navigator lets you message people directly using InMail credits, which bypasses the need to connect entirely.

How common is this setting among LinkedIn users?

Relatively uncommon. Most users keep the default setting that allows anyone to send connection requests. You're more likely to encounter it on senior executives or people who receive a high volume of requests.

If the error keeps showing up

If this error is disrupting your outreach at scale, get in touch with our Customer Care Team for advice on adjusting your setup. Include:

  • The Phantom name and link
  • A screenshot of the error in the output
  • The approximate number of profiles affected
  • Example profile URLs that triggered the error

Was this article helpful?

1 out of 2 found this helpful