Twenty + StackGo
Run compliance from inside Twenty. Checks start from a record and the result lands back on the client.
Twenty publishes 1 trigger event and 3 actions on its public Zapier listing. That is what a StackGo connector would be built on.
Twenty is a modern Open-Source CRM platform.
Description supplied by Twenty.
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.
| Event | What StackGo does | What comes back |
|---|---|---|
| A deal or opportunity is won | Starts intake and runs identity | Status on the contact |
| A contact is created | Sends a branded verification request | Verification status |
| Contact details change | Re-screens against sanctions and PEP lists | Updated status, alert if changed |
What StackGo puts back on the record
A Twenty connector would write named fields onto the record, not a link to a portal. These are the fields StackGo writes 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)
Every field is optional. What each one holds, and which carry personal data, is set out once in what “integrates with” actually means.
Twenty’s public integration surface
The rest of what Twenty exposes on Zapier, beyond the workflow. This is the raw material a connector would use.
- Record Trigger
- Create, Update or Delete Record
- Find objects
- List Record Ids.
Names are Twenty’s own, read from its public Zapier listing on 28 August 2026.
Twenty is made by twenty.com. We are not affiliated with them.
Want Twenty connected?
Requests decide the build order. Tell us and we will tell you where it sits.
Request this integrationReady 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.