Boon + StackGo

Run compliance from inside Boon. Checks start from a record and the result lands back on the client.

Boon publishes 5 trigger events and 0 actions on its public Zapier listing. That is what a StackGo connector would be built on.

HR & payroll System of record Not connected yet

Also listed under Client onboarding

Request this integration Book a demo

What Boon is

Boon is a social recruiting network that lets businesses engage and hire the right candidates faster through intelligent social referrals.

Description supplied by Boon.

The trigger

What starts a check

You do not open StackGo. A change in the system starts the work, and the system stays your source of truth.

Opportunity Application Status Change
New Opportunity Application
New Opportunity Posted

The write-back

What StackGo puts back on the record

A Boon connector would write the outcome, the status and a link to the result onto the record by default. These are the fields StackGo can write on the systems it connects to today.

Verification status
Risk rating
Last checked
Report link
Verified name
Date of birth
Document checked
Screening result
Beneficial owners
Form responses
Verification report (PDF)

Personal fields are off by default. What goes back to your CRM explains the default; what each field holds is set out in what “integrates with” actually means.

Everything else Boon publishes

Boon’s public integration surface

The rest of what Boon exposes on Zapier, beyond the ones above. This is the raw material a connector would use.

2 more events

New Message Received
Accepted Referral

Names are Boon’s own, read from its public Zapier listing on 23 October 2026.

Questions

Common questions about Boon

Which Boon events can start a compliance check?

“Opportunity Application Status Change”, “New Opportunity Application”, “New Opportunity Posted”. These are Boon’s own trigger names from its public Zapier listing. StackGo does not connect to Boon yet, so they show where a connector would start.