TPS and CTPS screening in Zapier.

Two actions

Screen Phone Number

Give it a UK number (any common format; it is normalised to E.164) and an optional campaign reference. It returns:

• Status: clean, tps-listed, ctps-listed or unknown, plus a plain-English label.
• Safe to Call: true only for a clean verdict, so a single Filter or Path step is enough to gate the call.
• Checked At and an Audit Record ID you can write back to the record: the evidence you want if the ICO ever asks.

Add Number to Suppression List

Adds a number to your own do-not-call list. Once it is on there, Screen Phone Number never returns it as safe to call again, whatever the registers say. Wire it to the form, inbox rule or CRM field where "please stop calling me" arrives, and the opt-out is honoured within seconds. Adding to the list does not use a credit.

No trigger, by design. The registers change daily and the DMA standard is screening data no more than 28 days old, so the right pattern is to screen at the moment of use and to re-screen anything older than 28 days before a campaign. A Zapier Schedule trigger feeding Screen Phone Number does the latter.

Set up in five minutes

1. 1. Sign in

   Go to tpsclear.co.uk/account and sign in with a link emailed to your work address. No password, no sales call.

2. 2. Create a test key

   Test keys are free and screen against built-in fixtures, so you can build and test the Zap end to end before spending anything.

3. 3. Connect in Zapier

   Add a TPSClear step to your Zap, paste the key when Zapier asks for it, and map your phone field to Phone Number. Test the step and the status and Safe to Call fields come back.

4. 4. Go live

   Buy a pack, create a live key, and swap it into the Zapier connection. Live keys screen the real TPS and CTPS registers and spend one credit per number.

What it costs

Checks are prepaid. Buy a pack, use it across Zapier, the REST API and anything else that takes a TPSClear key, and buy another when it runs out. Unused credits last 12 months from purchase.

Zapier bills its own tasks separately under your Zapier plan. Need more than 50,000 checks a month, or a signed DPA? Talk to us.

Zaps people build with it

• New lead in Pipedrive, Close or a Google Sheet → Screen Phone Number → write Status and Checked At back to the record, so reps see the verdict before they pick up the phone.
• Call about to be placed from a dialler → screen → Filter on Safe to Call → only clean numbers reach the queue.
• "Do not call me" arrives via Typeform, a shared inbox or a CRM checkbox → Add Number to Suppression List, so the opt-out sticks across every campaign and every tool.
• Monthly Schedule trigger → look up records screened more than 28 days ago → re-screen, so the data behind your next campaign is inside the DMA freshness standard.

Worked example, step by step, in TPS screening in Zapier: screen a number before every call.

Already on HubSpot?

You do not need Zapier for screening inside HubSpot: the native app screens on phone change, in workflows and on a daily backfill under a monthly plan. The API key from the app settings page works in Zapier too, which is useful for tools that sit alongside HubSpot, and those checks count against your plan rather than a prepaid pack.