MX Lookup API + Discord Integration

Why connect them

The MX Lookup API in Discord.

Discord powers communities worldwide with real-time communication. Connecting APIs to Discord enables automated notifications, bot-powered data lookups, and intelligent alerts. Keep your community informed with timely, relevant information.

What you can build

Workflows worth wiring.

Post automated alerts when cryptocurrency prices hit certain thresholds

Create a bot that looks up weather data when users request it

Send notifications when new content is published on monitored websites

Alert moderators when potentially problematic content is detected

Templates

Ready-made ideas.

New message with domain Look up MX records → reply with results

Look up MX records via bot command

Build a Discord bot that looks up MX records for any domain users submit. Reply with the domain, exchange hostnames, and priority values.

Domain submitted for review Look up MX records → post warning if empty

Alert on domains without mail servers

When a domain is submitted for review, check its MX records and post a warning in a mod channel if the mx array is empty.

Setup

Connect it in a few steps.

Set up with Zapier

1
Set the trigger. Create a Zap with Discord as the trigger app and "New message" as the event. Connect your account.
2
Add the API action. Add APIVerve as the action, select the MX Lookup API, and map your trigger data to the request.
3
Send it back. Add a second Discord action for "Send message" and map the returned fields (like domain) into it.
4
Test & turn on. Test the Zap with real data to confirm the mapping, then turn it on.

Set up with Make

1
Add the trigger. Create a scenario and add a Discord module set to "New message". Authenticate your account.
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
Parse & map. Add a JSON module to read the response, then a Discord module for "Send message". Map fields like data.domain into place.
4
Activate. Run once to confirm the mapping, then switch the scenario on and set its schedule.

Set up with n8n

1
Add the trigger node. Start a workflow with a Discord trigger node for "New message" and connect your credentials.
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
Map with expressions. Add a Discord node for "Send message" and reference the response with expressions such as {{ $json.data.domain }}.
4
Execute & activate. Execute manually to verify, then activate the workflow for production.

The payload

What Discord receives.

domain"yahoo.com"

mxarray of 3

MX Lookup API + Discord