Verify the emails of your Pipedrive people

The Pipedrive connector checks the addresses in your CRM where they already live. Choose all your people or a filter: every primary address goes through the YesWeCheck engine, SMTP included, then its verdict, score and reason are written on the record. Your sales team and your campaigns rely on addresses that exist.

How it works

  1. Connect the tool

    Paste an API key into your customer area. It is tested on the spot, then stored encrypted.

  2. Choose a list

    A list, a segment or the whole account. Contacts are checked by the batch processing engine, SMTP included.

  3. Find the verdict in the tool

    Status, score, reason and date are written on each contact. Segment, exclude, send.

What is written in Pipedrive

Four custom fields on the person record, created on the first clean. They work straight away in your Pipedrive filters, views and automations.

YesWeCheck fields written on each Pipedrive person.
FieldContent
YWC statusValid, Risky, Invalid or Unknown
YWC scoreScore from 0 to 100
YWC reasonReason: catch-all, disposable, mailbox does not exist, domain without a mail server, typo…
YWC last checkDate of the check

Understand the score and the four statuses

You stay in control

Spot the invalid addresses

A dedicated red label flags invalid people, without removing their other labels.

Check every new person

Every person created, across the whole CRM or in a watched filter, is checked within minutes, with a daily cap that you set.

Check one contact

An address entered from your customer area is checked and its verdict written on the Pipedrive record.

Your API quota preserved

Only records whose verdict changes are rewritten, and headroom always remains for your other tools.

Nothing is deleted

The connector writes fields. Deleting a person or changing their follow up remains your decision.

Security and credits

The Pipedrive API token is tested when you connect, then stored encrypted; it is never displayed again and disconnecting erases it. A clean costs the credits of batch processing: one credit per address checked with SMTP, except when the result is undetermined.

See batch processing

Frequently asked questions

How do I verify the emails of my Pipedrive people?
Copy your API token in Pipedrive (Personal preferences, API tab), paste it into your YesWeCheck account, choose all your people or a filter, then start the clean. The result is written on each record.
Which fields are added to my Pipedrive people?
Four custom fields: the status (valid, risky, invalid or unknown), the score from 0 to 100, the reason and the date of the check. They are created automatically on the first clean.
A person has several addresses: which one is checked?
Their primary address. One person means one check and one credit at most, and the verdict written on the record concerns the address you use for your sends.
How do I set invalid addresses aside in Pipedrive?
Create a people filter on the YesWeCheck status and use it in your views, automations and campaigns. You can also give invalid people a dedicated red label, without touching their other labels.
Can new people be checked automatically?
Yes. Watch all new people, or only those in a filter: each one is checked within minutes of being created, with a daily cap that you set to keep control of your credits.
Does the connector use up my Pipedrive API quota?
It spares it: only records whose verdict changes are rewritten, and it always leaves headroom for your other tools.
How many credits does a clean use?
One credit per address checked with SMTP, except when the result is undetermined. Duplicates and people without an address are neither checked nor charged.

Get started

Create an account, connect Pipedrive and run a first clean on a filter of a few people.