Skip to content

// automation and data tools

Via API

Make email verification with pingutil

Make scenarios move addresses between forms, sheets and CRMs without checking any of them, so a single bad source fills every downstream tool with bounces. One HTTP Make a request module calling pingutil, plus a Router keyed on status, lets each route handle valid, risky, unknown and invalid differently.

Where it connects: HTTP app, "Make a request" module, followed by a Router

What goes wrong without it

  • The scenario faithfully syncs junk: every fake signup lands in the CRM and the mailing list at the same time.
  • We only find out an address was dead when the campaign report shows the bounce.
  • Our HTTP module keeps timing out on some addresses and the whole bundle errors.

What you can do with Make and pingutil

  • One route per verification status

    Valid bundles create the contact, risky ones get a tag, unknown ones are stored for a re-check, and the fallback route logs invalid addresses with their reason.

  • Fast screening for high-volume sources

    For a busy webhook source, call /v1/lookup with skip_enrichment: true instead. It returns category and verdict.is_spam in milliseconds and catches disposable and machine-generated addresses.

  • Scheduled re-check of unknowns

    A second scenario on a schedule picks up rows tagged for re-check and runs the same HTTP call again, spaced at least an hour apart.

Set it up

  1. 1

    Run your trigger once so Make has a sample bundle with the email field.

  2. 2

    Add HTTP > Make a request with URL https://pingutil.com/v1/verify, method POST and an Authorization header set to Bearer pk_live_... with your key.

  3. 3

    Set the body content type to JSON, use a data structure with one key email mapped to the trigger field, and turn Parse response on.

  4. 4

    In advanced settings set the timeout to 30 seconds and keep "Return error if HTTP request fails" on.

  5. 5

    Add a Router with filters on Data: status equal to valid, risky and unknown, and mark the last route as the fallback.

  6. 6

    Attach an error handler to the HTTP module that stores the bundle as unverified rather than sending it down the valid route.

Make a request: request body (raw JSON string method)
{
  "email": "{{1.email}}"
}

What to do with each result

pingutil resultAction in Make
Data: status = validRoute 1: create or update the contact and continue the flow
Data: status = riskyRoute 2: create the contact with an email_risky tag and Data: reason in a field
Data: status = unknownRoute 3: store with an email_recheck tag for the scheduled scenario
Data: status = invalid (fallback)Fallback route: log to a review sheet, do not add to lists

Limits to plan for

  • Make's HTTP module timeout accepts 1 to 300 seconds; leave about 30 because slow mail servers can take up to about 25.
  • pingutil allows 60 requests a minute and 300 verifications a day (3,000 a month) per account, so throttle large imports or verify them first with the dashboard CSV upload. Those are Free plan limits; Enterprise has custom limits.
  • A bundle that matches no route stops silently, so always define a fallback route.

Make documentation

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

Common questions

Does Make have a built-in email verification module?
No. You call a verification API from the HTTP app and branch on the result with a Router and filters.
Data structure or raw JSON string for the body?
Data structure. Make escapes reserved JSON characters for you, so an address with a quote in it cannot break the request.

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