Bullhorn Integration FAQ

The SourceBreaker integration with Bullhorn makes it easy to add and update candidate records directly from your search results. This article covers frequently asked questions about how the integration works, including duplicate detection, data transfer, and candidate status settings.

Frequently Asked Questions

If I parse a candidate and two duplicate records already exist in Bullhorn, which record will it parse to?

If two records already exist for the same candidate before you add them from SourceBreaker, SourceBreaker defaults to the oldest record first. If that same candidate is added again at a later date, they will be added to the most recent record.

How does SourceBreaker recognize duplicate candidates?

SourceBreaker identifies candidates based on email address and phone number, not name. This check runs automatically in the background: if a match is found, the most recent CV is added to the existing record.

Additionally, when you view a candidate who is already in your database, SourceBreaker's Auto-Link feature will automatically link that candidate to their existing Bullhorn record and display the View in Bullhorn button for easy access going forward.

Why am I seeing more results when searching directly in Bullhorn than when searching through SourceBreaker?

This can happen for a number of reasons. We recommend replicating the search in both places to identify any specific discrepancies. If you continue to see differences, contact support with details of both searches so we can investigate.

I added a candidate from a job board and then ran the same search against Bullhorn, but the candidate isn't showing up. Why?

This is often related to location data. The location SourceBreaker parses from a job board profile may differ from the location stored against that candidate in Bullhorn, which can affect whether they appear in a location-based search. Try replicating the search to confirm, and check whether location filters may be a factor.

Why don't candidates from job board results show as "View in Bullhorn" even when they're already in our database?

To match a job board candidate to an existing Bullhorn record, SourceBreaker needs access to their email address and phone number. Retrieving this information from job boards requires using a credit for each candidate, which makes automatic matching from search results lists impractical.

However, when you open an individual candidate's profile, Auto-Link will check whether they already exist in your database and, if so, link the records and display the View in Bullhorn button automatically. Over time, as your team reviews candidates through SourceBreaker, more records will be linked and discoverable this way.

What data transfers from a job board candidate profile into Bullhorn?

SourceBreaker pulls through the candidate's current job title, current employment, current company, and skills (where entered). Desired job title is not parsed, as this field often contains unreliable data.

Can we add a note to show that a candidate was added or updated through SourceBreaker?

If a candidate is added or updated through SourceBreaker, this is automatically reflected in the Source field in Bullhorn. You can also add a manual note to the record if you'd like to record additional context.

Can we set candidate statuses to "Active" instead of "Registered" when candidates are added?

Yes. You can configure the default candidate status under Team Settings > User Profile > Settings. The available statuses are linked to your Bullhorn configuration and will not override any pre-existing statuses on existing records.

Are there additional filter options available when searching Bullhorn through SourceBreaker?

For more granular filtering, use the Open in Bullhorn option to take your SourceBreaker search results into Bullhorn directly, where you can apply your full range of Bullhorn filters.

Can I sort Bullhorn results by last updated?

Sorting by last updated is not currently available.