Vitally + StackGo

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

Vitally publishes 14 trigger events and 13 actions on its public Zapier listing. That is what a StackGo connector would be built on.

CRM System of record Not connected yet
What Vitally is

Vitally is a customer success platform for high-growth B2B SaaS teams.

Description supplied by Vitally.

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.

  • Customer Created
  • New Active Indicator at Customer
  • Organization Created
  • Customer Entered Segment
  • Customer Exited Segment
The write-back

What StackGo puts back on the record

A Vitally 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 Vitally
  • Add Customer to Segment
  • Create Task
  • Update Customer Traits
  • Update Organization Traits

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

Everything else Vitally publishes

Vitally’s public integration surface

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

9 more events
  • Custom Object Instance Created
  • Custom Object Instance Updated
  • Indicator Instance No Longer Active
  • Note Created
  • NPS Response Created
  • Project Created
  • Project Status Changed
  • Task Created
  • Task Completed
9 more actions
  • Create a Custom Object Instance
  • Create Message
  • Create Note
  • Create NPS Response
  • Create Project From Template
  • Create Track
  • Update a Custom Object Instance Traits
  • Update Project Status
  • Update User Traits

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

Questions

Common questions about Vitally

What does "vitally" mean?

Vitally is a customer success platform for high-growth B2B SaaS teams.

What are the three types of integrations?

There is no StackGo connector for Vitally yet. Vitally publishes 14 trigger events and 13 actions through Zapier, including “Customer Created”, so building one is realistic. Requests decide the build order.

Which Vitally events can start a compliance check?

“Customer Created”, “New Active Indicator at Customer”, “Organization Created”, “Customer Entered Segment”. These are Vitally’s own trigger names from its public Zapier listing. StackGo does not connect to Vitally yet, so they show where a connector would start.

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

Where this sits

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

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

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