Address Validation for Dataverse includes two classic workflow steps that verify addresses with PostGrid. Use them to verify addresses in the background, for example when a record is created or updated by an integration or a portal. To use PostGrid from Power Automate instead, see Validate Addresses with Power Automate: PostGrid (Unbound Action).
| Workflow step | PostGrid product | Use for |
|---|
| Verify with PostGrid | US / Canada address verification | Addresses in the United States and Canada |
| Verify with PostGrid International | International address verification | Addresses in every other country |
PostGrid sells these as two separate products with their own results and billing, so they are two steps. Use a condition on the country to send each address to the right step.
Before you start
- An Address Validation license that includes the PostGrid add-on.
- An API Configuration record with Validation Service Type PostGrid API that holds your PostGrid secret key (
live_sk_). The steps run on the server, where a public key is rejected. See Set up your PostGrid API Keys.
Create the workflow
- In the Power Apps Maker Portal, open the solution where you want to include the workflow.
- Select New > Automation > Process > Workflow. Enter a name, select the table where the address columns are located (for example, Contact) and select Create.
- Add a Check Condition that tests whether the country is the United States or Canada (for example, Address 1: Country/Region equals US, USA, United States, CA or Canada).
- In the condition's branch for the US and Canada, select Add Step > Address Validation > Verify with PostGrid. In the Otherwise branch, add Verify with PostGrid International.
- Select Set Properties on each step and fill in the inputs below.
- Add the steps that use the result, for example an Update Record step that writes the verified address when the address is deliverable (see Decide whether to update the record).
- Save and activate the workflow.
| Input | Required | What to enter |
|---|
| API Configuration | Yes | The API Configuration record that holds the PostGrid secret key (for example, PostGrid Verify). |
| Input Street Address | Yes | House number and street. |
| Input Unit Number | Recommended | Apartment, suite or unit. Buildings with several units are only deliverable when the unit is supplied. |
| Input City | Recommended | City. Supply at least the city and state, or the postal code. |
| Input State/Province | Recommended | State, province or region. |
| Input Zip/Postal Code | Optional | ZIP or postal code. |
| Input County | Optional | County. |
| Input Country | Yes | Country name or ISO code (for example US, CA, GB). |
| Include Geocoding (uses an extra lookup) | Optional | No by default. Yes returns latitude and longitude, but uses one extra PostGrid lookup per call. PostGrid must also enable geocoding on your account. |
Outputs
| Output | Description |
|---|
| Result Found | Success whenever PostGrid returned a usable standardized address, including addresses that are correct but not yet deliverable (for example, missing a suite number). Failed only when nothing usable came back. |
| Verification Status | The exact verdict: Verified, Corrected, MissingSecondary, Unverified, Insufficient or Unknown. |
| Missing Components | What is missing, for example Suite identifier. |
| Verification Details | A readable explanation, including PostGrid's corrections. |
| Confidence Level | VERY HIGH, HIGH, MEDIUM or LOW. |
| Street Address, Unit Number, City, State/Province, Zip/Postal Code, County | The standardized address components. |
| Extended Zip/Postal Code | ZIP+4 for US addresses (Verify with PostGrid only). The international product returns the full postal code in Zip/Postal Code. |
| Country | The two-letter ISO country code (for example US), not the country name. |
| Full Address | The complete formatted address. |
| Latitude, Longitude | Only when Include Geocoding is Yes and geocoding is enabled on your PostGrid account. Otherwise 0. |
| Entity Type | RESIDENTIAL or BUSINESS when PostGrid reports it. |
| Verification Status | Result Found | Confidence | Meaning |
|---|
| Verified | Success | VERY HIGH | Deliverable as supplied. |
| Corrected | Success | HIGH | Deliverable after PostGrid corrected it. |
| MissingSecondary | Success | HIGH | The address is correct but needs a unit or suite. Internationally, it was matched but not down to building level. |
| Unverified | Failed | LOW | Could not be matched. |
| Insufficient | Failed | LOW | Not enough input to identify an address. |
Decide whether to update the record
The PostGrid steps do not update any record; your workflow decides what to do with the result. A safe rule is to overwrite the address only when Verification Status is Verified or Corrected. A MissingSecondary result is a good trigger to ask the user for the missing unit, because the rest of the address is already correct. The country is returned as an ISO code (for example US); if you prefer to keep the country name, leave the country column out of the update.
Costs and limits
- Each verification uses one PostGrid lookup, plus one more when geocoding is requested.
- PostGrid limits address requests to 5 per second for your whole organization. Avoid running large numbers of these workflows at the same time.
Troubleshooting
| Symptom | What to check |
|---|
| There is a problem with the product licence. Please contact the administrator. | The Address Validation license has expired or does not include the PostGrid add-on. |
| PostGrid rejected this API key because of its allowed-origins restriction | The API Configuration holds a public key. Use the secret key. |
| HTTP 403 without an origin message | Your PostGrid lookups are used up. Check your balance in the PostGrid dashboard. |
| HTTP 429 | PostGrid's rate limit was reached. Retry later, or run fewer workflows at once. |
| A non-North-American address returns nothing | It was sent to Verify with PostGrid. Check the country condition. |
| No coordinates | Include Geocoding is No, or geocoding is not enabled on your PostGrid account. |