// sales engagement and cold email
Via automationQuickMail email verification with pingutil
Many QuickMail teams feed prospects in from a CRM, a sheet or a lead source through Zapier. Put a pingutil check in the middle of that Zap: verify the address, filter on the status, and only then run QuickMail's Create or Update Prospect action.
Where it connects: Zapier, QuickMail "Create or Update Prospect" action after a Webhooks by Zapier POST to pingutil and a Filter step
What goes wrong without it
- Our Zap pushes every new row from the sheet into QuickMail, typos and dead addresses included.
- We send from a pool of inboxes and do not want any of them to collect bounces.
- We would rather not write and host code just to check emails.
What you can do with QuickMail and pingutil
Verify new leads from a sheet or CRM
Trigger on a new row or contact, call pingutil with Webhooks by Zapier, and continue only when status is valid.
Send catch-all prospects to a different campaign
Use Paths by Zapier: valid prospects to the main campaign, accept_all ones to a cautious campaign.
Write the result back to the source
Add a step that updates the sheet row or CRM record with status and reason, so the list owner sees why a lead was skipped.
Set it up
- 1
In QuickMail, generate a Zapier API key under Settings, Add-ons, and connect QuickMail in Zapier.
- 2
Create a Zap with your trigger (new sheet row, new CRM contact, new form entry).
- 3
Add a Webhooks by Zapier POST step to https://pingutil.com/v1/verify with the JSON body and Authorization header shown below.
- 4
Add a Filter (or Paths) step on the returned status: continue when it equals valid.
- 5
Add QuickMail's Create or Update Prospect action and choose the campaign.
- 6
Optionally, add a step to write status and reason back to the trigger record.
{
"method": "POST",
"url": "https://pingutil.com/v1/verify",
"headers": {
"Authorization": "Bearer pk_live_your_key",
"Content-Type": "application/json"
},
"data": {
"email": "{{email from the trigger step}}"
},
"filter_step": "Only continue if status (Text) exactly matches valid",
"paths_option": {
"path_a": "status exactly matches valid -> QuickMail Create or Update Prospect, main campaign",
"path_b": "reason exactly matches accept_all -> QuickMail Create or Update Prospect, catch-all campaign"
}
}What to do with each result
| pingutil result | Action in QuickMail |
|---|---|
| status: valid | Continue to Create or Update Prospect in the main campaign. |
| status: invalid | Stop the Zap and write the reason back to the source record. |
| status: risky, reason: accept_all | Send down a separate path to a lower-volume campaign, or stop. |
| status: unknown, or the webhook step errors | Stop and flag the record for a later check; do not create the prospect blind. |
Limits to plan for
- QuickMail's plan pages have changed over time; check which current plans include the Zapier integration and API key.
- Verification of one address can take several seconds; Webhooks by Zapier waits for the response, and each step counts as a Zapier task.
- pingutil verifies 300 addresses per account per day (3,000 a month), which caps how many Zap runs can be checked per day. Those are Free plan limits; Enterprise has custom limits.
QuickMail documentation
QuickMail is a trademark of its owner. This integration uses QuickMail's documented extension points; it is not an official QuickMail app.
Common questions
- Is there a direct QuickMail and pingutil integration?
- No. The connection runs through Zapier: a webhook step calls pingutil and QuickMail's own Zapier action creates the prospect.
- Can I use Make or n8n instead?
- Yes, if your QuickMail setup is reachable there. The pattern is the same: an HTTP request to pingutil, a filter on status, then the step that creates the prospect.
Stop bad addresses in QuickMail today
Sign in with your email, create an API key and paste it into the step above. Test on a few real addresses first: the live demo shows exactly what your QuickMail setup will receive.