CRM

Sansan + StackGo

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

Sansan publishes 4 trigger events and 1 action on its public Zapier listing. That is what a StackGo connector would be built on.

CRM System of record Not connected yet

Also listed under Client onboarding

What Sansan is

Sansan is a cloud based contact management system. Digitize your business cards with 99.9% accuracy and share the contact information with your colleagues. Save time and increase your business opportunities.

Description supplied by Sansan.

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.

EventWhat StackGo doesWhat comes back
A deal or opportunity is wonStarts intake and runs identityStatus on the contact
A contact is createdSends a branded verification requestVerification status
Contact details changeRe-screens against sanctions and PEP listsUpdated status, alert if changed
The write-back

What StackGo puts back on the record

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

Everything else Sansan publishes

Sansan’s public integration surface

The rest of what Sansan exposes on Zapier, beyond the workflow. This is the raw material a connector would use.

4 events
  • Legacy New Business Card
  • New Business Card
  • New Business Card From You
  • New Business Card From Anywhere in Your Team
1 action
  • Find Tags

Names are Sansan’s own, read from its public Zapier listing on 28 August 2026.

Where this sits

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

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

If you use Sansan, you probably also use

Want Sansan 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.