Skip to content

// crm

Via API

Salesforce email verification with pingutil

Salesforce stores whatever address a web form, import or rep typed, so reps sequence dead mailboxes and Gmail signups sit next to real buyers. A record-triggered flow with an HTTP Callout action sends each new lead to pingutil and writes the verification status, email category and company industry back to the Lead, so assignment rules and list views can act on them.

Where it connects: Record-triggered flow on Lead (created), Run Asynchronously path with an HTTP Callout action through a named credential

What goes wrong without it

  • Our reps keep sequencing leads that bounce on the first touch, and nobody knows the address was dead until the bounce report.
  • Half the web-to-lead records are Gmail and Yahoo addresses, and they get routed to account executives like enterprise buyers.
  • Reps spend the first ten minutes on every lead looking up who the company is and how big it is.

What you can do with Salesforce and pingutil

  • Verify every new lead before it is assigned

    The flow writes `status` and `reason` to custom fields on Lead. Assignment rules and list views exclude `invalid`, so reps only see leads that have a working mailbox or an honest `risky` or `unknown` flag.

  • Route work email to sales, personal email to nurture

    A second callout to `/v1/lookup` returns `category`. Leads with `company` go to the sales queue; `free` and `isp` leads go to a marketing nurture queue; `disposable` leads are marked unqualified.

  • Fill company industry and size on arrival

    For `company` domains the lookup returns `company.industry` and `company.employee_size_estimate`. Write them to custom fields so territory and scoring rules work before a rep opens the record.

Set it up

  1. 1

    Create an external credential (Custom protocol) with a named principal that holds your pingutil API key, add an Authorization header of `Bearer ` plus that key, and a named credential `Pingutil` with URL `https://pingutil.com`.

  2. 2

    Grant the running user access to the principal with a permission set.

  3. 3

    Add custom Lead fields: `Email_Verification_Status__c` (picklist: valid, invalid, risky, unknown), `Email_Verification_Reason__c` (text), `Email_Category__c` (text) and `Company_Industry__c` (text).

  4. 4

    Build a record-triggered flow on Lead, created, with a Run Asynchronously path, because the callout cannot run in the same transaction as the save.

  5. 5

    On that path add an Action, choose Create HTTP Callout, select the `Pingutil` named credential, method POST, URL path `/v1/verify`, and paste the sample request `{"email": "jane@example.com"}` and the sample response below. Fields that are usually null, such as `did_you_mean`, carry sample strings so Salesforce can infer their types.

  6. 6

    Add an Update Triggering Record element that maps `status`, `reason` and `did_you_mean` from the callout output to the Lead fields. Repeat with a second callout to `/v1/lookup` for category and company data.

Sample response to paste into the HTTP Callout action for POST /v1/verify
{
  "email": "jane@example.com",
  "input": "jane@example.com",
  "status": "valid",
  "reason": "mailbox_exists",
  "score": 95,
  "did_you_mean": "jane@gmail.com",
  "checks": {
    "syntax": true,
    "disposable": false,
    "free_provider": false,
    "role_based": false,
    "randomized": false,
    "domain_exists": true,
    "has_mx": true,
    "mailbox": "exists",
    "catch_all": false
  },
  "mx_host": "mx.example.com",
  "smtp": { "code": 250, "enhanced": "2.1.5", "message": "OK" },
  "cached": false,
  "checked_at": "2026-11-16T09:00:00.000Z"
}

What to do with each result

pingutil resultAction in Salesforce
`status: "invalid"` (e.g. `mailbox_not_found`)Set Lead Status to Unqualified and keep the lead out of Sales Engagement cadences.
`status: "risky"`, `reason: "accept_all"`Assign normally but flag for low-volume outreach; the domain accepts every address, so the mailbox cannot be confirmed.
`status: "unknown"`Leave the lead active and re-check with a scheduled flow later; greylisting and timeouts are not verdicts.
`category: "free"` or `"isp"` from `/v1/lookup`Route to the nurture queue instead of an account executive.
`category: "company"` with `company.industry`Write industry and `employee_size_estimate` to Lead fields for territory and scoring rules.

Limits to plan for

  • Callouts from a record-triggered flow must run on the Run Asynchronously path, so fields fill a few seconds after the lead is saved, not during the save.
  • Verification can take up to about 25 seconds on slow mail servers. Apex callouts have a 120-second cumulative limit per transaction; for large imports, the batch endpoint (50 addresses per call) from Queueable Apex is a better fit.
  • pingutil allows 60 requests a minute and 300 verified addresses a day (3,000 a month) per account; past the daily budget the API returns `429 quota_exceeded`, so leave those leads blank and let a scheduled flow pick them up after 00:00 UTC. Those are Free plan limits; Enterprise has custom limits.

Common questions

Flow or Apex for Salesforce email verification?
Flow with an HTTP Callout action is enough for leads that arrive one at a time. For imports of hundreds of leads, a trigger that enqueues a Queueable Apex job and calls /v1/verify/batch with 50 addresses per request is more efficient. Our blog post on Salesforce lead email verification walks through the Apex version.
Does verification send an email to the lead?
No. pingutil checks the mailbox with an SMTP RCPT TO conversation and disconnects before any message is sent.
Should the flow delete invalid leads?
No. Mark them unqualified and keep the record, so you can still see which form or list produced bad addresses.

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