Verify emails in Pipedrive

Setup

1. Create an API key at simpleverifier.com/api-keys. It starts with sv_live_. API access comes with selected paid plans; a key on a plan without it gets a 402 that says so.
2. In Pipedrive, add a custom field for people named Email status (Company settings, Data fields, Person). A text field is enough; a single-option field with valid, risky and invalid also works.
3. In Make, Zapier or n8n, start a workflow with Pipedrive's new person trigger and connect your Pipedrive account.
4. Add the SimpleVerifier step exactly as on the Make, Zapier or n8n page here, and map the person's primary email into it.
5. Add Pipedrive's update person action, pick the person ID from the trigger and map status from the SimpleVerifier step into Email status.
6. Turn the workflow on, add a test person with your own address and check that Email status fills in. Then build a Pipedrive filter on Email status is invalid to keep those people out of campaigns.

What people use it for

• Check every person a web form, LeadBooster or an import adds before a rep emails them.
• Keep a Pipedrive filter of invalid addresses so Campaigns and sequences skip them.
• Clean an old Pipedrive database once with a CSV export, then keep it clean with the workflow.

Using the result

Route on the status field: valid means the mail server confirmed the mailbox, risky means delivery could not be confirmed (catch-all domain, role address, provider that hides mailbox status), invalid means it will bounce or is a throwaway address. Keep risky out of cold sequences unless you accept the bounce risk.

Full endpoint reference, error codes and an OpenAPI file are in the API docs. For lists of thousands of addresses, upload a CSV on the verify page instead.

Comparing tools? See email verifiers for Pipedrive compared, with prices checked on each vendor’s site.

Common questions

Which plans include API access for Pipedrive?

API access comes with Pro, Business and Agency, listed on the pricing page; Starter covers CSV verification only. A key on a plan without API access gets a 402 that says so. Each key can make 120 calls a minute.

Is there a SimpleVerifier app in the Pipedrive Marketplace?

Not yet. Today the check runs through Make, Zapier or n8n, which all have Pipedrive triggers and actions, or through a CSV export and re-import.

How do I verify the contacts already in Pipedrive?

Export the people list to CSV, upload it on the verify page, then import the result file back into Pipedrive and match on email to update Email status. The export guide at /verify-export/pipedrive walks through it.

Does it change or delete anything in Pipedrive?

Only what your workflow does. The setup above writes one field on the person; nothing is deleted or merged.