Third Party AI Automatch

The Third-Party Auto-Match Algorithm allows a third-party job matching service to be used in place of the Bullhorn Automation AI Auto Match feature.

When a job hits the auto match step rather than using the Bullhorn Automation Machine Learning algorithm to match candidates users can configure their settings to use a third-party algorithm if it better suits their needs.

Prerequisites

• Webhooks Enabled

• API Tab Enabled

• MaxCandidates, MinScore, MaxDistance, and CandidateIds will be required either in the Data or URL sections

Workflow Overview

• A job will enter the auto-match step in a customer’s environment

• Automation will make an HTTP request to the 3rd party’s specified endpoint

• The payload will include the job ATS ID, job title, and customer-defined key match settings

• The 3rd party will return a list of ATS Candidate IDs.

• The auto-match step will then retrieve the candidates based on those ATS Candidate IDs and the step will execute according to the Automation settings.

Configuration

• Navigate to Settings > API > Match Candidate Webhook

• Select Edit

• 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

Adding Automation

When adding an Automation to the Job Entity to Match Candidates the information added in the Match Candidates Webhook will be used to create the list of candidates.

Users will set match preferences as part of the Match Candidates automation step.