Odoo + StackGo

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

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

CRM System of record Not connected yet

Request this integration Book a demo

What Odoo is

Odoo is a powerful open source platform with dozens of apps to help you grow your business. Available apps range from CRM to eCommerce, and from accounting to manufacturing and project management. This Odoo CRM integration allows users to connect Odoo's CRM product to other apps. This integration works with instances that are cloud hosted at "odoo.com."

Description supplied by Odoo.

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.

Contact
New Lead

The write-back

What StackGo puts back on the record

A Odoo 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 Odoo publishes

Odoo’s public integration surface

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

2 actions

Create Lead
Find Contact

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

Questions

Common questions about Odoo

Which Odoo events can start a compliance check?

“Contact”, “New Lead”. These are Odoo’s own trigger names from its public Zapier listing. StackGo does not connect to Odoo yet, so they show where a connector would start.