Verify emails in Pipedrive with Spaw

Pipedrive is a sales CRM, and the addresses in it come from web forms, imports and reps typing fast. Spaw does not offer a Pipedrive marketplace app, because a Zap or a Make scenario gives the same result without asking for access to your account: a new-person trigger, a verification step, and an update-person action that writes the verdict to a custom field.

Set up the fields

1. In Pipedrive, add custom fields on the person: a single-option or text field for the verdict, a text field for the reason, and a numeric field for the risk score. Fields on the person rather than the deal keep the verdict attached to the address.
2. Create a secret API key on the API keys page of your Spaw dashboard.

Verify new people as they arrive

1. In Zapier or Make, start the flow with the Pipedrive trigger for a new person.
2. Add the verification step. Until the Spaw apps for Zapier and Make are listed, this is a Webhooks by Zapier POST or a Make HTTP request to https://spaw.co/api/v1/email with the header Authorization: Bearer sk_live_… and this body, mapping the address from the trigger:

{
  "email": "[email protected]"
}

The Zapier page and the Make page show the exact configuration.

3. Add a filter so the flow continues only when the person has an email.
4. Add the Pipedrive action that updates a person, and map the response's data.deliverable, data.reason and data.risk_score into the three custom fields. Zapier presents nested fields with a data prefix; Make shows them under the parsed response.
5. Turn the flow on and test it by creating a person with the address [email protected], which answers a fixed deliverable result at no cost and never appears in your history.

A person can carry more than one email in Pipedrive. Verify the primary one, or add a second verification step for the other addresses if reps rely on them.

Clean the existing database

For people already in Pipedrive, export them to a spreadsheet, and run the email column through a bulk verification on the Spaw dashboard or with the bulk endpoint. The result CSV keeps your original columns and adds the verdict, so it imports straight back with the person id as the match key. Rows that answer undeliverable are added to your suppression list automatically, and later batch and bulk runs answer them without a probe. The list cleaning checklist explains what to do with each group.

What to do with the verdict

Use the verdict field in Pipedrive filters and automations. A deliverable person is ready for sequences. A risky person needs a glance at the reason: catch_all means the company's mail server accepts every address, so the mailbox is unconfirmed but often real, role means a shared inbox such as sales@, and disposable means a throwaway domain. An undeliverable person should not enter a sequence; when the response's data.did_you_mean is filled, the address was a near miss and the suggested spelling can be written back as a note for the rep. risk_score is a 0 to 100 sum of published weights for teams that prefer one threshold.

Cost

Each new person that answers deliverable or risky spends 1 credit; undeliverable answers and repeats within seven days are free. Zapier and Make count their own tasks or operations. A bulk run bills each row the same way as it is processed, and duplicates inside the file are verified once.