Copilot + StackGo

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

Copilot publishes 45 trigger events and 24 actions on its public Zapier listing. That is what a StackGo connector would be built on.

Project management System of record Not connected yet

Also listed under Practice management

Request this integration Book a demo

What Copilot is

Create a client portal to combine messaging, payments, and other modules to offer clients a branded, streamlined experience.

Description supplied by Copilot.

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.

Client Custom Fields Updated
Client Updated
Company Custom Fields Updated
Client Activated
Client Created

The write-back

What StackGo puts back on the record

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

Create Client
Create Company
Update Internal User
Create File Channel

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

Everything else Copilot publishes

Copilot’s public integration surface

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

11 more events

Company Created
Contract Signed
Contract Requested
File Created
File Deleted
File Updated
Folder Created
Folder Deleted
Folder Updated
Form Response Completed
Internal User Created

12 more actions

Create App Connection
Update Client
Update Company
Create Contract
Create File
Create Folder
Update Folder Permissions
Update Root Folder Permissions
Request Form Responses
Create Invoice
Create Link
Create Message Channel

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

Questions

Common questions about Copilot

Is Copilot integrated with OneDrive?

There is no StackGo connector for Copilot yet. Copilot publishes 45 trigger events and 24 actions through Zapier, including “Client Custom Fields Updated”, so building one is realistic. Requests decide the build order.

What is replacing Teams?

Create a client portal to combine messaging, payments, and other modules to offer clients a branded, streamlined experience.

Which Copilot events can start a compliance check?

“Client Custom Fields Updated”, “Client Updated”, “Company Custom Fields Updated”, “Client Activated”. These are Copilot’s own trigger names from its public Zapier listing. StackGo does not connect to Copilot yet, so they show where a connector would start.