TPSClear for Pipedrive is in build. The Pipedrive Marketplace listing is in development; in the meantime the integration runs against Pipedrive's public API and webhooks, which means the architecture you read about here is the architecture that will ship. Nothing material changes when we go from API integration to listed app, except that you will install it from a button instead of from us.

Honest status: not yet on the Pipedrive Marketplace. We are running pilot installs by hand for waitlist customers while the listing is reviewed.

People and Organisations: where verdicts live

Pipedrive's data model is mercifully simple. Phone numbers live on People (with multiple labelled values per person) and on Organisations (typically a switchboard). TPSClear writes a verdict to both:

People. Every labelled phone value (Work, Mobile, Home, Other, plus your custom labels) gets its own status. The rolled-up combined status sits on the Person itself for filter and list-view use.
Organisations. The organisation phone gets a status, separate from the verdicts on the contacts associated with it.

Custom fields auto-created on install

The integration creates the following custom fields on first run, so you do not have to set them up by hand:

Field	Object	Type
TPSClear status	Person, Organisation	Single option
TPS register match	Person, Organisation	Yes / No
CTPS register match	Person, Organisation	Yes / No
Last screened	Person, Organisation	Date / time

Webhook re-screen on phone change

The integration registers Pipedrive webhooks on person.change and organization.change. When a phone field changes, TPSClear screens the new value within a few seconds and updates the matching custom field. There is no nightly sync to wait for, no manual button to press; the rep types the new number, switches to the next deal, and by the time they look at the record again the verdict is there.

For backfills (the day you turn it on, or after a CSV import), the integration walks Persons and Organisations in chunks and rate-limits itself against your Pipedrive plan's API allowance.

Pipedrive Automations: the bit reps actually use

Pipedrive's native Automations is where the integration earns its keep. The TPSClear status field is a normal custom field, which means you can build automations like:

When a Person is created and TPSClear status = TPS or CTPS or Both, move the Deal to a "Compliance review" stage.
When phone changes on a Person whose Deal is in an outbound-only pipeline, schedule an activity for a rep to review the new verdict before calling.
When status changes from Clean to anything else, notify the deal owner.

These are configured by you in Pipedrive's UI, against the fields we provision. We do not ship our own workflow engine; Automations is already the right tool.

Screenshot: Person record in Pipedrive with the TPSClear custom fields populated and a recent activity from the webhook re-screen.

For UK SMEs and outbound-led teams

Pipedrive's UK installed base is heavy on outbound SDR teams, agency-style sales operations, and SaaS sales orgs that picked Pipedrive over HubSpot specifically because they are dialling-led. Those are exactly the teams the ICO is most likely to hear about, because they are the ones making the most calls per day. A sensible TPS posture is not optional for that profile, and building it yourself is rarely the right call when a turnkey integration is on the marketplace.

What you can do today

Join the waitlist and we will install the integration into your Pipedrive account during the pilot.
If you cannot wait, the API can be driven from a Pipedrive Automation that sends a webhook to your backend, which then updates the custom field. Crude, but it works today.
Read about how often you should re-screen if you are unsure how aggressive your cadence should be.