Clubworx + StackGo

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

Clubworx publishes 8 trigger events and 7 actions on its public Zapier listing. That is what a StackGo connector would be built on.

CRM System of record Not connected yet

Request this integration Book a demo

What Clubworx is

Clubworx is a gym management application.

Description supplied by Clubworx.

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.

New Member
New Non-Attending Contact
New Prospect

The write-back

What StackGo puts back on the record

A Clubworx 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 Clubworx

Add Membership to Member
Create Member
Create Non-Attending Contact

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

Everything else Clubworx publishes

Clubworx’s public integration surface

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

5 more events

Member Archived
Non-Attending Contact Archived
Prospect Archived
New Task
Task Updated

4 more actions

Create Prospect
Update Member
Update Non-Attending Contact
Update Prospect

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

Questions

Common questions about Clubworx

What is Clubworx used for?

Clubworx is a gym management application.

Which Clubworx events can start a compliance check?

“New Member”, “New Non-Attending Contact”, “New Prospect”. These are Clubworx’s own trigger names from its public Zapier listing. StackGo does not connect to Clubworx yet, so they show where a connector would start.

How would a check result show up in Clubworx?

Through Clubworx’s own write operations: “Add Membership to Member”, “Create Member”, “Create Non-Attending Contact”. You choose which fields are written, and you can also run it one-way, with nothing written back to Clubworx at all.