Auto-Adding Candidates with LinkedIn RSC

There are two LinkedIn RSC features that may cause Candidate records to be automatically added to your database:

For information on the duplicate checking logic for candidate creation please see the Duplicate Checking Logic section.

InMail Responses

When replying to an InMail, candidates have the option to share their phone number and/or email address with you. When you receive an inbound InMail from a candidate who has agreed to share this information and is not already synced with a record in Bullhorn, Bullhorn checks for a match in the following order: LinkedIn URN first, then first and last name and/or email address.

The initial outbound inMail to a candidate record doesn't create a Candidate record.

  • If the first and last name and/or email address of the LinkedIn candidate does not match a candidate in Bullhorn, then a new Candidate record will be created and the InMail will be added as a Note.

    • When a new Candidate record is created in Bullhorn, the following stub profile information from LinkedIn will be populated on their record:

      • First Name

      • Last Name

      • Email Address

      • Phone Number

      • Current Company

      • Status of New Lead

      • Job Title

  • If the first and last name and/or email address of the LinkedIn candidate matches a single candidate in Bullhorn, the InMail is added as a Note on that existing Candidate record.

  • If the first and last name and/or email address of the LinkedIn candidate matches multiple candidates in Bullhorn, the InMail is added as a Note on the Candidate record that was updated most recently.

A stub profile is only created from an InMail Response if the candidate opts into sharing their contact information.

If you do not want any new candidate records created when you receive InMail, you can disable this in your Recruiter settings within LinkedIn.

1-Click Export

This feature allows you to submit candidates to Bullhorn jobs directly from their LinkedIn profile. If the candidate isn’t already synced with a record in Bullhorn, Bullhorn checks for a match in the following order: LinkedIn URN first, then first and last name.

This feature will not be available on a candidate’s LinkedIn profile if they've configured their settings to prevent LinkedIn from sharing their data with 3rd parties.

  • If the first and last name of the LinkedIn candidate does not match a candidate in Bullhorn, then a new Candidate record will be created and the Submission will be attached to the record.
    • When a new Candidate record is created in Bullhorn, the following stub profile information from LinkedIn will be populated on their record:
      • First Name
      • Last Name
      • Current Company
      • Status of New Lead
  • If the first and last name of the LinkedIn candidate matches a single candidate in Bullhorn, the Submission is attached to that existing Candidate record.
  • If the first and last name of the LinkedIn candidate matches multiple candidates in Bullhorn, the Submission is attached to the Candidate record that was updated most recently.

Duplicate Checking Logic

This section walks through the duplicate checking logic for candidate creation using 1-Click Export, InMail Responses, and Notes added from InMails and LinkedIn Notes.

These flowcharts refer to three concepts:

  • InMail- The name for an email sent using LinkedIn.
  • URN- A URN (Uniform Resource Name) is a unique identifier assigned by LinkedIn, stored in Bullhorn in the BH_UserLinkedInUrn table. Bullhorn checks for a URN match first when determining whether to create a new Candidate record or link to an existing one. If a URN match is found, Bullhorn links to that record regardless of name. If a URN match is found, you can also view the candidate's LinkedIn profile from within Bullhorn.
  • Stub Profile- A Candidate record created via the integration that contains limited information depending on how it was created. A stub profile created via 1-Click Export will contain First Name, Last Name, and Current Company. A stub profile created via an InMail Response will contain First Name, Last Name, Current Company, Email Address, Phone Number, and Job Title.

1-Click Export

When a 1-Click Export is initiated, Bullhorn checks for a matching Candidate record in the following order:

  1. URN match: If a URN match is found in Bullhorn, the submission record is added to the most recently updated matched candidate.

  2. First and last name match (checked only if no URN match is found):

    • If no name match is found: a stub profile and submission record are created for the candidate.

    • If a single name match is found: the submission record is added to that candidate.

    • If multiple name matches are found: the submission record is added to the most recently updated matched candidate.

Flowchart showing 1-Click Export duplicate check logic. Checks URN match first: if found, adds submission to most recently updated matched candidate. If no URN match, checks first/last name: no match creates stub profile and submission record; single match adds submission to that candidate; multiple matches add submission to most recently updated matched candidate.

InMail Responses

When an InMail is sent or received, Bullhorn checks for a matching Candidate record in the following order:

  1. URN match: If a URN match is found in Bullhorn:

    • If a single URN match is found: the note is added to that candidate.

    • If multiple URN matches are found and the first match has been manually matched via the LinkedIn profile widget: the note is added to the manually matched candidate.

    • If multiple URN matches are found and no manual match exists: the note is added to the most recently updated matched candidate.

  2. First and last name match (checked only if no URN match is found):

    • If a single name match is found: the note is added to that candidate.

    • If multiple name matches are found and the first match has been manually matched via the LinkedIn profile widget: the note is added to the manually matched candidate.

    • If multiple name matches are found and no manual match exists: the note is added to the most recently updated matched candidate.

Flowchart showing InMail duplicate check logic. Checks URN match first: if single URN match, adds note to matched candidate; if multiple URN matches, checks for manual profile widget match before falling back to most recently updated candidate. If no URN match, applies same logic using first/last name match.

Notes Added From InMails and LinkedIn Notes

When a LinkedIn Note is added, Bullhorn applies the same matching logic as InMail Responses above — URN match first, then first and last name match. The outcome in each path is a note added to the matched candidate rather than a submission record.

Flowchart showing LinkedIn Notes duplicate check logic. Identical logic to InMail Responses: checks URN match first, then first/last name match. Each path results in a note being added to the matched candidate, or to the most recently updated matched candidate if multiple matches exist.