MX Lookup API + Dropbox

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

WhenDropboxNew file
trigger
RunMX Lookup APIReturns the response
action
ThenDropboxUpload file

The MX Lookup API in Dropbox.

Dropbox simplifies file storage and sharing for teams. Connecting APIs to Dropbox enables automated file processing, intelligent organization, and seamless data extraction. Build powerful file-based workflows without manual intervention.

Workflows worth wiring.

Process uploaded receipts through OCR APIs and extract expense data
Automatically convert uploaded images to different formats
Generate reports from API data and distribute via shared Dropbox folders
Create automated photo organization based on image analysis APIs

Ready-made ideas.

New file added to folder Parse file → look up MX records → save report

Look up MX records from uploaded domain lists

When a domain list lands in Dropbox, look up MX records for each domain and save a report with exchange and priority data.

New file added to folder Look up MX records → save results to subfolder

Archive MX lookup results

Process domain lists, look up MX records for each, and save the results with exchange hostnames to a designated Dropbox subfolder.

Connect it in a few steps.

Set up with Zapier
  1. 1
    Set the trigger. Create a Zap with Dropbox as the trigger app and "New file" 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 Dropbox action for "Upload file" 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 Dropbox module set to "New file". 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 Dropbox module for "Upload file". 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 Dropbox trigger node for "New file" 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 Dropbox node for "Upload file" 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 Dropbox receives.

domain"yahoo.com"
mxarray of 3

Dropbox + MX Lookup API FAQ

How do I trigger API calls when files are uploaded to Dropbox?
Use automation platforms with Dropbox triggers. Watch specific folders for new files, then process them through your API workflows.
Can I save API responses as files in Dropbox?
Yes. Generate files (JSON, CSV, PDF, etc.) from API responses in your automation and upload them to specified Dropbox folders.
How do I process large files from Dropbox with APIs?
Download files to the automation platform first. For very large files, consider using APIs that accept file URLs rather than file uploads.

Connect the MX Lookup API to Dropbox. One key, no code, live in minutes.

Scaling up?

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

Contact sales