Other integrations at a glance
Overview. Alongside Xero Practice Manager, HubSpot and Karbon, IdentityCheck connects to FYI, Zendesk Sell, Pipedrive, Monday and Clio. In each one you start a check from a field, action or panel on the client, and the status writes back automatically. Two of them, FYI and Zendesk Sell, run on an hourly sync, so treat those as automatic rather than instant. Monday is the exception on results: it receives status columns only, not the full result set. These are all out-of-the-box integrations, so they are available on every tier, including the free plan.
FYI
FYI is a scheduled (hourly) integration. You tick a KYC command field (or the AML command field for a Tranche 2 risk assessment) on an FYI entity or client. On its next sync, a background job sends the client the verification link and sets the status to Started, and it can verify the entity's related contacts as well.
Because FYI polls on an hourly cycle, a check is sent on the next sync rather than the instant you tick the box. For a completed Tranche 2 assessment, FYI receives the full result set written back onto the client, the same fields XPM and HubSpot get.
Zendesk Sell
Zendesk Sell is also a scheduled (hourly) integration, and it covers plain identity (KYC) checks. You set a KYC command field to true on a contact; a background job then starts a KYC verification, emails the contact the link, and updates the KYC status field on the contact.
As with FYI, treat this as automatic but not instant: the job runs on its hourly cycle, so allow up to an hour for the check to go out and the status to update.
Pipedrive
Pipedrive works in real time. An IdentityCheck panel on a person record triggers a KYC verification, and the status writes back onto the Pipedrive person. As part of this, the contact is enrolled in ongoing PEP and sanctions monitoring, so the person keeps being screened after the initial check rather than only once.
Monday
Monday connects via a secure authorisation (OAuth). You pick the boards you want to use and map the columns, and IdentityCheck provisions the columns it needs: KYC Command, KYC Status and Verification Link, plus Risk Assessment columns for Tranche 2. Flipping KYC Command to Start sends the verification and writes progress, the decision and the risk rating back to the board.
Monday has one important limit on results. For a Tranche 2 risk assessment, its write-back is status columns only: a Risk Assessment Status and the Risk Assessment rating (High, Medium or Low). It does not receive the risk-assessment link, the completed date, the completed-by name or an AML Status field, and there is no clickable link to the full assessment on the board. If you need those, use XPM, HubSpot or FYI. See Understanding write-back for the full comparison.
Clio
Clio connects via a secure authorisation (OAuth). IdentityCheck adds an IdentityCheck Verification custom action to the Clio contact, along with a KYC status field and a verification-link field. Invoking the custom action on a contact starts a verification and writes the status and link back onto that contact, all from inside Clio.
Don't see the system you use?
The integrations above are the ones available out of the box, but the list keeps growing. If the system your firm works in is not here, tell us: raise a support ticket describing the platform you use and how you would like to trigger checks and receive results, and we can look at building it as a custom integration.
Frequently asked
How do I start a check in FYI or Zendesk Sell? In both, you tick or set a command field on the client or contact. A background job then sends the verification link and updates the status field. Both run on an hourly sync rather than in real time, so treat them as automatic but not instant, and allow up to an hour.
What does Monday write back? For a Tranche 2 risk assessment, Monday receives status columns only: a Risk Assessment Status and the Risk Assessment rating (High, Medium or Low). It does not receive the risk-assessment link, the completed date, the completed-by name or an AML Status field. Plain KYC status and the verification link are written back to the board as well.
How is a check started in Clio and Pipedrive? In Clio, IdentityCheck adds an IdentityCheck Verification custom action plus status and link fields to the contact; running the action starts a check and writes the status and link back. In Pipedrive, an IdentityCheck panel on a person triggers the check, and the status writes back onto that person.
Which of these are instant and which are on a sync? FYI and Zendesk Sell run on an hourly background sync, so a check goes out on the next cycle, allow up to an hour. Pipedrive, Monday and Clio act in real time when you trigger the check. Either way, nobody has to copy results between systems; the status writes back on its own.