MX Lookup API + Microsoft Outlook

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

WhenMicrosoft OutlookNew email
trigger
RunMX Lookup APIReturns the response
action
ThenMicrosoft OutlookSend email

The MX Lookup 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 email received Look up MX records → move to folder

Check sender domains on incoming mail

Look up MX records for the sender's domain on incoming Outlook mail. Move emails from domains with an empty mx array to a review folder.

New contact created Look up MX records → flag if no records

Verify contact domains before saving

When adding a new Outlook contact, look up MX records for their email domain. Flag contacts whose domain has no mx records.

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 MX Lookup 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 domain) 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/mxlookup 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.domain 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/mxlookup 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.domain }}.
  4. 4
    Execute & activate. Execute manually to verify, then activate the workflow for production.

What Microsoft Outlook receives.

domain"yahoo.com"
mxarray of 3

Microsoft Outlook + MX Lookup 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 MX Lookup 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