
Connectors / Human resources · HTTP Connector
Automate Checkr with Tray.ai
Create a candidate, create an invitation and create a report in Checkr, and start a workflow when Checkr sends “Candidate created”.
What can you do with Checkr on Tray.ai?
Checkr runs background checks for employers, including criminal, motor vehicle, identity and verification screenings, with candidate invitations and adverse action handling. Tray.ai connects to Checkr through the HTTP Connector, so your workflows can call the Checkr API alongside the rest of your stack. API access comes through Checkr's partner program or API plan, so you need approved credentials first.
- When Checkr sends “Report completed”, update the candidate's status in your applicant tracking system.
- Create an invitation when a candidate reaches the offer stage in your applicant tracking system.
- When Checkr sends “Invitation expired”, remind the recruiter in your team chat.
- When Checkr sends “Form I-9 completed”, mark the onboarding step done in your HR system.
- Connects through
- HTTP Connector
- Authentication
- Basic authentication
- Base URL
- https://api.checkr.com/v1
Set it up
Connect Checkr to Tray.ai
Each step uses Checkr's own API details, from its documentation.
Step 1
Save Checkr's username and password
Ask Checkr for API access. Once it's approved, save the credentials Checkr gives you as a Tray.ai authentication. The HTTP Client sends them as basic auth. They stay out of the workflow and out of the logs.
Step 2
Point the HTTP Client at the API
Add an HTTP Client step and use https://api.checkr.com/v1 as the base URL. Or paste a cURL example from Checkr's API docs, and Tray.ai fills in the method, URL, and headers.
Step 3
Start with “List candidates”
It's one of 23 documented actions, under Candidates. The response comes back as data the next step can map into your other apps.
Step 4
Start workflows from Checkr events
Give Checkr the URL of a Tray.ai webhook trigger. “Candidate created” can then start a workflow, and so can 7 other events.
Workflows to build with Checkr
Each one uses actions and events from Checkr's own API documentation.
Start a Checkr background check from a Greenhouse offer
When
A candidate reaches the offer stage in Greenhouse
Then
- Create a candidate
- Create an invitation with the right package
With Greenhouse
Update Greenhouse when a Checkr report completes
When
Report completed
Then
- Get a report
- Add the result to the candidate profile in Greenhouse
- Notify the recruiter in Slack
With Greenhouse and Slack
Send completed Checkr I-9 forms to BambooHR
When
Form I-9 completed
Then
- Get a candidate
- Mark the I-9 step done on the employee record in BambooHR
With BambooHR
Apps you can build on Checkr data
Internal tools your team can build with an AI assistant, each one using Checkr calls from its API documentation.
Background check tracker
Shows each candidate with invitation and report status, and lets a recruiter cancel an invitation or send a new one.
Adverse action review queue
Lists suspended or completed reports needing review and lets an HR lead start or cancel an adverse action.
Continuous check roster
Lists workers enrolled in continuous checks and lets a compliance manager add a worker or cancel a check.
Give your AI agents Checkr tools
Build an MCP server on Checkr in Agent Gateway and choose which actions your agents can call. Every call runs with access control and an audit trail. How Agent Gateway works
- List candidates
- List invitations
- Get a report
- List packages
- List continuous checks
- List adverse actions
- Get a candidate
- Create a candidate
What the Checkr API covers
6 resources and 23 documented actions, each one a call the HTTP Connector can make from a Tray.ai workflow. Checkr gives API access on request, so approved credentials come first. Connecting it takes a few clicks: here's how.
Candidates
- List candidates
- Get a candidate
- Create a candidate
- Update a candidate
Invitations
- List invitations
- Get an invitation
- Create an invitation
- Cancel an invitation
Reports
- Get a report
- Create a report
- Update a report
- Complete a report
Packages
- List packages
- Get a package
- Delete a package
Continuous checks
- List continuous checks
- Create a continuous check
- Update a continuous check
- Cancel a continuous check
Adverse actions
- List adverse actions
- Get an adverse action
- Create an adverse action
- Cancel an adverse action
Events Checkr can send to a Tray.ai webhook trigger
- Candidate created
- Invitation completed
- Invitation expired
- Report created
- Report completed
- Report suspended
- Adverse action created
- Form I-9 completed
Checked against Checkr's own documentation on 2026-10-22
How Tray.ai makes this work
Checkr plugs into the whole Tray.ai platform
Intelligent Integration
Integrate and automate across 12,000+ apps, databases, APIs, and services with visual workflows, error handling, and observability.
Learn more →Agent Builder
Build AI agents that read, write, and take action in Checkr — with guardrails, audit, and human-in-the-loop.
Learn more →Agent Gateway for MCP
Expose Checkr actions as governed MCP tools — observable, rate-limited, authenticated.
Learn more →Tray Helix
Build apps on Checkr data with your AI assistant, then deploy, run, and govern them on Tray.ai.
Learn more →More human resources apps on Tray.ai
Dedicated connectors and other apps Tray.ai reaches in the same category. See every human resources connector →
Frequently asked questions
What can a Tray.ai workflow do in Checkr?
+
The Checkr API documents 23 actions across 6 resources (Candidates, Invitations, Reports, Packages, Continuous checks, Adverse actions). For example: List candidates; List invitations; Get a report. A workflow can make any documented call through the HTTP Connector.
How does Tray.ai authenticate with Checkr?
+
The Checkr API uses basic authentication. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.
Which Checkr events can start a Tray.ai workflow?
+
Checkr sends 8 events to a webhook URL, for example: Candidate created; Invitation completed; Invitation expired; Report created; Report completed; Report suspended; Adverse action created; Form I-9 completed. A Tray.ai webhook trigger receives them and starts a workflow.
Do I need special access to the Checkr API?
+
Yes. Checkr gives API access on request, so you need approved credentials before a Tray.ai workflow can call it.
See Checkr working against your stack.
We'll walk through a tailored demo with your systems plugged in.
Thanks — someone from our team will be in touch soon.