Workable + StackGo

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

Workable publishes 3 trigger events and 5 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

What Workable is

Workable is a beautifully simple tool that helps you advertise jobs, screen candidates and accelerate your company's hiring process.

Description supplied by Workable.

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.

  • Updated Candidate Stage
  • New Candidate
  • New Disqualified Candidate
The write-back

What StackGo puts back on the record

A Workable 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 Workable
  • Add Comment Candidate
  • Add Tag to Candidate

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

Everything else Workable publishes

Workable’s public integration surface

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

3 more actions
  • Create Candidate
  • Move Candidate Stage
  • Create Requisition

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

Questions

Common questions about Workable

Which Workable events can start a compliance check?

“Updated Candidate Stage”, “New Candidate”, “New Disqualified Candidate”. These are Workable’s own trigger names from its public Zapier listing. StackGo does not connect to Workable yet, so they show where a connector would start.

How would a check result show up in Workable?

Through Workable’s own write operations: “Add Comment Candidate”, “Add Tag to Candidate”. You choose which fields are written, and you can also run it one-way, with nothing written back to Workable at all.

Questions taken from what people actually search in Australia. We answer only the ones our own data answers.

Where this sits

Workable is the record. StackGo runs the steps around it.

Every step writes back to Workable, so the client record stays the source of truth.

Want Workable connected?

Requests decide the build order. Tell us and we will tell you where it sits.

Request this integration

Ready to make onboarding minutes, not hours?

Start free and run your first check today, or book a demo and we will walk you through it.

Cookie settings

Choose which optional cookies we can use. You can change this at any time from Cookie settings at the bottom of every page.