Project management

Cor + StackGo

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

Cor publishes 14 trigger events and 16 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

What Cor is

COR is the all-in-one management solution for creative agencies that automate timesheets, through AI, to predict profitability, reduce work overload and improve client engagements.

Description supplied by Cor.

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.

  • Create Client
The write-back

What StackGo puts back on the record

A Cor 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 Cor
  • Create Client
  • Create Task

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

Everything else Cor publishes

Cor’s public integration surface

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

13 more events
  • Create Brand
  • Create Hour
  • Create Invoice
  • Create Product
  • Create Project
  • Create Task
  • Create User
  • Delete Brand
  • Delete Client
  • Delete Hour
  • Delete Product
  • Delete Project
  • Delete User
14 more actions
  • Create Fee
  • Create Hour
  • Create Invoice
  • Create Project
  • Create Quickbooks Invoice
  • Delete Client
  • Delete Hour
  • Delete Project
  • Update Client
  • Update Project
  • Create Quickbooks Expense
  • Update Task
  • Fetch Brands
  • Fetch Clients

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

Questions

Common questions about Cor

How would a check result show up in Cor?

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

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

Where this sits

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

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

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