Validate Addresses with Power Automate: Smarty (Unbound Action)

Overview

Address Validation for Dataverse exposes Smarty address verification as two Dataverse unbound actions. Power Automate can call them with the standard Microsoft Dataverse connector and its Perform an unbound action step:

Smarty sells these as two separate products with their own results and subscriptions. They are therefore two actions, not one action with a country switch, so a flow never silently changes which product it uses. The example flow in this article routes each contact to the right action based on its country.

Both actions return a standardized address, a precise verification status and a list of missing components. They do not update any record. Your flow decides whether the result is good enough to write back.

Address autocomplete is not available as a Power Automate action: Smarty's terms allow US Address Autocomplete only for people typing in a form. Use the verification actions for automated validation.

[Screenshot placeholder: overview of the example flow.]

Before you start

• Address Validation for Dataverse is installed in a version that includes the Smarty actions (sharpxrm_VerifyWithSmarty appears in the Action Name list).
• A valid Address Validation license that includes the Smarty add-on. Without a valid license, the actions return ResultFound = Failed with the message There is a problem with the product licence. Please contact the administrator.
• A Smarty subscription for US Address Verification, International Address Verification, or both.
• An active API Configuration row with Validation Service Type = Smarty Api that holds your Smarty secret key, entered as your Auth ID, a colon, then your Auth Token. The actions run on the server, where an embedded key is refused. If you also use the Smarty autocomplete control, create two API Configuration rows: one with the embedded key for the control (for example Smarty Autocomplete), and one with the secret key for verification (for example Smarty Verify). See Set up your Smarty API Keys.
• A Microsoft Dataverse connection in Power Automate.

Cost: Smarty bills per lookup. Each verification uses one lookup from the US or the international subscription.

How the example flow works

1. When a row is selected (Contacts): users run the flow from the Flow menu on a contact.
2. Get contact (Get a row by ID): reads the Address 1 columns.
3. Get Smarty configuration (List rows) and Configuration found (Condition with a Terminate in the False branch).
4. Is US address (Condition): sends US addresses to sharpxrm_VerifyWithSmarty and everything else to sharpxrm_VerifyWithSmartyInternational.
5. Smarty result (Compose): merges the output of whichever action ran, so later steps have a single place to read from.
6. Is deliverable match (Condition): overwrites Address 1 only when Smarty confirms the address is deliverable.

Find the API Configuration

Use List rows on APIs Configuration to find the secret-key record by name:

[Screenshot placeholder: List rows action that finds the Smarty Verify API Configuration.]

Route by country

The Is US address condition compares this expression with true:

contains(createArray('', 'US', 'USA', 'UNITED STATES', 'UNITED STATES OF AMERICA'), toUpper(trim(coalesce(outputs('Get_contact')?['body/address1_country'], ''))))

Add any other spellings your data uses. In this example, contacts with no country go to the US action, because the international action requires a country. If most of your addresses are outside the United States, remove '' from the list and handle missing countries separately.

[Screenshot placeholder: the Is US address condition.]

Call the unbound actions

In each branch, add Microsoft Dataverse > Perform an unbound action. Choose sharpxrm_VerifyWithSmarty in the True branch and sharpxrm_VerifyWithSmartyInternational in the False branch. Both actions take the same inputs, except that only the international action has IncludeGeocoding. The API Configuration input lists every column of that table; only the ID field needs a value.

[Screenshot placeholder: Perform an unbound action configured for sharpxrm_VerifyWithSmarty.]

[Screenshot placeholder: Perform an unbound action configured for sharpxrm_VerifyWithSmartyInternational.]

Input fields

A transaction log is written only when Save Transaction Logs is enabled on the API Configuration row.

Output values

Example result

Verifying 780 Greenwich St, New York, NY with sharpxrm_VerifyWithSmarty returns (abridged):

{ "ResultFound": "Success", "VerificationStatus": "MissingSecondary", "MissingComponents": "Secondary number (apartment, suite, etc.)", "Confidence": "HIGH", "StreetAddress": "780 Greenwich St", "City": "New York", "State": "NY", "ZipPostalCode": "10014", "ExtendedZipPostalCode": "5919", "County": "New York", "Country": "US", "EntityType": "RESIDENTIAL" }

Merge the result and decide whether to update

Add a Compose action named Smarty result after the condition, set to run after both branches, with this expression:

coalesce(outputs('Verify_with_Smarty')?['body'], outputs('Verify_with_Smarty_International')?['body'])

Then add an Is deliverable match condition that checks whether outputs('Smarty_result')?['VerificationStatus'] is Verified or Corrected, and update the contact's Address 1 columns only in its True branch. A MissingSecondary result is a good trigger to ask for the missing unit, because the rest of the address is already correct.

[Screenshot placeholder: Compose action that merges the two Smarty outputs, and the Is deliverable match condition.]

Troubleshooting