Configuring 3rd Party Auto-Match

Users can configure their settings to use a third-party algorithm, instead of Bullhorn Automation Semantic Match Bullhorn Automation leverages AI to match up jobs and candidates. It evaluates the similarity between job postings and candidates by analyzing factors such as Title, Location, Specialities, etc., if their needs are better met when a job hits the auto match step.

Prerequisites

Webhooks Enabled
API Tab Enabled
MaxCandidates, MinScore, MaxDistance, and CandidateIds will be required either in the Data or Url sections

This feature is part of the Automation Enterprise package. If you are unsure which package you have, reach out to your Account Manager.

Steps to Configure

Navigate to Settings > API > Match Candidate Webhook
Select Edit.

The Merge Tags Merge tags enable the use of Bullhorn ATS or Bullhorn Automation imported data to populate content. They are utilized in emails, notifications, and text messages where applicable. for MaxCandidates, MinScore, MaxDistance, and CandidateIds will be required either in the Data or URL sections. The third party algorithm will use these settings to filter candidates properly.

MinScore: The minimum score calculated by the algorithm that a candidate must meet to be included. Value will be between 0-1.
MaxCandidateCount: The maximum number of candidates to return.
MaxDistanceMiles: The maximum number of miles the candidate may be away from the job to be accepted.
CandidateIdsInList: The response should be a subset of this list of ATS Candidate IDs.

Complete the required fields.
- Method - There are three options to choose from:
  - GET: This can be used to initiate and/or test a particular endpoint from the third-party application.
    - Note: Bullhorn Automation does not store and/or process any response from the GET request or through any other method in the Webhook Step. This method cannot pull data from the third-party application.
  - POST: This can be used to create a new resource in the destination end point, using information from the entity record entering this step in the automation.
  - PUT: This can be used to update an existing resource in the destination endpoint, using information from the record entering this step in the automation.
- URL - This setting allows the configuration of what endpoint the Webhook Step should be sent to. Bullhorn Automation Merge Tags can be added here to allow you to use the data of a record that gets passed through the automation step as an identifier in the URL.
  - Example: Candidate ATS ID.
- Header - The Include Header checkbox allows the configuration of a header to be sent along with the API Request.
  - Single or multiple headers under a Header Prefix | Header Content parameter to value configuration are supported
  - The Webhook step doesn’t support specific user authentication, so any endpoint that requires an Auth process will need to occur through the parameters set in the header of the Webhook step.
- Response - The following response types are supported:
  - Array of objects - the Candidate ID is a property on an object which has other properties as well such as a MatchScore field.
  - Array of Candidate IDs: - the Candidate IDs are in an array.
- Candidate IDs Field Name - This is the name of the field that contains the Candidate ID(s). If the field is nested, you specify the hierarchy with dot notation.
  - Example: “ParentObject.ChildObject.CandidateID”
- Match Score Field Name - This is only available if the response type is an Array of objects. This is an optional field. If specified, this is the matching score determined by the algorithm and will be displayed in Bullhorn Automation. The expected value is between 0-1.
Click Save.

Testing the Webhook

There is an option to test the Webhook configuration. Follow these steps to test.

Navigate to Settings > API > Match Candidate Webhook
Ensure that your Webhook is Activated
Select Test Webhook
Fill out the information in the form
Select Test Webhook