Skip to content

// automation and data tools

Via API

Power Automate email verification with pingutil

Power Automate flows pull addresses from Microsoft Forms, SharePoint lists and Outlook into Dynamics and Dataverse, with nothing checking whether those mailboxes exist. An HTTP action calling pingutil, a Parse JSON step and a Switch on status let the flow reject, tag or accept each address before it lands.

Where it connects: HTTP action (premium connector) followed by Parse JSON and a Condition or Switch

What goes wrong without it

  • Registrations from our Microsoft Forms event page are full of typos and nobody notices until the reminder bounces.
  • The flow creates Dynamics contacts from any address, so sales chases people who do not exist.
  • We want a check our Power Platform team can own without standing up an Azure Function.

What you can do with Power Automate and pingutil

  • Verify form registrations

    Trigger on a new Microsoft Forms response, verify the address, and write status into the SharePoint list so the event team sees which registrations will bounce.

  • Gate Dataverse or Dynamics contact creation

    Only run "Add a new row" for valid and risky results; send invalid ones to an approval or a Teams message.

  • Flag personal addresses on B2B forms

    Call /v1/lookup with skip_enrichment: true and store category so free webmail leads get a different follow-up.

Set it up

  1. 1

    Add an HTTP action with method POST, URI https://pingutil.com/v1/verify, and headers Authorization: Bearer pk_live_... and Content-Type: application/json.

  2. 2

    Set the body to { "email": "@{triggerBody()?['email']}" }, adjusting the expression to your trigger's email field.

  3. 3

    Add Parse JSON on the HTTP body and paste the schema below.

  4. 4

    Add a Switch on the parsed status with cases valid, risky and invalid and a default case.

  5. 5

    Configure "run after" on a fallback branch so a failed or timed-out HTTP action stores the address as unverified instead of stopping the flow.

  6. 6

    Keep the key in an environment variable or Azure Key Vault reference rather than in the action itself.

Parse JSON schema for the /v1/verify response
{
  "type": "object",
  "properties": {
    "email": { "type": ["string", "null"] },
    "status": { "type": "string" },
    "reason": { "type": "string" },
    "score": { "type": "integer" },
    "did_you_mean": { "type": ["string", "null"] },
    "checks": {
      "type": "object",
      "properties": {
        "disposable": { "type": "boolean" },
        "free_provider": { "type": "boolean" },
        "role_based": { "type": "boolean" },
        "catch_all": { "type": ["boolean", "null"] }
      }
    },
    "cached": { "type": "boolean" }
  }
}

What to do with each result

pingutil resultAction in Power Automate
status = "valid"Switch case: add the Dataverse or Dynamics row
status = "risky"Add the row with an email risk column set to reason
status = "invalid"Skip the row and post the address and reason to a Teams channel
did_you_mean not nullReply to the registrant or flag the item for a human to confirm the fix
HTTP action failed or timed outRun-after branch: store as unverified and re-check later

Limits to plan for

  • The HTTP action is a premium connector, so the flow owner needs a license that includes premium connectors.
  • pingutil allows 60 requests a minute and 300 verified addresses a day (3,000 a month) per account; apply concurrency control on loops. Those are Free plan limits; Enterprise has custom limits.
  • Verification can take up to about 25 seconds on slow mail servers, and catch-all domains only ever come back risky.

Power Automate documentation

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

Common questions

Is there a standard connector for pingutil in Power Automate?
No. You call the API with the HTTP action. A custom connector is possible if many flows need it, but it is not required.
What should the flow do with unknown results?
Keep the record and mark it unverified. Unknown means the mail server did not answer clearly, often greylisting, and a later re-check usually resolves it.

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