Skip to content

HR & recruiting integration

Bullhorn integration for AI workflows.

Beta — requires your Bullhorn API access. Keep candidates, job orders and placements in sync, and react to new candidates and jobs.

Start free See pricing
Beta

In short

Fluxo Flow connects to Bullhorn with an API key or credentials you provide; workflows can search candidates, create a candidate and create a job order and more, and start from new candidate and new job order. The integration is in beta.

Beta means it works but hasn't been tested against every account setup yet; actions and fields may still change. Found a problem? Tell us.

What you can do

Actions and triggers for Bullhorn.

Actions

  • Search candidates

    Finds candidates with a Bullhorn (Lucene) search, e.g. email:"ada@example.com".

  • Create a candidate

    Adds a candidate record.

  • Create a job order

    Adds a job order for a client contact.

  • Search job orders

    Finds job orders with a Bullhorn (Lucene) search, e.g. isOpen:1.

  • Create a placement

    Places a candidate on a job order.

  • Update a record

    Updates fields on a candidate, job order, placement, contact, company, lead or opportunity.

  • Get a record

    Reads a record by ID.

  • Add a note

    Adds a note about a candidate or contact.

Triggers

  • New candidate (checked on your plan's schedule interval)

    Starts a run for each candidate added in Bullhorn (checks the newest candidates on your plan's schedule).

  • New job order (checked on your plan's schedule interval)

    Starts a run for each job order added in Bullhorn (checks the newest job orders on your plan's schedule).

Build it yourself

What teams build with Bullhorn.

There's no ready-made template for Bullhorn yet. These are the workflows to build: each step is a real node or Bullhorn action.

  • Duplicate-safe candidate intake

    1. Webhook trigger (sourcing form)
    2. Bullhorn: Search candidates
    3. Router: exists?
    4. Bullhorn: Add a note / Create a candidate

  • Job order intake

    1. Webhook trigger (client request)
    2. AI Generate: job order fields
    3. Human Review: account manager
    4. Bullhorn: Create a job order

  • New job order alert

    1. Bullhorn: New job order
    2. AI Generate: two-line summary
    3. Slack: Post a message

Step-by-step guides: Recruiting automation: what to automate in Bullhorn and Greenhouse (and what never to)

How to connect

Connect Bullhorn in a minute.

Connects with an API key or credentials, tested before they're saved and encrypted at rest.

  1. Ask Bullhorn Support for REST API access: an OAuth client ID and secret, and a dedicated API user.
  2. In Fluxo Flow open Settings → Integrations → Bullhorn, pick your data center and paste the client ID/secret and the API user's username/password.
  3. Use the Bullhorn actions in a workflow, or start one from “New candidate” or “New job order”.

What you need on the Bullhorn side

  • REST API credentials from Bullhorn Support: an OAuth client ID and secret and a dedicated API user.
  • Your Bullhorn data center (picked when connecting).

Permissions & limits

What it can access, and how fast it runs.

Limits and timing

  • Polling triggers are checked on your plan's schedule interval: Basic every 15 minutes, Pro every 5 minutes, Business every 2 minutes, Elite every minute.
  • Bullhorn triggers check at most every 5 minutes, whatever your plan, to respect Bullhorn's limits.
  • If Bullhorn says to slow down (HTTP 429 or 503), requests wait as told and retry a limited number of times.
  • Required fields on create depend on your Bullhorn field mappings; add any Bullhorn asks for under the action's More fields.

Ready-made agents

AI agents that use Bullhorn.

Finished workflows that connect to Bullhorn. Pay once, connect your apps, Dry Run and switch on.

Browse all agents

FAQ

Bullhorn questions, answered.

Why do I need a client ID from Bullhorn?

Bullhorn only issues REST API credentials to customers and partners through Bullhorn Support. Once you have them, Fluxo signs in with them on your behalf and renews the session automatically.

Which fields are required when creating records?

Bullhorn's field mappings decide that per account. If Bullhorn says a field is missing, add it under the action's “More fields”.

How quickly do the triggers fire?

They check the newest records on your plan's schedule interval (5 minutes at the fastest).

Is the Bullhorn integration finished?

It's in beta: it works, but it hasn't been tested against every account setup yet. Tell us if something doesn't behave as expected.

Can I use Bullhorn on the Free plan?

You can connect it, build with it and Dry Run on the Free plan. Running workflows live (triggers, schedules, webhooks) needs a paid plan.

Can I call Bullhorn endpoints the integration doesn't cover?

Yes, if Bullhorn has an API: save a key in the encrypted credential vault and call it with an HTTP Request step.

Can I test a workflow without touching my real data?

Yes. Dry Run walks through every step with simulated app calls, so nothing is sent until you run it for real or activate its trigger.

All integrations

Connect Bullhorn to your first workflow.

Build and Dry Run on the Free plan, no credit card. Run live on a paid plan, on your own AI key at cost.

Start free See pricing

Free to explore · No credit card · 30-day money-back guarantee on paid plans