Capturing LinkedIn applications
Connect a LinkedIn job so its applicants flow into Kepler’s Inbound queue automatically.
If you advertise on LinkedIn, Kepler can capture those applicants automatically — no copy-paste from notification emails. LinkedIn sends "new application" emails to an inbox; Kepler reads the notification, creates an inbound application and processes it according to the job's intake policy. In review mode it waits in For Review in the job's Inbound queue; in automatic mode a clean applicant can join the pipeline immediately.
Before you start
- You need a connected email account (Settings → Communications Accounts) — specifically, the inbox that receives your LinkedIn application notifications. If none is connected, the dialog will point you there.
- You need a live job post on LinkedIn (Kepler doesn't create the LinkedIn post itself).
Connecting a LinkedIn job
- Open the job's Advertising tab and click + Connect to LinkedIn Job.
- Choose the receiving email account — the connected inbox where LinkedIn sends application notifications for this job.
- Pick the application stage accepted applicants should enter.
- Optionally paste the LinkedIn Project URL and LinkedIn Application URL for reference.
- Connect — the LinkedIn posting goes live in Kepler immediately (connecting means it's already live on LinkedIn).
How the capture works
- LinkedIn emails the receiving inbox about a new applicant.
- Kepler's email sync recognises the notification (sender + subject patterns) and matches it to your connected posting — when several LinkedIn postings share an inbox, the job title in the email disambiguates.
- The applicant's name, headline, location and profile URL are parsed out; a CV attached to the email comes along too.
- The applicant is scored against the job and appears in the Inbound tab marked with a LinkedIn source icon. Duplicate notifications are ignored.
Every LinkedIn applicant is parsed and scored. A confident junk submission moves to Screened out. In automatic intake mode, likely duplicates and processing failures stay in For Review for a recruiter, while clean applications are added to the configured pipeline stage.
If an application can't be matched
When a LinkedIn application email can't be matched to any connected posting (say, the job title changed on LinkedIn), Kepler sends you an Unmatched LinkedIn application notification instead of guessing — connect the right posting or handle the applicant manually.
LinkedIn occasionally changes its email format. Kepler's parser tolerates drift and degrades gracefully — if some fields can't be parsed, the applicant still arrives with whatever was readable, flagged for review.