How to Add LinkedIn Candidates to Greenhouse Automatically

A recruiter opens a Boolean search and gets back 180 promising engineers. Twelve carry an open-to-work badge; the rest are the real pipeline. Then comes the tax: opening each profile, switching to Greenhouse, creating the candidate, and pasting the same four fields, 180 times. At 2 to 3 minutes apiece, that shortlist is roughly 6 to 9 hours of pure data entry before a single message goes out.

Quick answer: the sanctioned way to add LinkedIn candidates to Greenhouse is LinkedIn Recruiter System Connect, which exports a profile to a chosen job in one click and keeps consent inside the platform. Below are the ways to do it, first by hand, then with a Simular AI computer agent that drives both real interfaces, then with the native RSC and Greenhouse sourcing tools.

‍

Manual vs. Simular vs. native tools, at a glance

‍

Which method should you use?

• A few candidates for one job: add them by hand. The setup is not worth it.
• You already run LinkedIn Recruiter: turn on RSC and use the one-click Export to ATS.
• Large lists spanning several jobs, or no RSC seat: a Simular AI computer agent files each profile on the right job for you.

‍

Method 1: Add each candidate by hand across both tabs

Read the profile in LinkedIn, then recreate it in Greenhouse. Fully compliant, but it is the slow lane.

1. Open the LinkedIn profile and note the name, current title, company, and location.
2. In Greenhouse, open the target job, click Add Candidate, and fill the fields.
3. Paste the LinkedIn profile URL into a link or custom field so the source is traceable.
4. Set the source to LinkedIn and add a short sourcing note, then save.

Pros: no license beyond Greenhouse, full control over every field. Cons: the tab-to-tab switch runs 2 to 3 minutes per candidate, and hand-typing invites typos in names and titles that later break search.

‍

Method 2: Hand it to a Simular AI computer agent (the automated path we recommend)

Instead of retyping or wiring up an integration, you show a Simular agent your sourcing routine once, and it repeats it across the whole list.

1. Demonstrate one cycle: open a LinkedIn profile, read the name, title, company, and experience, switch to Greenhouse, open the job, create the candidate, and attach the profile URL.
2. Name the target job and source: tell the agent which posting to file each candidate on and to set the source to LinkedIn.
3. Let it run on its cloud VM: the agent works the real screens at a human pace and logs every profile it files, so nothing is silently dropped.
4. Stay in the loop: it pauses on the missing email field and any duplicate, and asks you before creating a record it is unsure about.

Because the agent operates the actual LinkedIn and Greenhouse interfaces, it needs no Greenhouse API key, no Zapier wiring, and no background scraper for LinkedIn to fingerprint. It uses the same sanctioned export and forms a recruiter would, so consent and terms stay intact while the busywork disappears. That also lets it handle steps the native integration skips, like copying a specific note or reconciling a duplicate. See the Sai page for how the agent is guardrailed, and the team behind it.

At about 2.5 minutes to retype one profile into a job, a 150-candidate sourcing sprint is roughly 6 hours of data entry. An agent that files them unattended returns that half-day to actual candidate conversations. Derived estimate.

Pros: large-list volume on the sanctioned rails, no integration to maintain, human-in-the-loop. Cons: a subscription, plus 20 minutes up front to teach it your workflow.

‍

Method 3: LinkedIn Recruiter System Connect and Greenhouse sourcing tools

If your team runs LinkedIn Recruiter, the native rails are the cleanest one-off path. RSC adds an export button straight into Recruiter.

1. On a candidate in LinkedIn Recruiter, click the ellipsis icon and choose Export to ATS.
2. Select your organization, then search for the Greenhouse job by name or ID and click Export.
3. Find the candidate in Greenhouse under the job, sourced as LinkedIn (Prospecting) with a 1-click export tag.
4. Add the email manually, since RSC does not carry it across, and the profile stays partial until you do.

For bulk sourcing, the Greenhouse Recruiting Chrome extension prefills a prospect from a LinkedIn profile and checks for duplicates by name, email, phone, and URL. Both routes are documented on LinkedIn's Greenhouse integration page.

Pros: official, consent-preserving, one click per profile. Cons: RSC needs a full Recruiter seat, not Recruiter Lite; the Chrome extension requires a Sourcing Automation seat on Plus or Pro and caps PDF saves at 200 profiles a month; and neither imports the email address for you.

‍

Why the sanctioned path matters, and where teams slip

RSC and the Greenhouse extension exist because LinkedIn treats profile data as consented and platform-bound. A background scraper strips that consent, and LinkedIn can detect the injected code and inhuman request timing that scraping tools leave behind. That is why the compliant route is not just safer for your recruiter seat; it protects the candidate relationship too.

Pro tactics that keep sourcing clean:

• File the URL every time. A pasted profile link is the reliable dedupe key later, more so than a name that two people may share.
• Fix the email gap on intake. Because RSC omits the address, build the missing-email prompt into your process so records do not sit half-complete.
• Segment by job before you source. Deciding the target posting up front stops candidates from piling into one generic pool.
• Watch for duplicates across pools. The extension checks name, email, phone, and URL; keep those fields consistent so the check actually catches repeats.

The mistakes that cost teams are consistent: retyping profiles until typos poison search, bulk-scraping to save time and risking the seat, and leaving RSC candidates without an email so outreach stalls. Recruiting communities repeat the same complaint, that the copy-between-tabs step is where a good sourcing day quietly turns into a data-entry day. The takeaway worth pinning up: use the sanctioned export, then automate the clicking, not the consent.

‍

Key takeaways

• The sanctioned way in is LinkedIn Recruiter System Connect: click the ellipsis, Export to ATS, pick the job.
• RSC needs a full Recruiter seat and does not carry the candidate's email, so add it on intake.
• For a few candidates, add them by hand; for large lists across jobs, a Simular agent files them on autopilot.
• Automate the clicking, not the consent: the agent uses the real sanctioned screens, no scraper.

The winning pattern: keep candidates on the consent-preserving rails, then let a Sai agent read each LinkedIn profile and file it on the right Greenhouse job while you focus on the conversations. Pair it with a repeatable way to build a targeted LinkedIn prospect list, a step to extract LinkedIn profile data, and, when you need contact details, a compliant way to find emails from LinkedIn. Sourcing into Lever instead follows the same shape.