Resources · Make integration

Checkr Make integrationAutomate Checkr with Make.

Can background checks move forward without anyone copying data by hand? The Checkr Make integration gives you 11 modules: 1 instant trigger, 6 actions and 4 searches. This guide shows recruiters and ops teams how to link the account and build a first working scenario.

Try the Checkr integration on MakeSee the 11 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Checkr Make integration do for your hiring flow?

The Checkr Make integration links your Checkr account to Make, a no-code automation tool. You build a scenario (the automation itself, a chain of bricks called modules) that reacts to Checkr events, creates candidates, sends invitations and reads reports, so the data lands where your team already works.

Invitations sent the moment a hire is confirmed. When your applicant tracker or a form marks someone as selected, Create a Candidate records the person in Checkr and Create a Background Check Invitation sends the request. Nobody retypes the applicant's details.

Reports that reach the right desk. Watch Events wakes the scenario when Checkr sends an invitation or report event. Get a Report then pulls the details, and a later module can post them to a hiring channel or a spreadsheet. Get a Report's ETA fits in the same flow when a manager keeps asking about start dates.

A clean lookup before creating anything. Search Candidates and Search Invitations tell you whether a person already exists, which prevents duplicates when the same applicant comes back through two sources.

One limit to know: Make's own documentation for Checkr is marked as limited, because there is not enough public information about the app. Expect to test each module with real data before trusting it. If a flow gets stuck, the Make troubleshooting guide helps, and the n8n vs Make comparison is there if you also weigh n8n. For a broader look at the tool, read the Make review.

Connect

How do you connect Checkr to Make?

  1. 01

    Add a Checkr module

    In a scenario, click the + and search for Checkr. Pick any of its modules, then click Create a connection. A connection is your Checkr account linked to Make once; every Checkr module in every scenario reuses it afterwards.

  2. 02

    Name the connection

    This step is optional, but a clear name such as “Checkr, HR account” saves confusion later when several people or several Checkr accounts share the same Make organization and pick from the connection list.

  3. 03

    Authorize and save

    Depending on what Checkr asks for, either approve Make on the Checkr page that opens or paste the key Checkr gives you. Then click Save. The module now shows your account, and Make can list the objects it is allowed to read.

First scenario

Your first scenario with Checkr and Make

GoalWhen Checkr sends a report event, Make fetches that report with Get a Report.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the large + in the middle of the editor. This first slot holds the module that starts everything.

  2. 02

    Add Watch Events

    Search for Checkr, choose Watch Events and select the connection you created. This is an instant trigger: Checkr calls Make through a webhook as soon as an invitation or report event happens.

  3. 03

    Chain Get a Report

    Click the + on the right of the trigger and add Get a Report. In its fields, map data from the Watch Events bundle (one item passed between modules) so Make knows which report to read.

  4. 04

    Test with Run once

    Click Run once, then trigger an event on the Checkr side. Open the bubble above each module to read the bundle it received and check that the report details look right.

  5. 05

    Switch the scenario on

    Turn the scenario on. Because Watch Events is instant, the scenario runs when Checkr calls it rather than on the 15-minute default schedule that polling triggers use.

Triggers

What can start a Checkr scenario?

1 module starts a scenario when something happens in Checkr. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Checkr as soon as it happens.

Checkr1Watch Events

Watch Events

Instant trigger

In Make“Triggers when an invitation or report event is sent via API.”

Watch Events starts your scenario whenever Checkr sends an invitation or report event, so the rest of the flow reacts to progress in a background check instead of someone refreshing the dashboard.

How it fires
instant, meaning Checkr calls Make through a webhook as soon as the event happens. There is no polling interval to set.
When to use it
as the first module of any flow that must follow a check, for example alerting a recruiter or fetching a finished report.
Watch out
one scenario receives both invitation and report events, so add a filter after the trigger if only one kind matters to you.
Modules

Every Checkr module in Make

Checkr gives you 10 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Checkr1

Create a Background Check Invitation

Action

In Make“Creates a new background check invitation.”

This module sends a background check invitation from Checkr, which turns a hiring decision into an actual request without opening the Checkr dashboard.

When to use it
right after an offer is accepted in your tracker, paired with the candidate record you just created or found.
Watch out
it acts on one person per run, so check for an existing invitation first with Search Invitations.
Checkr2

Create a Candidate

Action

In Make“Creates a new candidate.”

Create a Candidate adds a new person to Checkr from data that already lives elsewhere, like a form submission or an applicant row, so nobody retypes names and contact details.

When to use it
as the step before an invitation, when the applicant has never been checked through your account.
Watch out
when the same applicant can arrive from two sources, run Search Candidates first so the scenario does not create the person twice.
Checkr3

Get a Candidate

Action

In Make“Returns information about the selected candidate.”

Get a Candidate returns the details of one candidate you already know, which is handy when a later module needs more than the reference an event carries.

