Connecting HubSpot
Overview. Connect HubSpot to IdentityCheck once, and IdentityCheck adds KYC (and, for Tranche 2, AML) command and status properties to your contacts. Set the command property to start on a contact and IdentityCheck emails them a verification link and writes the result straight back onto the contact. HubSpot is a real-time connection, so checks fire as soon as you act. On a HubSpot company you can also run a business (KYB) check and CreditorWatch reports, with the report saved to HubSpot Files.
How the connection works
The HubSpot integration is one of our out-of-the-box integrations, so it is available on every tier, including the free plan. Only custom integrations require a paid tier.
You connect HubSpot to IdentityCheck through a secure authorisation, so you never share your password. Once connected, IdentityCheck adds a small set of custom contact properties: a KYC Command and a KYC Status, plus an AML Command and AML Status if you use the Tranche 2 risk-assessment flow. These properties are created for you automatically the first time each feature is enabled, and only ever once, so you will not end up with duplicates.
Unlike the scheduled integrations, HubSpot is real time. When a staff member sets a command property, IdentityCheck acts on it straight away rather than waiting for an hourly sync. Your team works entirely in HubSpot, and IdentityCheck starts the check, emails the contact and writes results back onto the same contact record.
You connect and manage HubSpot from your Integrations settings in the app.
Setting up the trigger (KYC Command and AML Command)
The command property is the switch that tells IdentityCheck to act on a contact.
- KYC Command starts a plain identity (KYC) check. Set it to start on a contact, and IdentityCheck emails that contact a verification link and sets KYC Status to Started. When the contact finishes, the identity decision writes back.
- AML Command starts a full Tranche 2 risk assessment: the consent, intake, biometric and risk-assessment journey. This only works once the account-level Tranche 2 flow is switched on. See Setting up your Tranche 2 compliance flow.
The command property is a trigger only. IdentityCheck reads it to know it should start a check; it never writes results into the command property. Results go to the separate status and result properties.
If you need to stop a check that is already under way, set the command to Terminate. That ends the in-flight verification and posts a note so there is a record of the change.
What gets written back to the contact
Once a check runs, IdentityCheck writes the outcome onto the HubSpot contact so your CRM stays current.
- For a KYC check: the identity decision and status are written back onto the contact.
- For a Tranche 2 (AML) check: when the assessment completes, five properties are written back: Risk Rating, RA Completed Date, RA Completed By, Risk Assessment Link and AML Status. The AML Status tracks the assessment through Started, Awaiting risk assessment, and Completed or Failed.
Because the result lives on the contact record in HubSpot, your evidence sits in the CRM you already use.
Checking a business through HubSpot (KYB)
HubSpot is the one place in IdentityCheck where you can run a business (KYB) check rather than verifying an individual. It works on a HubSpot company record, not a contact.
Set the company's KYB command to start, and IdentityCheck runs the business check, generates a PDF report, uploads it to HubSpot Files, and writes the report link back onto the company. You open the report from the link, and the PDF is saved in HubSpot so you have a copy for your records.
KYB Command, our business KYB and UBO capability, is available on paid plans only, on any tier, and is set up on request. To switch it on, raise a support ticket with StackGo and we enable it for your account.
This is a deliberately narrow capability. Business checking runs through HubSpot KYB and the CreditorWatch reports below. Individual-level PEP and sanctions screening still happens on the person, through the normal KYC and Tranche 2 contact flow. For what a business check does and does not cover, see Business and entity checks (KYB).
Running CreditorWatch reports from a HubSpot company
If your account has CreditorWatch enabled, you can trigger a company credit report, credit score, ASIC report or UBO (KYB/UBO) report from a HubSpot company record, and set up credit risk monitoring and alerts. IdentityCheck runs the check, uploads the report PDF to HubSpot Files, and writes the link and score back onto the company.
These reports are part of KYB Command, so, like the KYB check, they are a paid-plan feature (any tier) enabled on request via a support ticket. Once enabled, CreditorWatch reports are delivered into HubSpot, where the report link and score land, so run these checks from the company records you keep in HubSpot.
Frequently asked
How do I start a check from inside HubSpot? On the contact, set the KYC Command property to start (or the AML Command property to start for a Tranche 2 risk assessment). IdentityCheck emails the contact a verification link and updates the status property. The HubSpot connection is real time, so the check fires as soon as you set the command.
Where do the results appear on the contact? On the contact's HubSpot properties. A KYC check writes the identity decision and status back. A completed Tranche 2 assessment writes back five properties: Risk Rating, RA Completed Date, RA Completed By, Risk Assessment Link and AML Status.
Can I verify a business, not just a person, through HubSpot? Yes, in a narrow way. On a HubSpot company you can run a business (KYB) check and CreditorWatch reports. IdentityCheck generates the report PDF, saves it to HubSpot Files and writes the link back onto the company. Person-level PEP and sanctions screening still runs on individual contacts.
How do I stop a check I started by mistake? Set the command property to Terminate on the contact. That ends the in-flight verification and posts a note recording the change. Terminate applies to a check that is still under way; a check that has already completed has its result written back as normal.