Skip to content

HR & recruiting integration

Greenhouse integration for AI workflows.

Beta — requires your Greenhouse API access. Add candidates and notes, move or reject applications, and react to new applications.

Start free See pricing
Beta

In short

Fluxo Flow connects to Greenhouse with an API key or credentials you provide; workflows can create a candidate, find a candidate by email and read a candidate's activity feed and more, and start from new application, new candidate and greenhouse web hook (instant). 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 Greenhouse.

Actions

  • Create a candidate

    Adds a candidate, optionally applying them to a job.

  • Find a candidate by email

    Looks up candidates with this email address (case-insensitive).

  • Read a candidate's activity feed

    Lists the notes, emails and activity on a candidate's activity feed (Harvest v3 replaced the v1 activity_feed with the notes list).

  • Add a note to a candidate

    Posts a note on the candidate's Notes tab (or a free-form activity feed entry).

  • Move an application to a stage

    Moves an application to another interview stage of its job (runs Greenhouse's stage rules and automated emails).

  • Reject an application

    Rejects an application with a rejection reason.

Triggers

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

    Starts a run for each new application (checked on your plan's schedule interval).

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

    Starts a run for each new candidate or prospect (checked on your plan's schedule interval).

  • Greenhouse web hook (instant) (instant webhook)

    Instant events from a Greenhouse web hook you create (Configure → Dev Center → Web Hooks): new applications, stage changes, hires and rejections.

Build it yourself

What teams build with Greenhouse.

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

  • Application summary for the recruiter

    1. Greenhouse: New application
    2. AI Generate: evidence per requirement, no score
    3. Greenhouse: Add a note to a candidate
    4. Slack: Post a message

  • Stage moves a recruiter approves

    1. Greenhouse: New application
    2. Human Review: recruiter decides
    3. Greenhouse: Move an application to a stage

  • Referral intake

    1. Webhook trigger (referral form)
    2. Greenhouse: Find a candidate by email
    3. Router: exists?
    4. Greenhouse: Create a candidate

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

How to connect

Connect Greenhouse in a minute.

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

  1. In Greenhouse (Site Admin), open Configure → Dev Center → API Credentials and create a Harvest V3 (OAuth) credential with the scopes you need.
  2. In Fluxo Flow open Settings → Integrations → Greenhouse and paste the client ID and secret (optionally the user ID to act as).
  3. Use the Greenhouse actions in a workflow, or start one from a new application, a new candidate or a Greenhouse web hook.

What you need on the Greenhouse side

  • A Site Admin creates a Harvest V3 (OAuth) credential in Greenhouse (Configure → Dev Center → API Credentials) with the scopes listed below.
  • Harvest v1/v2 API keys no longer work: Greenhouse removed them on August 31, 2026.

Permissions & limits

What it can access, and how fast it runs.

Permissions requested

  • Create a candidate

    harvest:candidates:create

  • Find candidates, New candidate trigger

    harvest:candidates:list

  • Add a note

    harvest:notes:create

  • Read a candidate's activity feed

    harvest:notes:list

  • Move an application

    harvest:applications:move, harvest:job_interview_stages:list

  • Reject an application

    harvest:applications:reject, harvest:rejection_reasons:list

  • New application trigger

    harvest:applications:list

  • Job pickers

    harvest:jobs:list

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.
  • Greenhouse triggers check at most every 5 minutes, whatever your plan, to respect Greenhouse's limits.
  • Instant triggers arrive by webhook within seconds of the event.
  • If Greenhouse says to slow down (HTTP 429 or 503), requests wait as told and retry a limited number of times.
  • Rejections should always go through a Human Review step; we don't recommend automated rejection.

Ready-made agents

AI agents that use Greenhouse.

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

Browse all agents

FAQ

Greenhouse questions, answered.

Does this use the old Harvest API key?

No. Greenhouse removed Harvest v1/v2 (API keys) on August 31, 2026. This connector uses Harvest v3 with an OAuth client ID and secret you create in Greenhouse.

Who do notes and moves show up as?

As the credential's integration user, or as the Site Admin whose user ID you enter on the connection.

Is it instant?

The new-application and new-candidate triggers check Greenhouse on your plan's schedule. For instant events, use the web hook trigger and paste its URL and secret into a Greenhouse web hook.

Is the Greenhouse 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 Greenhouse 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 Greenhouse endpoints the integration doesn't cover?

Yes, if Greenhouse 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 Greenhouse 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