// automation and data tools
Via APIPipedream email verification with pingutil
Pipedream workflows often sit between an HTTP trigger and a CRM, email tool or database, and they pass along whatever email arrived. A short Node.js code step that calls pingutil can export the verdict to later steps and stop the run with $.flow.exit when the address is junk.
Where it connects: Node.js code step in a workflow (defineComponent with run({ steps, $ }))
What goes wrong without it
- Our signup webhook workflow writes every address to the database, including obvious temp-mail ones.
- We want to skip the expensive downstream steps for addresses that will never receive mail.
- The verification call sometimes hangs and the whole workflow hits its execution timeout.
What you can do with Pipedream and pingutil
Stop junk before downstream steps
Call /v1/lookup with skip_enrichment: true and end the workflow with $.flow.exit when verdict.is_spam is true, so no CRM or email step runs for that event.
Verify, then branch
Call /v1/verify, export status and reason, and use them in later steps to decide between creating the contact, tagging it, or logging it.
Enrich work-email signups
For category company, a full lookup adds company.name, company.industry and company.headquarters to the payload you forward to the CRM.
Set it up
- 1
Add an environment variable PINGUTIL_KEY in your Pipedream project settings with your pingutil API key.
- 2
Add a Node.js code step after the trigger and paste the code below.
- 3
Point the email lookup at the field your trigger provides (for an HTTP trigger, steps.trigger.event.body).
- 4
Use the exported status, reason and category in later steps, or let the step end the run for spam.
- 5
If you call /v1/verify on an HTTP-triggered workflow, raise the workflow timeout above the 30 second default.
export default defineComponent({
async run({ steps, $ }) {
const email = steps.trigger.event.body?.email;
if (!email) return $.flow.exit('no email in payload');
let data = null;
try {
const res = await fetch('https://pingutil.com/v1/lookup', {
method: 'POST',
headers: {
Authorization: 'Bearer ' + process.env.PINGUTIL_KEY,
'Content-Type': 'application/json',
},
body: JSON.stringify({ input: email, skip_enrichment: true }),
signal: AbortSignal.timeout(5000),
});
if (res.ok) data = await res.json();
} catch (err) {
// timeout or network error: fail open
}
if (!data) {
$.export('category', 'unchecked');
return { email, checked: false };
}
$.export('category', data.category);
$.export('reason', data.verdict.reason);
if (data.verdict.is_spam) {
return $.flow.exit('blocked: ' + data.verdict.reason);
}
return { email, checked: true, low_trust: data.verdict.low_trust };
},
});What to do with each result
| pingutil result | Action in Pipedream |
|---|---|
| verdict.is_spam = true | return $.flow.exit() so no later step runs |
| verdict.low_trust = true | Continue but pass a review flag to the CRM step |
| category = "company" | Run a full lookup and forward company fields to the CRM |
| Error, 429 or timeout | Export category "unchecked" and continue the workflow |
Limits to plan for
- Pipedream defaults HTTP-triggered workflows to a 30 second execution timeout; /v1/verify can take up to about 25 seconds on slow mail servers.
- pingutil allows 60 requests a minute and 2,000 lookups and 300 verified addresses a day (30,000 and 3,000 a month) per account. Those are Free plan limits; Enterprise has custom limits.
- Blocklists lag behind brand-new disposable domains, so a clean verdict means "not known to be bad".
Pipedream documentation
Pipedream is a trademark of its owner. This integration uses Pipedream's documented extension points; it is not an official Pipedream app.
Common questions
- Why use $.flow.exit instead of throwing an error?
- An exit ends the run cleanly without marking it as failed, which keeps your error alerts for real failures.
- Can the step verify the mailbox instead?
- Yes. Change the URL to /v1/verify, send { email }, read status and reason, and allow a longer timeout of around 25 seconds.
Stop bad addresses in Pipedream 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 Pipedream setup will receive.