Skip to content

// automation and data tools

Via API

n8n email verification with pingutil

n8n workflows usually run right after a signup or form submit, which is where disposable, random and role addresses slip into the CRM and Slack alerts. An HTTP Request node calling pingutil gives the next Switch node a category, a spam verdict and, if you want it, a mailbox status to route on.

Where it connects: HTTP Request node (POST), routed with a Switch node

What goes wrong without it

  • Our #new-signups channel is half throwaway inboxes and gibberish addresses.
  • The nightly sync loops over thousands of rows and trips the API rate limit halfway through.
  • Sales gets pinged about gmail.com signups that were never going to buy.

What you can do with n8n and pingutil

  • Route each signup in real time

    Webhook node, then HTTP Request to /v1/lookup with skip_enrichment: true, then a Switch on verdict.is_spam, verdict.low_trust and category to send spam, review and company leads to different places.

  • Verify mailboxes before an import

    Call /v1/verify/batch with up to 50 addresses per request and merge the results back onto your items before they reach the mailing list.

  • Enrich company signups for sales

    Drop skip_enrichment on the company branch and post company.name, company.industry and company.employee_size_estimate to the sales channel.

Set it up

  1. 1

    Create a Header Auth credential with name Authorization and value Bearer pk_live_... so the key stays out of exported workflow JSON.

  2. 2

    Add an HTTP Request node: method POST, URL https://pingutil.com/v1/lookup or /v1/verify, authentication Generic Credential Type then Header Auth.

  3. 3

    Turn on Send Body with JSON and send the body below, mapping the email from the previous node.

  4. 4

    Under Options set Timeout to 30000 ms for /v1/verify, and Batching with 1 item per batch and a 1100 ms interval for bulk runs.

  5. 5

    In node settings set On Error to continue with the error output and wire that output to your unverified path.

  6. 6

    Add a Switch node in Rules mode on verdict.is_spam, verdict.low_trust and category, with a fallback output.

HTTP Request node: JSON body for fast classification
{
  "input": "{{ $json.body.email }}",
  "skip_enrichment": true
}

What to do with each result

pingutil resultAction in n8n
verdict.is_spam = trueSwitch output "spam": flag the user in your database or alert a private channel
verdict.low_trust = trueSwitch output "review": lower-priority queue for info@ and noreply@ style addresses
category = "company"Switch output "company": post to sales or create a CRM lead
status = "invalid" (from /v1/verify)Drop the item before the mailing-list node and log the reason
Error output (429, 5xx, timeout)Treat as unclassified and continue the normal flow

Limits to plan for

  • pingutil allows 60 requests a minute per account plus 2,000 lookups and 300 verified addresses a day (30,000 and 3,000 a month); use Batching for loops. Those are Free plan limits; Enterprise has custom limits.
  • n8n runs after your app accepted the signup, so it can route and flag but cannot block the signup itself.
  • There is no bulk lookup endpoint; only verification has a 50-address batch call.

n8n documentation

n8n is a trademark of its owner. This integration uses n8n's documented extension points; it is not an official n8n app.

Common questions

Should n8n block disposable signups?
No. By the time n8n runs, the account exists. Block synchronously in your signup handler and use n8n for routing, alerts and cleanup.
Does this work on self-hosted n8n?
Yes. It only uses core nodes (Webhook, HTTP Request, Switch), which exist on n8n Cloud and self-hosted installs.

Stop bad addresses in n8n 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 n8n setup will receive.