Ashby + StackGo

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

Ashby publishes 11 trigger events and 8 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 Ashby is

Ashby's all-in-one recruiting software consolidates your ATS, Analytics, Scheduling, and CRM.

Description supplied by Ashby.

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.

Candidate Applied
Candidate Hired

The write-back

What StackGo puts back on the record

A Ashby 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.

How it lands in Ashby

Create Candidate Note
Change Job Consideration Stage
Consider Candidate for Job

Ashby's own write operations. The result goes onto the record you already work in.

Everything else Ashby publishes

Ashby’s public integration surface

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

9 more events

Application Changed Stage
Interview Schedule Created
Interview Schedule Updated
Job Posting Published
Job Posting Unpublished
Offer Created
Offer Deleted
Offer Updated
Opening Created

5 more actions

Create Candidate
Create Opening
Generate Report on Ashby
Update Candidate
Update Opening

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

Questions

Common questions about Ashby

Does Ashby integrate with ADP?

There is no StackGo connector for Ashby yet. Ashby publishes 11 trigger events and 8 actions through Zapier, including “Candidate Applied”, so building one is realistic. Requests decide the build order.

Which Ashby events can start a compliance check?

“Candidate Applied”, “Candidate Hired”. These are Ashby’s own trigger names from its public Zapier listing. StackGo does not connect to Ashby yet, so they show where a connector would start.

How would a check result show up in Ashby?

Through Ashby’s own write operations: “Create Candidate Note”, “Change Job Consideration Stage”, “Consider Candidate for Job”. You choose which fields are written, and you can also run it one-way, with nothing written back to Ashby at all.