HR SoftwareSalesCross-stack blueprint

Automating Checkr + Close CRM Stack Workflows with Make.com

These tools sit in different operational verticals. Instead of a feature matrix, this page maps a production-grade integration path: trigger → Make.com transform → downstream action, with explicit auth at each API node.

Connection endpointscheckr · triggermake · middlewareclose · action

1
The Trigger Event
Checkr
When Checkr emits ‘Report Completed’ via its Webhook Listener, Make.com opens the scenario run. Native trigger catalog for this node:
- Report Completed
- Report Flagged
- Invitation Expired
checkr → make.com payloadwebhook / json
```
{
  "source": "checkr",
  "event": "Report Completed",
  "listener": "webhook",
  "category": "HR Software",
  "auth": "OAuth 2.0"
}
```
Alternate entry points: Report Flagged · Invitation Expired
2
The Middleware Transformation
Make.com
Make.com captures the raw webhook payload, applies router filters on data state (status, adjudication flags, or CRM field presence), then maps JSON objects into the destination schema using native module mappers—no custom ETL service required.
make.com transform mapwebhook / json
```
{
  "middleware": "make.com",
  "filter": { "status": "actionable" },
  "map": {
    "from": "checkr.Report Completed",
    "to": "close.Create Lead"
  },
  "nodes": ["checkr", "make", "close"]
}
```
3
The Downstream Action
Close CRM
Close CRM instantly fires ‘Create Lead’ so the receiving system reflects the upstream event without manual handoff.
- Create Lead
- Update Opportunity
- Send Email
Optional follow-on actions: Update Opportunity · Send Email
4
Security & Authentication Protocol
Connected API nodes authenticate independently. Confirm token scopes and refresh routines before promoting this scenario to production.
Checkr
OAuth 2.0
Make.com
OAuth 2.0 / Token Refresh
Close CRM
API Key Pass-through

View Make.com Checkr review Close CRM review

The Trigger Event

The Middleware Transformation

The Downstream Action

Security & Authentication Protocol