List Criteria Support

This article documents known behaviors and limitations when building list criteria in Bullhorn Automation, organized by entity type.

Contacts and Candidates

• When records are merged in Bullhorn ATS, the deleted record is removed from all lists in Bullhorn Automation.
• To return records opted out in Bullhorn ATS specifically, use “Subscription Status IS NOT Subscribed”.

Primary vs. Additional Contacts

Bullhorn Automation communicates only with the main contact in the Sales Contact field. Additional contacts in other fields cannot be processed through an automation as the primary Sales Contact.

Notes with Multiple Sales Contact References

When a Note references more than one Sales Contact via the Additional References field, Bullhorn Automation can only attach it to one of those records. The record it attaches to is chosen at random, and the other referenced contacts do not receive the note.

This causes a common symptom: a “Contacts without Notes” list in Bullhorn Automation shows a higher count than the same search in Bullhorn ATS. The contacts that appear note-free in Automation are not missing data — their notes exist in the ATS but were attached to a different referenced record in Automation.

Notes on Cross-Entity References

Bullhorn Automation does not pull in Notes where a Sales Contact is referenced on a Note that belongs to a Candidate record. Only Notes directly associated with the Sales Contact record are synced.

Date Criteria

• ”More Than/Less Than X Days Ago” is inclusive of the specified number of days. Verify by checking matched records for someone who fits the criteria exactly on the day of.
• When using date logic on statuses, Bullhorn Automation looks at the date the record was added to the database with that status, not the date the status was changed.
• ”Before” and “After” date qualifiers include the selected date and require the record to currently have the selected status.
• Date parameters only apply to fields where activity data is captured by date. Job records do not capture date modifications the same way other entities do.
• The Bullhorn ATS API does not provide access to the Date Modified field or the Activity tab. The only exception is the Date Added field.

Using Dynamic Date Criteria

To return Candidates with a Placement ending in the next 30 days dynamically, use the following criteria:

Using “IS NOT” Logic with Date Qualifiers in the Same Logic Statement

This finds all Submissions where “Packet Created” equals 1 and “Date Added” is less than 2 days ago, then returns everything except those records because of the IS NOT qualifier. The IS NOT applies to the entire statement, including the date qualifier field.

Submissions

• ”Submission Status: Placed” is the standard status for returning Submissions that resulted in Placements.
• ”Job Is Open” and “Submission Job Is Open” return the same results.
• ”Has Submission” returns Submissions of any status (Rejected, Shortlisted, Web Response, etc.). To filter by a specific status, use “Submission Status IS = X”.
• If a Candidate is added to a Tearsheet and a Placement or Submission-based list is created, every associated Placement or Submission is returned unless additional logic is added to narrow the results.

Video Example

• ”Submission Date Added” is the date the Submission was created, not the date it moved to “Client Submission” status.