Skip to content

For staffing agencies & recruiting teams

Let software organize the pipeline. Let recruiters decide.

Notifications, record hygiene, factual summaries and job-order intake are safe to automate. Ranking, rejecting and offering aren't. Fluxo Flow does the first and routes the second to a recruiter.

Start free See pricing

In short

Fluxo Flow connects to Bullhorn and Greenhouse through beta connectors that use your own API credentials. Recruiting teams use it to summarize new applications for a recruiter, catch duplicate candidates, turn client job requests into job orders, and move applications between stages only after a person approves. AI never rejects or ranks candidates on its own.

Staffing & recruiting: key facts
ATS connectorsBullhorn (candidates, job orders, placements, notes) and Greenhouse (Harvest v3: candidates, notes, stage moves, rejections), both in beta.
TriggersNew candidate and new job order (Bullhorn); new application, new candidate and instant web hooks (Greenhouse).
PrincipleAssist, don't decide: summaries and checks are automated, decisions about people go through Human Review.
RegulationAutomated tools that score or rank candidates can be regulated (for example NYC Local Law 144). Check with counsel.

What changes

Less copying, chasing and checking.

  • Today

    Recruiters open every application to find out if it's even close.

    With Fluxo Flow

    A short, factual summary of the application against the job's stated requirements lands as a note on the candidate, with nothing scored or hidden.

  • Today

    The same candidate exists three times in the ATS.

    With Fluxo Flow

    Before creating a candidate, a search by email finds the existing record; the workflow adds a note instead of a duplicate.

  • Today

    Client job requests arrive as emails and calls, then get retyped.

    With Fluxo Flow

    An intake form becomes a structured job order draft that the account manager approves before it's created in Bullhorn.

  • Today

    Stage moves and their emails happen late or not at all.

    With Fluxo Flow

    A recruiter approves the move in the Review Queue and Greenhouse's own stage rules and emails run at once.

Example workflows

Five workflows you could build this week.

Each one uses nodes that exist on the canvas today. Start from a blank canvas or a marketplace agent and adapt it.

Application summary for the recruiter

5 steps

Each new Greenhouse application gets a factual summary note and a Slack heads-up for the recruiter.

  1. Step 1: App event triggerGreenhouse: New application (beta)
  2. Step 2: AI GenerateList evidence for each stated requirement, no score
  3. Step 3: GuardrailBlock protected-trait mentions
  4. Step 4: IntegrationGreenhouse: Add a note to the candidate
  5. Step 5: Slack PostTell the recruiter

Result: Recruiters start from a summary, and every decision is still theirs.

Duplicate-safe candidate intake

4 steps

Candidates from a sourcing form are matched by email before anything is created.

  1. Step 1: Webhook triggerSourcing or referral form
  2. Step 2: IntegrationBullhorn: Search candidates by email
  3. Step 3: RouterAlready in Bullhorn?
  4. Step 4: IntegrationBullhorn: Add a note / Create a candidate

Result: One record per person, with every touch logged on it.

Job order intake

5 steps

A client's job request is structured by AI and created in Bullhorn after the account manager checks it.

  1. Step 1: Webhook triggerClient job request form
  2. Step 2: AI GenerateTitle, location, rate, must-haves as JSON
  3. Step 3: ValidatorRequired fields present
  4. Step 4: Human ReviewAccount manager approves or edits
  5. Step 5: IntegrationBullhorn: Create a job order

Result: Job orders that are complete on day one, without retyping.

Stage move, approved by a recruiter

5 steps

New applications wait in the Review Queue with their summary; the recruiter's decision moves them and Greenhouse runs its stage rules and emails.

  1. Step 1: App event triggerGreenhouse: New application (beta)
  2. Step 2: AI GenerateFactual summary for the reviewer
  3. Step 3: Human ReviewRecruiter approves the next stage
  4. Step 4: IntegrationGreenhouse: Move an application to a stage
  5. Step 5: Slack PostNotify the hiring manager

Result: Candidates move on the day the decision is made, and the decision is on record.

New job order alert

3 steps

New Bullhorn job orders are announced to the right desk with the essentials.

  1. Step 1: App event triggerBullhorn: New job order (beta)
  2. Step 2: AI GenerateTwo-line summary and must-haves
  3. Step 3: Slack PostPost to the desk's channel

Result: Recruiters start sourcing within one schedule interval of the order landing.

Apps

The apps these workflows use.

Status comes straight from each integration's definition. Beta means it works but hasn't been tested against every account setup yet.

Human in the loop

What AI must never do here

Put a Human Review step in front of these. The run waits in the Review Queue until someone approves, edits or rejects it.

  • Reject, rank or score a candidate on its own
  • Decide who gets an interview, an offer or a placement
  • Infer age, health, ethnicity or any other protected trait
  • Send a candidate bad news without a person reading it

Features

The parts you'll use most.

Plans

Which plan usually fits.

Explore free with no credit card and Dry Run your workflows. Upgrade to run them live, with more workflows, seats and faster schedules.

  • Usually the best fit

    Pro$119/mo

    A recruiting desk: several workflows, seats for recruiters and approvers, faster schedules.

    • 25 workflows
    • 5 seats
    • Schedules as often as every 5 minutes
    • 2 marketplace agents included

  • Also a good fit

    Basic$39/mo

    A solo recruiter automating notes and alerts.

    • 15 workflows
    • 3 seats
    • Schedules as often as every 15 minutes

Compare every plan

FAQ

Questions, answered.

Can AI screen out candidates automatically?

We don't recommend it and don't build it that way. Use AI to summarize evidence against stated requirements, and let a recruiter make every decision about a candidate. Automated screening can fall under rules such as NYC Local Law 144.

Does it work with Greenhouse's Harvest API keys?

No. Greenhouse removed Harvest v1 and v2 on August 31, 2026. The connector uses Harvest v3 with an OAuth client ID and secret you create in Greenhouse.

How do I get Bullhorn API access?

Bullhorn issues REST API credentials (client ID, secret and an API user) through Bullhorn Support. Once you have them, the connector signs in and renews the session for you.

Who do notes and stage moves show up as?

In Greenhouse, as the credential's integration user or the Site Admin you set on the connection. In Bullhorn, as the API user.

Automate your first recruiter alert this week.

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