Integration directory
Bullhorn logo
Recruiting and ATSSelf serve

Bullhorn

Bring the staffing records behind candidates, jobs, placements, clients, credentials, and locations into the Teambridge workflows that operate after recruiting.

Connection at a glance

Bullhorn logoBullhorn
TeambridgeTeambridge

Bullhorn to Teambridge ATS records. Teambridge to Bullhorn candidate creation. Optional identity handoffs to Bullhorn services.

How it works

How Teambridge connects with Bullhorn

Teambridge polls Bullhorn event subscriptions every minute and syncs candidates, jobs, placements, clients, contacts, credentials, and related staffing records.

Admins can also create a Bullhorn candidate from Teambridge. Optional Able and Bullhorn Time Entry paths support onboarding and identity handoffs.

Verified data movement

What moves, where, and when

01
BullhornTeambridgeEvery minute

Teambridge polls Bullhorn event subscriptions and upserts or deletes changed records in batches.

02
TeambridgeBullhornAdmin action

An administrator can create a Bullhorn candidate from a Teambridge worker record.

03
TeambridgeBullhorn Time EntryIdentity handoff

A linked candidate can receive a SAML identity assertion for Bullhorn's time product.

What the connection supports

  • Fourteen mapped Bullhorn entity types
  • Near real time event polling
  • Candidate creation
  • Ordered collection sync
  • Optional Able onboarding flow

Scope and limitations

  • Main ATS sync is polling, not a push webhook
  • Bullhorn Time Entry is identity access only
  • Some accounts include bespoke candidate filters

Operational use cases

Where Bullhorn fits in the work

The connection matters when it removes a specific handoff without losing the worker, customer, job, approval, or document context behind it.

01

Operate from the ATS record

Map fourteen Bullhorn entity types into ordered Teambridge collections.

02

Carry placements into work

Connect candidates, jobs, submissions, placements, clients, and locations before scheduling begins.

03

Support optional onboarding

Use the separate Able connection for configured applicant and onboarding handoffs.

Implementation path

Set up the connection around one verified outcome

Configuration varies by account and system. These steps establish the minimum path Teambridge should validate before the connection is trusted in production.

  1. 1

    Connect Bullhorn

    Enter the customer's Bullhorn REST API username and password.

  2. 2

    Choose collections

    Map the Bullhorn entities required by the Teambridge operating model.

  3. 3

    Review sync order

    Confirm that supporting records such as clients and locations arrive before dependent placements.

  4. 4

    Validate account rules

    Test any candidate filters or bespoke rules applied to the customer account.

Questions and answers

What teams ask about Bullhorn

What does the Bullhorn integration with Teambridge do?+

Sync ATS entities on a near real time polling cycle and create candidates from Teambridge. Bring the staffing records behind candidates, jobs, placements, clients, credentials, and locations into the Teambridge workflows that operate after recruiting.

What data moves between Bullhorn and Teambridge?+

Bullhorn to Teambridge ATS records. Teambridge to Bullhorn candidate creation. Optional identity handoffs to Bullhorn services.

How do you set up the Bullhorn integration?+

Enter the Bullhorn REST API username and password, choose the mapped collections, then review account specific candidate filters and optional Able setup.

Is the Bullhorn integration generally available?+

A customer administrator can start the connection without a Teambridge feature flag. The most important current boundary is: Main ATS sync is polling, not a push webhook.

Get started