Street Address Parser API + Microsoft Outlook

Send the response straight into Microsoft Outlook — connected through Zapier, Make, or n8n, no code required.

WhenMicrosoft OutlookNew email
trigger
RunStreet Address Parser APIReturns the response
action
ThenMicrosoft OutlookSend email

The Street Address Parser API in Microsoft Outlook.

Microsoft Outlook powers enterprise email worldwide. Connecting APIs to Outlook enables automated email processing, intelligent categorization, and seamless data extraction. Enhance your enterprise email workflows with external intelligence.

Workflows worth wiring.

Validate sender addresses to identify potential phishing attempts
Extract and process data from structured email formats
Auto-categorize emails based on content analysis
Enrich calendar events with location and weather data

Ready-made ideas.

New address submitted Fetch parsed address → send email

Send parsed address confirmations

Parse a submitted address and send an Outlook email with the streetNumber, cityName, stateName, and zipCode for confirmation.

New address submitted Fetch parsed address → send email if incomplete

Alert on incomplete address submissions

Send an Outlook alert when a parsed address is missing key components like zipCode or stateName for review.

Connect it in a few steps.

Set up with Zapier
  1. 1
    Set the trigger. Create a Zap with Microsoft Outlook as the trigger app and "New email" as the event. Connect your account.
  2. 2
    Add the API action. Add APIVerve as the action, select the Street Address Parser API, and map your trigger data to the request.
  3. 3
    Send it back. Add a second Microsoft Outlook action for "Send email" and map the returned fields (like address) into it.
  4. 4
    Test & turn on. Test the Zap with real data to confirm the mapping, then turn it on.
Set up with Make
  1. 1
    Add the trigger. Create a scenario and add a Microsoft Outlook module set to "New email". Authenticate your account.
  2. 2
    Call the API. Add an HTTP module pointing at api.apiverve.com/v1/streetaddressparser with your x-api-key header. Pass the trigger's data as the input.
  3. 3
    Parse & map. Add a JSON module to read the response, then a Microsoft Outlook module for "Send email". Map fields like data.address into place.
  4. 4
    Activate. Run once to confirm the mapping, then switch the scenario on and set its schedule.
Set up with n8n
  1. 1
    Add the trigger node. Start a workflow with a Microsoft Outlook trigger node for "New email" and connect your credentials.
  2. 2
    Add an HTTP Request node. Point it at api.apiverve.com/v1/streetaddressparser using Header Auth (x-api-key). Feed in the trigger data.
  3. 3
    Map with expressions. Add a Microsoft Outlook node for "Send email" and reference the response with expressions such as {{ $json.data.address }}.
  4. 4
    Execute & activate. Execute manually to verify, then activate the workflow for production.

What Microsoft Outlook receives.

address"1600 Amphitheatre Parkway, Mountain View, CA 90210"
parsedstreetNumber, streetType, streetAddress, cityName, stateName, zipCode

Microsoft Outlook + Street Address Parser API FAQ

How do I automate Outlook with external APIs?
Use automation platforms with Microsoft 365 triggers. Process emails, call external APIs, and create responses, tasks, or calendar events based on the results.
Can I use APIs to enhance Outlook calendar events?
Yes. Trigger on new calendar events, extract location data, call APIs for weather or travel information, and update event descriptions with the details.
How do I validate email addresses in Outlook workflows?
Extract addresses from emails or contacts, send them to validation APIs, and tag or categorize based on validity and deliverability scores.

Connect the Street Address Parser API to Microsoft Outlook. One key, no code, live in minutes.

Scaling up?

Volume pricing, custom SLAs, and dedicated support for high-traffic teams.

Contact sales