Checkr

Automate background checks with Checkr. Agents create candidates when hires advance in an ATS, send secure screening invitations, order reports directly when candidate data is on file, poll report status, and look up available screening packages.

8 actions Basic auth available

Checkr website ↗ Platform Documentation ↗ Capability data verified 2026-07-28

An applicant advances to the offer stage in the ATS

List Candidates confirms this person has not already been screened for this role

Create Candidate adds them to Checkr with the contact details on file

List Packages resolves the standard screening package for this role and work location

The recruiting lead confirms the package choice and that consent paperwork is complete before any screening begins

Create Invitation emails the candidate a secure link to submit their own information

Get Invitation and Get Report poll until the screening reaches a terminal status

The completed result routes to the hiring channel and logs against the employee record

What This Integration Enables

Background checks sit on the critical path between offer and start date, and every day they idle is a day the candidate is fielding other offers. FlowRunner agents keep that path moving without touching what should never be automated: the decision to screen someone, and the decision about what happens after. Agents create candidates when hires advance in the ATS, send secure self-service invitations so applicants submit their own sensitive data, order reports directly when information is already on file, poll status until results land, and standardize which packages get ordered for which roles. - Kick off screening from a [Greenhouse](/integrations/greenhouse) hire event or [Workable](/integrations/workable) stage change - Send secure invitations so candidates self-submit SSN and address data instead of emailing it - Order reports directly for rescreens where the candidate's data is already on file - Poll invitation and report status and route completed results to [Slack](/integrations/slack), a sheet, or email - Log screening outcomes onto the employee record in [BambooHR](/integrations/bamboohr) - Enforce package standards by role, so the driver role always gets the MVR and the office role never pays for one

Without FlowRunner

Screening starts when someone remembers The offer goes out, days pass, then someone notices the background check was never ordered

Candidate data retyped into a portal SSNs and addresses move by copy-paste between the ATS and the screening dashboard

Status checked by logging in "Is the check back yet?" means someone opening Checkr to look, again

With FlowRunner

Screening starts at the stage change The ATS advance creates the candidate and sends the invitation the same hour

Candidates enter their own data The secure invitation link means sensitive fields never pass through a recruiter's clipboard

Status comes to the team Completed reports post to the hiring channel and log to the HR record automatically

Use Case Scenarios

Offer accepted, screening already moving

[Greenhouse](/integrations/greenhouse) fires a hire event. The agent creates the candidate in Checkr from the application's contact details, resolves the role's standard package from List Packages, and queues the order for the recruiting lead's confirmation. On approval, Create Invitation emails the candidate their secure link. By the time the signed offer letter is filed, the candidate is already entering their information, and the start date stops slipping for administrative reasons.

The status board nobody has to refresh

Twice a day, the agent sweeps open screenings: Get Invitation for anything pending or expired, Get Report for anything in progress. Expired invitations trigger a re-send proposal to the recruiter. Completed reports post to the hiring channel in [Slack](/integrations/slack) with the overall status, and the outcome logs against the employee's profile in [BambooHR](/integrations/bamboohr). Nobody logs into the dashboard to answer "is it back yet?" because the answer arrives on its own.

The contractor rescreen cycle

A fleet company rescreens drivers annually. On each driver's anniversary, the agent finds their record with List Candidates, confirms their data is on file with Get Candidate, and stages a Create Report order with the motor vehicle package. The ops manager reviews the week's rescreen batch every Monday, removes anyone who has left, and approves the rest. Results flow back to the compliance sheet as they complete, and lapsed screenings stop being discovered during audits.

Human-in-Loop Highlight

Create Report runs real screenings on a real person the moment it executes: SSN trace, criminal searches, motor vehicle records, whatever the package bundles. Each order spends screening fees that are not refunded when the target turns out to be the wrong Jordan Smith, and screening a person is a legal act with consent obligations attached, not a data operation to retry casually. So no FlowRunner flow lets an agent order screenings unattended. The agent assembles everything: candidate record, package slug, work location, whether consent paperwork is on file. The recruiting lead reviews that assembly, "Order Standard Criminal + MVR for Jordan Smith, driver role, Dallas, consent signed 07/22?", and the order runs only on their yes. Create Invitation carries the same gate for a plainer reason: it emails a person a request for their Social Security number, and that email should never surprise anyone, least of all the sender.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via email

Human decides

Agent resumes with decision

Agent Capabilities

8 actions

Candidates

List Candidates Retrieves a paginated list of candidates in the account. The dedup check before creating a candidate and the roster behind rescreen cycles.
Get Candidate Retrieves one candidate in full by ID: personal information, contact details, and associated identifiers. The verification step before ordering anything against a record.
Create Candidate Creates the person to be screened, from an email or full contact details. SSN and date of birth can be added later, or better, self-submitted by the candidate through an invitation.

Invitations

Create Invitation Emails the candidate a secure link to submit the information a screening package requires, scoped to a package slug and work locations. The privacy-preserving path: sensitive data goes from the candidate to Checkr directly.
Get Invitation Retrieves an invitation by ID with its status of pending, completed, or expired, the secure application URL, and the associated candidate and package. The polling read behind re-send logic.

Reports

Create Report Orders a background check directly for a candidate whose data is on file, running the package's screenings. The spend-and-screen action this connector's human gate exists for.
Get Report Retrieves a report by ID with its overall status and result, the package used, and references to each screening, such as SSN trace, sex offender search, criminal searches, and MVR. The read that routes results to the people waiting on them.

Packages

List Packages Retrieves the screening packages available in the account, each bundling a set of screenings under a slug. The reference data that standardizes which checks each role gets.

Frequently Asked Questions

What can FlowRunner do with Checkr?

FlowRunner agents can run List Candidates, Get Candidate, and Create Candidate in Checkr, plus 5 more actions.

Does connecting Checkr to FlowRunner require OAuth?

No. Checkr connects to FlowRunner with basic authentication (a username and password), no OAuth flow required.

Can Checkr trigger a FlowRunner workflow automatically?

Checkr doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with Checkr

$100 in credits. No card required. Connect in minutes.

Start Building Free Talk to us