Flow + StackGo

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

Flow publishes 4 trigger events and 3 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 Flow is

Flow is a task management solution that offers an online web application, iOS mobile app, and a native Mac OS X application for users.

Description supplied by Flow.

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.

Event	What StackGo does	What comes back
An item moves to an onboarding stage	Starts the compliance workflow	Status on the item
A client card is created	Sends a verification request	Verification status

The write-back

What StackGo puts back on the record

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

How it lands in Flow

Create Task

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

Everything else Flow publishes

Flow’s public integration surface

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

4 events

Completed Task
New Project
New Task
New Team

2 more actions

List of Accounts
List of Sections

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

Questions

Common questions about Flow

What is an integration flow?

There is no StackGo connector for Flow yet. Flow publishes 4 trigger events and 3 actions through Zapier, so building one is realistic. Requests decide the build order.

How would a check result show up in Flow?

Through Flow’s own write operations: “Create Task”. You choose which fields are written, and you can also run it one-way, with nothing written back to Flow at all.