Works with Greenhouse. This connection is in beta. When a candidate reaches an interview stage you choose, PreHireBadge creates a check request in Ready to send. A person on your team confirms and sends it. When the check is complete, Greenhouse gets a status note on the application. Reports, results, and AI summaries stay in PreHireBadge.
Who it is for. An owner or admin who uses Greenhouse to manage candidates and wants check requests to start from the hiring pipeline without switching tools.
How to connect
- In Greenhouse, open Configure, then Dev Center, then API credentials. Create a Harvest v3 credential for PreHireBadge. Allow jobs, interview stages, applications, candidates, and notes. Copy the client ID and the client secret. The secret is shown once.
- Greenhouse only lets list calls through when the authorizing user is a Site Admin. Make sure the user who authorizes the credential has the Site Admin role.
- In PreHireBadge, open Settings, then Integrations, find Greenhouse, and choose Connect. Paste the client ID and the client secret, then accept the integration certification.
- Pick the interview stages that should request a check, your default work location, and the default pay band.
Stages are chosen by name
You choose stages by name. A choice applies to every job that has a stage with that name. If only some jobs should request a check, give those jobs their own stage name in Greenhouse.
What Greenhouse receives
PreHireBadge adds a status note to the application in Greenhouse. The note is visible to anyone on the job, so it holds only the status. It looks like this:
PreHireBadge background check: Clear. Updated Nov 11, 2026. Check 0B6F2B1E. Sign in to view: …
Greenhouse never receives the report, results, AI summaries, or resumes. Rejected and hired statuses come straight from Greenhouse; PreHireBadge reads them to run the adverse action watchdog.
No instant updates: the five-minute check
Greenhouse does not send instant updates to PreHireBadge. A background check runs every five minutes, so a stage change, a rejection, or a hire shows up within about five minutes.
A person sends every check
When something fails
Settings, then Integrations, lists each connected app. The Activity card shows recent requests. Each error includes a short fix. Common problems:
- The hiring tool did not accept the saved key. The credential may have been deleted, may be missing a permission above, or may have been authorized by a user who is not a Site Admin. Create a new credential in Greenhouse if needed, then Disconnect and connect again with the new client ID and secret.
- The hiring tool refused a request. A stage you chose may have been renamed or removed in Greenhouse. Reselect the stages in the Setup section on the integration page.
Disconnect there to stop the integration. Requests already waiting in Ready to send can still be dismissed.
See Integrations and the FCRA and adverse action watchdog for more on how connected hiring tools work with PreHireBadge.