Skip to main content

Map application answers to Bullhorn fields

Decide which Bullhorn candidate or submission field each application answer fills when an applicant goes to Bullhorn.

Written by Jan Alexander Jedlinski

Who can do this: Owners and Admins, on the application form. The company-wide Updates to existing candidates setting in the Bullhorn integration: Owners only.

Before you start: Bullhorn is connected (see Connect Bullhorn to your Job Board), and the question you want to send is on the form (see Build an application form).

Each application form has a Bullhorn field mapping section. It decides which Bullhorn candidate or submission field each answer fills when the applicant is pushed to Bullhorn.

What goes to Bullhorn already

  • The standard fields come mapped: name, email, and the current employer, job title and address read from the resume.

  • The resume file is attached on every application. A new candidate also gets the resume text and the details read from the resume. For a candidate who's already in Bullhorn, the two settings under When the applicant already exists in Bullhorn decide (see below).

Map one of your questions

  1. Go to Settings > Jobs > Application forms and click the preset.

  2. Scroll down to Bullhorn field mapping.

  3. Click Add new field.

  4. Pick the question on the left and the Bullhorn field on the right. The left list also has the job's own fields, marked Job, and fields from the Bullhorn job order, marked Bullhorn job. For example, a job order field that holds the recruiter's name can fill the candidate's owner or the submission's sending user.

    Form Bullhorn field mapping: First name, Last name, Email, CV fields mapped to Bullhorn candidate fields, with update rules

    To fill the owner, Candidately looks up an active Bullhorn user with that full name or email. If there's no match, it uses the job owner (or else the job order's owner) and flags the applicant.

    A Bullhorn job order list, like categories or specialties, can fill the candidate's list of the same kind. Those rows offer Add to existing and Add only if empty.

  5. Click Save changes.

You see Application form saved. When an applicant is pushed to Bullhorn, their answer now fills the Bullhorn field you picked.

Note: Only fields of a similar type can be mapped. File uploads and the resume can't be mapped.

Which answer types fit which Bullhorn fields:

  • Short answer, dropdown, multiple choice: text fields.

  • Long answer: text fields with room for at least 500 characters.

  • Number: number or text fields.

  • Date: date or text fields.

  • Checkbox: yes/no or text fields.

Examples:

  • Notice period (short answer or dropdown): Bullhorn has no standard field for this, so ask your Bullhorn admin for a free text custom field on the candidate and map to it.

  • Desired salary (number): a salary field on the candidate.

  • Start date (date): the candidate's date available field.

Custom fields your Bullhorn admin has set up on candidates and submissions show up in the list too.

Choose what happens to existing data

Under each Bullhorn field you see what happens to data already in Bullhorn:

  • Written once, when the candidate is created

  • Always overwrites

  • Adds to existing

Email is the match key and is never overwritten. Where a field's caption has a menu, click it to pick a different option for that field under If the candidate already exists.

The line Existing candidates in Bullhorn on the form shows your company-wide setting, Updates to existing candidates. It's the most a push may change. A field on the form can be set to be more careful, never less. It can follow each field's setting (recommended), only fill empty fields, or never update.

To change it, click Change. It opens Settings > Integrations > Bullhorn, where the setting sits under Job Board settings in the Applicants part. Only Owners can change it.

The candidate owner works differently. The company-wide setting doesn't limit it, and its row offers only Never update or Always overwrite. With Always overwrite, the Owner overwrite rule in the Bullhorn settings decides which existing owners get replaced.

Bullhorn settings, Applicants: Auto push yes, Default submission status, Updates to existing candidates, Application source

When the applicant already exists in Bullhorn

Below the mapping, two settings decide what a new resume changes on an existing candidate:

  • Replace the Resume text with the new CV: Off by default. When it's on, every application writes the new resume's text to the candidate's Resume field. When it's off, that field is only filled when the candidate is created.

  • Update candidate details from the new CV: On by default. Fields filled from the resume, the job or the Bullhorn job order are written as each field's setting allows. When it's off, only answers the applicant typed are written, and the candidate's owner and categories stay as they are.

Troubleshooting

Some details are missing in Bullhorn

An answer only goes to Bullhorn if its question is mapped. Check the form's Bullhorn field mapping.

One answer was left out

If Bullhorn rejects an answer, for example a number that's too large, the applicant is still sent without it. The Bullhorn section on the applicant names the field that was left out.

Still stuck? Send us a message in the chat with the form name, the question and the Bullhorn field it should fill.

Related articles

Did this answer your question?