// crm
Via APIMicrosoft Dynamics 365 Sales email verification with pingutil
Dynamics 365 Sales leads come from marketing forms, list imports and integrations, and bad addresses only show up when Customer Insights journeys or sellers' emails bounce. A Power Automate cloud flow triggers when a lead row is added, calls pingutil with the HTTP action, and writes the verification status, email category and company industry back with Update a row.
Where it connects: Power Automate cloud flow with the Dataverse trigger "When a row is added, modified or deleted" (Lead, Added), an HTTP action and an "Update a row" action
What goes wrong without it
- Imported lead lists in Dynamics are full of addresses that bounce on the first journey email.
- Sellers qualify leads by hand because nothing tells them whether it is a work or personal address.
- Industry is empty on most leads, so our routing rules fall back to round robin.
What you can do with Microsoft Dynamics 365 Sales and pingutil
Verify new leads
Write `status` and `reason` to custom columns on Lead. Views and journey segments exclude `invalid`.
Route by email type
A second HTTP action calls `/v1/lookup`. Use `category` in assignment rules: `company` to sellers, `free` and `isp` to a nurture team.
Fill industry and size
Copy `company.industry` and `company.employee_size_estimate` to text columns for routing and scoring.
Set it up
- 1
Add text columns to the Lead table, for example `new_emailstatus`, `new_emailreason`, `new_emailcategory` and `new_companyindustry`.
- 2
Create an automated cloud flow with the Microsoft Dataverse trigger "When a row is added, modified or deleted", change type Added, table Leads, scope Organization.
- 3
Add an HTTP action configured like the snippet below (in code view), with the pingutil key stored in an environment variable or secret, not typed into the action.
- 4
Set the HTTP action's Configure run after so the flow continues when the call fails or times out, then add a condition on the status code.
- 5
Add Update a row (table Leads, row ID from the trigger's `leadid`) and map `body('Verify_email')?['status']` and the other fields to your columns.
- 6
Repeat with a second HTTP action to `/v1/lookup` with body `{"input": ...}` for category and company data.
{
"Verify_email": {
"type": "Http",
"inputs": {
"method": "POST",
"uri": "https://pingutil.com/v1/verify",
"headers": {
"Authorization": "Bearer @{parameters('PingutilApiKey')}",
"Content-Type": "application/json"
},
"body": {
"email": "@{triggerOutputs()?['body/emailaddress1']}"
}
},
"runAfter": {}
}
}What to do with each result
| pingutil result | Action in Microsoft Dynamics 365 Sales |
|---|---|
| `status: "invalid"` | Set the lead to Disqualified (or a custom reason) and exclude it from journeys. |
| `status: "risky"`, `reason: "accept_all"` | Keep qualified but flag for low-volume email. |
| `status: "unknown"` | Re-check later with a scheduled flow. |
| `category: "company"` with `company.*` | Write industry and size columns and route to sellers. |
| `category: "free"` or `"isp"` | Route to nurture. |
Limits to plan for
- The Dataverse connector and the HTTP action are premium in Power Automate, so the flow owner needs a license that includes premium connectors.
- Every action counts toward Power Platform request limits; a bulk lead import runs the flow once per row.
- pingutil allows 60 requests a minute and 300 verified addresses a day (3,000 a month) per account. For big imports, verify the list first in batches of 50 with `/v1/verify/batch`. Those are Free plan limits; Enterprise has custom limits.
Microsoft Dynamics 365 Sales documentation
- learn.microsoft.com/en-us/power-automate/dataverse/create-update-delete-trigger
- learn.microsoft.com/en-us/power-automate/limits-and-config
- learn.microsoft.com/en-us/connectors/connector-reference/connector-reference-premium-connectors
Microsoft Dynamics 365 Sales is a trademark of its owner. This integration uses Microsoft Dynamics 365 Sales's documented extension points; it is not an official Microsoft Dynamics 365 Sales app.
Common questions
- Can I use a plug-in instead of Power Automate?
- Yes. An asynchronous plug-in registered on Lead create can call pingutil and update the row. Power Automate is easier to maintain for most teams, so we show that route here.
- Does the flow slow down lead creation?
- No. Cloud flows run after the row is saved, so the lead is created immediately and the columns fill a few seconds later.
Stop bad addresses in Microsoft Dynamics 365 Sales 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 Microsoft Dynamics 365 Sales setup will receive.