Overview
We're pleased to announce the January 2026 release for Bullhorn integration, focusing on improvements to candidate event routing. This update resolves an issue where Job Application events were incorrectly using the Candidate Registration status field, causing applications to be misrouted in Bullhorn.
What's new
This release introduces improved configuration options for your Bullhorn integration to ensure accurate candidate routing.
Separate status fields for registrations and applications
You can now control status values separately for Candidate Registrations and Job Applications. Previously, both events used the same status field, which caused Job Applications to route incorrectly in Bullhorn. Two distinct configuration fields now give you precise control over how each event type is handled.
The existing Status text for Candidate records field continues to control Candidate Registration events when someone signs up on your careers site.
The new Bullhorn Status Text for Job Applications field controls Job Application events when someone applies to a job posting.
This field defaults to New Lead if left empty, ensuring applications route correctly to Bullhorn's Online Response bucket.
Benefits you'll gain:
Accurate routing of Job Applications to the correct Bullhorn bucket based on your requirements.
Flexible configuration that lets you set different status values for Registrations versus Applications.
Automatic default behaviour that maintains correct routing without requiring reconfiguration.
📌 Note: For detailed configuration steps and field explanations, see the Bullhorn Integration Help Guide.
How to access this update
This version updated automatically on January 2026.
FAQs
Q1: Do I need to reconfigure my Bullhorn integration?
Answer: No reconfiguration is required. The existing Status text for Candidate records field continues to work for Registrations. The new field defaults to "New Lead" if left empty, maintaining correct behaviour for Job Applications.
Q2: What should I do about applications sent between 5-20 January?
Answer: Check alternative buckets in Bullhorn based on the status value configured during that period. Applications may require manual reassignment in Bullhorn if they were routed incorrectly.
Q3: When should I customise the new Bullhorn Status Text for Job Applications field?
Answer: Only customise this field if you have specific Bullhorn routing requirements for Job Applications that differ from the standard "Online Response" bucket. Most customers should leave this field empty to use the default "New Lead" status.
Q4: How can I tell which field controls which event?
Answer: The Status text for Candidate records field controls Candidate Registration events when someone signs up. The Bullhorn Status Text for Job Applications field controls Job Application events when someone applies to a job posting.
Q5: Can both fields have the same value?
Answer: Yes, both fields can use the same value such as "Available". However, this may affect Bullhorn routing for applications depending on your Bullhorn configuration.
Q6: What happens if I leave the new field empty?
Answer: The system automatically uses "New Lead" as the status for Job Applications, which routes them to Bullhorn's "Online Response" bucket. This is the standard behaviour for most customers.
Q7: Where can I find these configuration fields?
Answer: Go to CMS, then Settings, then Apps, then Bullhorn. Both status fields are available in this configuration area.
Q8: Will this change affect my existing Candidate Registrations?
Answer: No, existing Candidate Registration behaviour remains unchanged. The Status text for Candidate records field continues to control Registration events exactly as before.