TPSClear for Zoho CRM is in build. The Zoho Marketplace listing is being prepared, and the integration is being designed against Zoho CRM's standard Lead and Contact modules with a Deluge-friendly custom function for re-screen. Zoho is a high-priority target on this roadmap because of how much UK SME outbound runs on it, particularly in agency, training, and price-sensitive verticals.

Honest status: not yet on the Zoho Marketplace. The integration is being piloted with waitlist customers using a connected-app install while the listing is reviewed.

Modules covered

Leads. Verdict on the Lead at insert and on phone change, before any auto-assignment workflow that might dial.
Contacts. Status on the Contact, with the rolled-up value mirrored to the linked Account where applicable.
Accounts (optional). If your org keeps a switchboard phone on Account, we screen it as a separate field.

Auto-created custom fields

On first run, the integration provisions these fields under the TPSClear_ prefix so they cannot collide with anything you already have:

TPSClear_Status (picklist: Clean, TPS, CTPS, Both, Unscreened)
TPSClear_TPS_Match (boolean)
TPSClear_CTPS_Match (boolean)
TPSClear_Last_Checked (datetime)

Two screening patterns: Workflow Rule or Deluge

Zoho admins are split between people who live in the Workflow Rules UI and people who happily write Deluge. The integration is designed to support both.

Workflow Rule. The default install creates a Workflow Rule on Lead and Contact that fires on Create or Edit when a phone field changes, and calls the TPSClear API via a webhook action. The verdict is written back by a Deluge custom function that the rule invokes.
Deluge custom function. The same custom function can be invoked directly from any Deluge script: a button on a related list, a scheduled function for monthly re-validation, a mass-action handler. The function takes a record ID and a phone field name, calls the API, and writes the verdict back. Useful when you have outgrown the standard Workflow Rule.

Zoho Flow connector

For orgs that have standardised on Zoho Flow rather than Workflow Rules, we publish a Zoho Flow connector with the same actions: screen a number, screen a record, fetch a verdict. That lets you build cross-app flows like "new Lead from Forms, screen against TPS, then create or skip a Bigin pipeline entry depending on the verdict" without writing Deluge.

Cost-conscious SMEs: why this matters here

Zoho's positioning is unapologetically price-led. Customers buying Zoho CRM are typically buying it because it costs a fraction of Salesforce or HubSpot Sales Hub at comparable functional depth. That same cost discipline is why the existing TPS app on the HubSpot marketplace, at over £3,500 a year, is not viable for most Zoho teams. TPSClear's free tier and £29 Starter plan are deliberately priced to be installable on a Zoho budget without a procurement conversation.

The other thing UK Zoho teams notice quickly is that Zoho's own data centre is in the EU but the TPS register is a UK-specific legal artefact. There is no built-in TPS check in Zoho, and there will not be one, because TPS is a UK regulator concern. That is precisely the gap TPSClear fills.

Screenshot: Lead detail in Zoho CRM with the TPSClear custom fields populated and the related-list timeline showing the latest screen event.

What you can do today

Join the waitlist; we will pilot the connected-app install on your org while the marketplace listing finishes review.
Or call the TPSClear API from a Deluge function today. The function we ship in the marketplace app is a thin wrapper around the same endpoint.
Background reading: PECR explained covers the regulation that drives this whole product.