// automation and data tools
Via APIZapier email verification with pingutil
Zaps copy whatever address a form or CRM hands them, so typos, dead mailboxes and temp-mail signups flow straight into your lists and sequences. Add one Webhooks by Zapier POST to pingutil after the trigger and every later step can branch on a real verification status instead of trusting the raw field.
Where it connects: Webhooks by Zapier, POST action (or a Code by Zapier JavaScript step)
What goes wrong without it
- Our Zap pushes every form fill into HubSpot and the sequence, including the asdf@mailinator ones.
- Bounces from leads that came in through Zapier are dragging our sender reputation down.
- Nobody knows which of the contacts a Zap created were ever real, because nothing checked them on the way in.
What you can do with Zapier and pingutil
Gate new leads before the CRM step
Put the verification step between the trigger and "Create contact". Valid leads go through, invalid ones are logged to a sheet, risky ones are created with a tag so sales can decide.
Hold back cold sends to risky addresses
Catch-all domains and role inboxes come back as risky. Route them to a separate Path that adds the contact without enrolling it in an outbound sequence.
Surface typos to a human
When did_you_mean is filled (gmial.com to gmail.com), write the suggestion into a CRM note or a Slack message instead of silently correcting the address.
Set it up
- 1
Create an API key in the pingutil dashboard and keep it ready to paste into a header.
- 2
After your trigger, add a Webhooks by Zapier action with the POST event, URL https://pingutil.com/v1/verify and Payload Type json.
- 3
In Data add one key, email, mapped to the trigger's email field; in Headers add Authorization with the value Bearer pk_live_... and your key.
- 4
Test the step so Status, Reason, Score and Did You Mean become mappable fields.
- 5
Add Paths with one branch each for valid, risky and invalid, plus a fallback branch for unknown and errors.
- 6
Turn the Zap on for new records only, so updates to existing contacts do not re-spend your daily verification budget.
// Input Data: email -> the trigger's email field, key -> your pingutil API key
const controller = new AbortController();
const timer = setTimeout(() => controller.abort(), 25000);
try {
const res = await fetch('https://pingutil.com/v1/verify', {
method: 'POST',
headers: {
Authorization: 'Bearer ' + inputData.key,
'Content-Type': 'application/json',
},
body: JSON.stringify({ email: inputData.email }),
signal: controller.signal,
});
const data = await res.json();
if (!res.ok) {
// 429 rate_limited / quota_exceeded, 401, 5xx: let the lead through as unverified
return { status: 'unverified', reason: data.error || String(res.status) };
}
return {
status: data.status,
reason: data.reason,
score: data.score,
did_you_mean: data.did_you_mean || '',
};
} catch (err) {
return { status: 'unverified', reason: 'timeout_or_network' };
} finally {
clearTimeout(timer);
}What to do with each result
| pingutil result | Action in Zapier |
|---|---|
| status: "valid" | Path to Create or Update Contact and start the sequence |
| status: "risky" (accept_all, role_based, mailbox_full) | Create the contact with an email-risky tag, skip cold outreach |
| status: "invalid" | Skip the CRM step and append the row to a review sheet with the reason |
| status: "unknown" or an error | Fallback Path: tag email-unverified and re-check later |
| did_you_mean not empty | Write the suggestion into a note or Slack message for a person to confirm |
Limits to plan for
- Zapier lists Webhooks by Zapier and Paths as paid-plan features; Code by Zapier runs under plan-dependent time and memory limits.
- pingutil allows 60 requests a minute and 300 verified addresses a day (3,000 a month) per account; a bulk import that fires hundreds of Zap runs will hit 429 errors. Those are Free plan limits; Enterprise has custom limits.
- Most checks take 1 to 5 seconds, a slow mail server up to about 25, and catch-all domains can only ever come back risky.
Zapier documentation
- help.zapier.com/hc/en-us/articles/8496326446989
- help.zapier.com/hc/en-us/articles/8496288555917
- help.zapier.com/hc/en-us/articles/8496310939021
Zapier is a trademark of its owner. This integration uses Zapier's documented extension points; it is not an official Zapier app.
Common questions
- Should I use Webhooks by Zapier or a Code step?
- Webhooks by Zapier is easier to read and maintain. Use a Code step when you want a hard timeout and to turn pingutil errors into an unverified result instead of a failed Zap run.
- Where do I keep the API key in a Code step?
- Map it in as an Input Data value rather than typing it into the code. Use a dedicated pingutil key for Zapier so you can revoke it without touching other systems.
Stop bad addresses in Zapier 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 Zapier setup will receive.