Why connect themThe DNS Lookup API in Slack.
Slack is where work happens for millions of teams. Integrating APIs with Slack enables intelligent notifications, automated alerts, and data-rich messages. Transform your channels into real-time dashboards and keep your team informed with contextual, actionable information.
What you can buildWorkflows worth wiring.
Send instant alerts when a monitored website's SSL certificate is expiring
Post daily weather forecasts to team channels for field workers
Notify sales teams when a lead's email is validated as deliverable
Alert DevOps when DNS changes are detected on critical domains
TemplatesReady-made ideas.
Scheduled hourly Lookup DNS → post alert if records missingAlert on DNS lookup failures
Periodically check critical domains and post a Slack alert if records.A is empty or records.MX is missing, indicating a possible outage.
Scheduled daily Lookup DNS → post summary to channelPost daily DNS summary for monitored domains
Query DNS for your monitored domains and post a daily digest to Slack with each domain's A records, nameservers, and MX configuration.
SetupConnect it in a few steps.
Set up with Zapier
- 1
Set the trigger. Create a Zap with Slack 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 DNS Lookup API, and map your trigger data to the request.
- 3
Send it back. Add a second Slack 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 Slack module set to "New message". Authenticate your account.
- 2
Call the API. Add an HTTP module pointing at api.apiverve.com/v1/dnslookup 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 Slack 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 Slack trigger node for "New message" and connect your credentials.
- 2
Add an HTTP Request node. Point it at api.apiverve.com/v1/dnslookup using Header Auth (x-api-key). Feed in the trigger data.
- 3
Map with expressions. Add a Slack 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 payloadWhat Slack receives.
domain"google.com"
recordsA, AAAA, CNAME, MX, NS, PTR, SRV, SOA, TXT, CAA
ttlA, AAAA, CNAME, MX, NS, PTR, SRV, SOA, TXT, CAA
summaryhasIPv6, hasMailServers, hasSPF
