Syncing Bullhorn Fields with LinkedIn RSC

This article lists the Bullhorn fields that sync with LinkedIn RSC, including which fields are required for a record to sync. For records that aren't syncing, see Records Not Syncing with LinkedIn RSC.

• Candidate Fields
• Submission Fields
• Job Fields

If a field is not required for a record to sync with LinkedIn, Bullhorn will always send it to LinkedIn if the field is populated. You cannot choose which fields are or are not sent to LinkedIn as part of this integration.

Candidate Fields

Candidate data is synced to LinkedIn to power the following features:

• The LinkedIn Profile Widget in Bullhorn
• Past Applicant Spotlight
• In-Bullhorn Indicator
• 1-Click Export
• InMail and Note tracking

Bullhorn Field	Description of Field	Required for Record to Sync with LinkedIn?
createdAt	Date record was created in Bullhorn.	Yes
lastModifiedAt	Date record was last updated in Bullhorn.	Yes
(not an actual field, see Note)	Link to the candidate in Bullhorn.	Yes. We provide a link to the Candidate record in Bullhorn so users can access the link while on a LinkedIn profile.
firstName	Candidate's first name.	Yes
lastName	Candidate's last name.	Yes
email, email2	List of Candidate's email addresses.	Yes
Candidate ID	Candidate's unique identifier in Bullhorn.	Yes
fullAddress	A list of the Candidate's addresses.	No
companyName	Name of the Candidate's current employer.	No
occupation	Candidate's current job title.	No
phone, workPhone, mobile, phone2, phone3	A list of the Candidate's phone numbers.	No
namePrefix	The prefix of the Candidate's name.	No
nameSuffix	The suffix of the Candidate's name.	No

Submission Fields

Submission data is synced to LinkedIn to power the following features:

• In-Bullhorn Indicator
• Past Applicant Spotlight

Bullhorn Field	Description of Field	Required for Record to Sync with LinkedIn?
createdAt	Date record was created in Bullhorn.	Yes
lastModifiedAt	Date record was last updated in Bullhorn.	Yes
Job ID	The Job's unique identifier in Bullhorn.	Yes
title	Bullhorn Job name.	Yes
email	Candidate's email address.	Yes
firstName	Candidate's first name.	Yes
lastName	Candidate's last name.	Yes
source	Source of the Submission.	Yes
status	Stage of the Submission (e.g. Phone Screen).	Yes
Submission ID	The Submission's unique identifier in Bullhorn.	Yes

Job Fields

Job data is synced to LinkedIn to power the following feature:

• 1-Click Export

Bullhorn Field	Description of Field	Required for Record to Sync with LinkedIn?
Job ID	The Job's unique identifier in Bullhorn.	Yes
title	Bullhorn Job name.	Yes
description	Custom description of the Job (minimum 100 characters, maximum 25,000 characters).	Yes
isOpen	Current state of the Job (Open or Closed).	Yes
createdAt	Date Job was created in Bullhorn.	Yes
City/State OR City/Country	Geographic location of the Job.	Yes
Country Code	Country Code of the Job.	Yes
Zip Code	Postal code of the Job.	Yes
skills	Description of desired skills and experiences.	No
categories	Categories of the Job in Bullhorn. Bullhorn will send up to ten to LinkedIn.	No

If a Job Isn't Syncing, Check the Following

• The 100 character minimum/25,000 character maximum for the Description field is referencing the Internal Job Description field (this is different than the publicDescription field). This character count includes all HTML formatting that can be seen by clicking "Source" in the field's toolbar.

• The Job must not be Deleted. If a Job is deleted, it will not sync.

• The Job must be Open. If a job is Closed, it will not sync.

• The Job does not have to be in a Published state, because Published is not a field that is synced to LinkedIn.

Records Not Syncing with LinkedIn RSC

If a record isn't syncing with LinkedIn RSC, use the following sections to identify the cause.

How to Identify an Unsynced Candidate Record

A Candidate record is not synced with LinkedIn if the LinkedIn RSC tab on that record displays the following message: "Candidate Not Matched. No candidate was found using the candidate id."

Check Required Field Data

LinkedIn requires minimum data on each record before it can sync. For Candidate, Submission, and Job records, verify that all required fields listed in the tables above are populated.

Check Candidate Consent

Candidate records in Bullhorn must have the Consent tab on their record populated with certain information in order to sync. If a Candidate isn’t syncing, navigate to the Consent tab on their record to see if it contains the necessary information.

Consent is handled in one of two ways depending on how Bullhorn Support enables your integration:

Automatic Consent Handling

This setting requires no action on your part as consent is assumed. Records sync with LinkedIn when the Consent tab contains a LinkedIn RSC entry with the Purpose and Legal Basis values configured during your RSC setup.

If you provided Bullhorn Support with a different Consent Purpose and/or Legal Basis during your setup, then records will need to contain those values instead.

Manual Consent Handling

Manual consent means that Candidate records default to opted out until consent is obtained from the candidate. They will not sync initially. Once consent is obtained the Consent tab will populate with the Consent Purpose and Legal Basis you provided to Bullhorn Support during your initial setup and the record will sync.

Check LinkedIn Profile Visibility

If a candidate has set their LinkedIn profile to private, the LinkedIn RSC integration cannot sync that record. The integration uses the candidate’s public LinkedIn profile. A candidate with their public profile visibility disabled will not be eligible to sync.

If the Record Still Isn’t Syncing

Since LinkedIn ultimately controls the information that displays on the LinkedIn Profile Widget, they are the authority. Reach out to LinkedIn's Support Team for further troubleshooting.