Agentic credentialing, built into Bullhorn.

A placement is approved in Bullhorn. The agents pull the candidate, the client and the start date, build the requirement list, prepare the offer letter, verify every credential, and write the finished file back to the record. Bullhorn stays the system of record.

Getting started

Connect Bullhorn this morning. Files back this week.

01

donenow

Connect Bullhorn

API credentials, no package to install.

BU

Bullhorn

bullhorn.com

Connected · 10:02 am

02

donenow

Choose what is in scope

A division, a recruiter, a client. Start small.

Placement·status is Approved
Division·Travel Nursing
Start date·next 45 days

142 placements match · 3 start this week

03

donenow

First files back

Cleared, written to the record, in days.

  • Lauren Chen

    ICU RN · Riverside Medical

    queuedworking
  • Marcus Ellery

    Cath Lab RN · St. Vincent

    queuedworking
  • Priya Nair

    OR Tech · Lakeview

    queuedworking

written back to Bullhorn · certifications, files, notes

Placement in

Approved in Bullhorn, picked up in seconds.

The moment a placement or job submission is approved, the agents pull the candidate, client, facility and start date, build the requirement list for that client, and prepare the offer letter for signature.

Files both ways

Read what Bullhorn holds. File what it was missing.

The agents fetch the files already on the candidate, read each one, verify it at the source, correct a stale expiry, and push every credential into Bullhorn Certifications with its expiry and evidence attached.

Notes back

Every conversation lands as a Bullhorn note.

Texts, emails and calls with the candidate, and every verification the agents complete, are filed as notes on the Bullhorn record under your own action types, so a recruiter sees the whole file without leaving Bullhorn.

Bullhorn keeps the record. The agents do the credentialing.

Live in an afternoon

Four steps. No rip-and-replace.

Connect

Bullhorn API credentials or an authorized login. Ten minutes.

Scope

One division, one recruiter or one client. The agents pick up only what you point them at.

Shadow

The first files run beside your team. Nothing writes back until you say so.

Write back on

Certifications, files, notes and status flow to the record. Specialists direct from Bullhorn.

Only need screening?

Screen your Bullhorn roster against OIG, SAM and OFAC.

Everyone your saved Bullhorn filter matches, searched at each list every month, the result page captured, a dated PDF filed back on the candidate. It runs on its own, with or without the rest of the credentialing work.

See evidence-based screening →

Questions

Does Credentialing Agents integrate with Bullhorn?

Yes. Credentialing Agents connects to your Bullhorn account through the Bullhorn REST API. Approved placements and job submissions poll in and open credentialing files, bulk import onboards everyone already on contract, client documents import into the library, and finished credentials, files and notes are written back to the candidate record. A Credentialing Agents tab inside Bullhorn opens the candidate's vault.

How does credentialing work inside Bullhorn?

A placement is approved in Bullhorn. The agents pull the candidate, client, facility and start date, build the full requirement list for that client (typically 30 to 50 items), match what Bullhorn already holds, prepare and send the offer letter, verify licenses and certifications at the source, order background checks, chase the candidate by text and email, route e-signatures, and write the result back. Your specialists review flags and judgment calls; the chasing is gone.

Where do credentials and documents go in Bullhorn?

Certifications. Each verified credential is pushed to the candidate's Certifications in Bullhorn under your certification mapping, with the expiry date set and the evidence file attached. Your mapping decides whether a push replaces the most recent entry, attaches the file, or always creates a new row. Other documents land in Files; conversations and verifications land in Notes.

Can the agents read files that are already in Bullhorn?

Yes. The agents fetch the files on the candidate record, classify each one (license, BLS card, TB result, resume), read the dates and numbers, verify them at the issuing source, correct what is stale, and match them to the requirement list so nobody is asked for a document Bullhorn already has.

What starts a credentialing file in Bullhorn?

An approved placement, by default. Job submissions can start the pre-work early, so the file is most of the way done before the placement is approved, and bulk import opens a file for everyone currently on contract. Files can also start from a forwarded email or a one-line text.

Do we need a Bullhorn Marketplace app or IT work?

No. Setup is API credentials or an authorized Bullhorn login, done in an afternoon, with no change to your Bullhorn configuration. You choose the scope (a division, a recruiter, a client) and whether write-back is on. The first files run in shadow beside your current process.

Can we screen our Bullhorn roster against OIG, SAM and OFAC?

Yes. Continuous monitoring screens everyone matched by your saved Bullhorn filter against OIG LEIE, SAM.gov and OFAC every month, with the result page captured and a dated PDF filed on the candidate as a certification. It runs on its own, with or without the rest of the credentialing work.

See a Bullhorn placement worked live.

Thirty minutes, one real placement from your Bullhorn, approved to cleared and written back.