When to use it
after Watch Events, to enrich a message to the recruiter with the candidate's information before posting it.
Watch out
it reads a single record; to find someone by name or to list everyone, Search Candidates is the right module.
Checkr4

Get an Invitation

Action

In Make“Returns information about the selected invitation.”

Pulling one invitation back into Make lets you see where a request stands and pass that status to the tools your team reads every day.

When to use it
when an invitation event arrives and you want the full invitation before updating a tracker or a spreadsheet row.
Watch out
it needs a specific invitation; map it from the trigger or from a search instead of typing it in by hand.
Checkr5

Get a Report

Action

In Make“Returns information about the report.”

Get a Report brings the information of a Checkr report into your scenario, so the result of a check can reach a hiring manager, a channel or an HR file.

When to use it
straight after Watch Events reports a report event, as in the first scenario on this page.
Watch out
think about who can read the destination before mapping report details into it, since every later module receives the full bundle.
Checkr6

Get a Report's ETA

Action

In Make“Returns an existing Report ETA.”

Asking Checkr for a report's estimated completion lets a recruiter answer the question every manager asks: when will this check be done?

When to use it
in a flow that updates a start date or tells a hiring manager when to expect results.
Watch out
it reads an ETA that Checkr already holds for an existing report; it does not create or change one, so map the report from an earlier module.
Checkr7

List Nodes

Search

In Make“Lists all nodes.”

List Nodes returns every node of your Checkr account as separate bundles, giving your scenario the list to choose from or to keep in sync elsewhere.

When to use it
when a later step needs one of your nodes, or when you mirror that list into a sheet for reference.
Watch out
as a search, it can output many bundles, and each following module then runs once per node.
Checkr8

List Packages

Search

In Make“Lists all packages.”

With List Packages, your scenario reads all the packages set up in Checkr and gets one bundle per package, which helps when several kinds of checks exist.

When to use it
to let a form or a tracker offer only packages that really exist before an invitation goes out.
Watch out
every package becomes a bundle, so add a filter or an aggregator if the next step should run a single time.
Checkr9

Search Candidates

Search

In Make“Searches for candidates or lists them all.”

Search Candidates finds matching people in Checkr, or lists all of them, which is the safest way to know whether someone is already there.

When to use it
before Create a Candidate, with a filter or a router that only creates the person when the search comes back empty.
Watch out
a search can return zero, one or several bundles; plan for each case, especially several matches.
Checkr10

Search Invitations

Search

In Make“Searches for invitations or lists them all.”

This search looks up invitations or lists every one of them, useful to audit what has been sent and to avoid inviting the same applicant twice.

When to use it
ahead of Create a Background Check Invitation, or when building a status sheet that the HR team checks.
Watch out
listing everything can produce many bundles and many operations, so narrow the search whenever you can.
Need help

Need help automating Checkr with Make?

A person reads every message.

FAQ

Checkr Make integration: common questions

01Is the Checkr Make integration free?
Yes, as far as Make is concerned. Checkr is a standard app, available from the Free plan, which allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. Make counts usage in operations, one per module per bundle. Your Checkr subscription is a separate matter that this page does not cover.
02What do you need to connect Checkr to Make?
A Checkr account and a Make account. Make's documentation lists no specific prerequisite and gives no dedicated connection steps, so the standard flow applies: add a Checkr module, click Create a connection, optionally name it, then either approve Make on the Checkr page or paste the key Checkr provides, and click Save. The connection is stored once and every Checkr module reuses it. Since the documentation is marked as limited, test the connection with a harmless search such as List Packages before building anything that writes data.
03Does the Checkr Make integration react in real time?
Yes. Watch Events is an instant trigger: Checkr calls Make through a webhook as soon as an invitation or report event happens, and the scenario runs at that moment. That is different from scheduled triggers, which Make polls on the scenario's schedule, every 15 minutes by default. Every other Checkr module is an action or a search, so it only runs when something earlier in the scenario reaches it. If you need a periodic check instead, start the scenario from a schedule and use Search Invitations.
04What if a Checkr module you need is missing in Make?
It depends on the gap. The Checkr app in Make has no Make an API Call module, so you cannot reach extra endpoints through it. The 11 modules cover candidates, invitations, reports, report ETAs, nodes and packages. Make also flags its Checkr documentation as limited, which means fewer notes on edge cases than for most apps. If a step is not covered, look at whether another app in your stack can carry that part of the flow, or ask the agency team to review the scenario with you.
05Should you use Make or n8n for Checkr?
It depends on the criteria that matter to your team, and this page does not rank the two. On the Make side, you get 11 Checkr modules, including 1 instant trigger for invitation and report events, a visual editor, and the plan limits described above. The same app often has an n8n node as well, so compare what each tool offers for your exact flow: the events you need, the searches, and how you prefer to build. The n8n vs Make comparison linked in the section above goes through the general differences.
Same platform

Other docs you might need on this stack.

Browse all integrations