DNS Lookup API + Airtable

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

WhenAirtableNew record
trigger
RunDNS Lookup APIReturns the response
action
ThenAirtableCreate record

The DNS Lookup API in Airtable.

Airtable combines the simplicity of a spreadsheet with the power of a database. Integrating APIs with Airtable unlocks automated data enrichment, real-time validation, and dynamic record updates. Build sophisticated data workflows without writing complex database queries.

Workflows worth wiring.

Validate and enrich new contact records automatically when added to your CRM base
Create an automated content calendar that fetches trending topics and keywords
Build an inventory tracker that updates product data from external APIs
Monitor competitor websites and log changes to an Airtable base automatically

Ready-made ideas.

New record created Lookup DNS → populate DNS fields

Enrich domain records with DNS data

When a domain record is created in Airtable, fetch its A records, MX records, and TXT records and store them in dedicated fields.

Record updated Lookup DNS → update MX and TXT fields

Verify mail server config for domains

When a domain is edited, re-query its records.MX and records.TXT to verify mail server configuration is still correct.

Connect it in a few steps.

Set up with Zapier
  1. 1
    Set the trigger. Create a Zap with Airtable as the trigger app and "New record" as the event. Connect your account.
  2. 2
    Add the API action. Add APIVerve as the action, select the DNS Lookup API, and map your trigger data to the request.
  3. 3
    Send it back. Add a second Airtable action for "Create record" 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 Airtable module set to "New record". Authenticate your account.
  2. 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. 3
    Parse & map. Add a JSON module to read the response, then a Airtable module for "Create record". 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 Airtable trigger node for "New record" and connect your credentials.
  2. 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. 3
    Map with expressions. Add a Airtable node for "Create record" 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 Airtable receives.

domain"myspace.com"
recordsA, MX, NS, SOA, TXT

Airtable + DNS Lookup API FAQ

Can Airtable handle real-time API data?
Yes. Using automation platforms, you can trigger API calls on record creation or updates. Airtable also has built-in automations that can work with webhooks for near real-time data.
How do I prevent duplicate records when using APIs?
Use a "Find Record" step before creating new records. Check for existing entries by a unique field (like email or ID), then update if found or create if not.
What's the best way to handle API errors in Airtable workflows?
Set up error handling paths in Make or Zapier. Log failed API calls to a separate "Errors" table in Airtable for review and retry.

Connect the DNS Lookup API to Airtable. One key, no code, live in minutes.

Scaling up?

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

Contact sales