Resources · Make integration

DataForSEO Domain Analytics API Make integrationAutomate DataForSEO Domain Analytics API with Make.

Need to know what a domain runs on before you reply to a lead? The DataForSEO Domain Analytics API Make integration gives you 8 action modules, all started by another app or a schedule. This guide links your account and walks you through a first working scenario.

Try the DataForSEO Domain Analytics API integration on MakeSee the 8 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the DataForSEO Domain Analytics API Make integration do for you?

The DataForSEO Domain Analytics API Make integration lets a Make scenario (the automation you build in Make, a chain of modules) ask DataForSEO about domains and technologies, then pass the answer to your other tools. A module is one brick of that chain, and each one here is an action: it runs when something upstream hands it a domain or a query.

Enrich inbound leads. A form or CRM brings in a company website, and Get live domain technologies fetches the technologies DataForSEO associates with that domain, so sales sees the stack before the first call. Add Get a live domain Whois overview when registration details matter too.

Build a prospect list from a technology. Get domains by technology starts from a tool instead of a domain and returns sites DataForSEO links to it. That suits an agency hunting for sites on the platform it specializes in. Get domains by HTML terms does the same from a snippet of page code.

Track a market. Get live technology stats and Get live aggregation technologies are, by their names, meant for figures across many domains rather than one. Send the results to a sheet to watch how a technology spreads.

What the integration does not do: it has no trigger, so it never starts a scenario by itself, and the Make documentation for this app is marked as AI generated, so check key details against DataForSEO before you rely on them. For a broader view of the tool, read our Make review; if you also weigh the other platform, the n8n vs Make comparison lays out the criteria.

Connect

How do you connect your DataForSEO account to Make?

  1. 01

    Grab your API credentials

    You need an active DataForSEO account with API access. Open your account dashboard, go to the API access section and copy the login and the password displayed there. Make asks for those two values, not for anything else.

  2. 02

    Add a module and open the connection form

    In your scenario, add any DataForSEO Domain Analytics API module and click Create a connection. A connection is your DataForSEO account linked to Make once, then reused by all 8 modules of this app.

  3. 03

    Name it and paste the credentials

    The Connection name field is optional, but a clear name helps when you run several accounts. Paste the login and password you copied, save, and Make can now call DataForSEO on your behalf.

First scenario

Your first scenario: profile every new lead's website

GoalWhen a new lead with a website lands in the app you already use, Make asks DataForSEO which technologies run on that domain and who registered it.

  1. 01

    Create the scenario and pick a starting point

    From the Scenarios page, create a new scenario and click the +. Since DataForSEO has no trigger, choose the module of the app where your leads arrive, such as your form or CRM.

  2. 02

    Add Get live domain technologies

    Click the + on the right of that first module, search for DataForSEO Domain Analytics API and pick Get live domain technologies. Create the connection if it is your first module of this app.

  3. 03

    Map the lead's domain

    In the module's fields, map the website value coming from the first module to the domain it asks for. Each lead is a bundle, one item flowing from module to module, so every new lead gets its own lookup.

  4. 04

    Add the Whois overview

    Click the + again and add Get a live domain Whois overview, mapped to the same domain. You can then add a module of your CRM to write both results back to the lead.

  5. 05

    Test with Run once

    Click Run once to execute the scenario one time. Open the bubble above each module to read the bundles it received and check that DataForSEO answered for the right domain.

  6. 06

    Schedule and switch it on

    If your first module is scheduled, set its clock (every 15 minutes by default for a new scenario), then switch the scenario on. Each module run counts as an operation on your Make plan.

Modules

What each DataForSEO Domain Analytics API module does

DataForSEO Domain Analytics API gives you 8 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

DataForSEO Domain Analytics API1

Get a live domain Whois overview

ActionIn the docs only

You get the Whois picture of one domain, the registration record DataForSEO returns for it, right inside your scenario. The module name is the only description Make gives, so read the first output carefully.

When to use it
a lead or partner shares a website and you want registration context next to the technology data.
Watch out
the Make documentation for this app is marked as AI generated, so confirm which fields come back with a Run once before mapping them.
DataForSEO Domain Analytics API2

Get a live technologies summary

ActionIn the docs only

This one hands you a summary view of technologies rather than a full breakdown, which keeps the result light when you only need the headline. Make publishes no description beyond the name, so treat that as a reading of the title.

When to use it
you want a quick overview to drop into a report or a message.
Watch out
compare its output with Get live domain technologies on the same input to see which fits your case.
DataForSEO Domain Analytics API3

Get domains by HTML terms

ActionIn the docs only

Turn a piece of page code into a list of websites: you give HTML terms, DataForSEO returns domains where they appear. Handy when a tool leaves a recognizable tag but has no clean technology name.

When to use it
you track a script, widget or tracking snippet and want to find the sites that carry it.
Watch out
it can return many domains, each as its own bundle, and every later module then runs once per domain.
DataForSEO Domain Analytics API4

Get domains by technology

ActionIn the docs only

Starting from a technology instead of a website, this module brings back domains DataForSEO associates with it. It is the natural first brick of a prospecting list built around a platform you know well.

When to use it
your agency serves users of one CMS or shop engine and wants to see who runs it.
Watch out
filter or limit the results before sending them to a CRM, or one run can create far more records than you planned.
DataForSEO Domain Analytics API5

Get live aggregation technologies

ActionIn the docs only

Here the output is grouped figures about technologies, going by the module name, instead of one line per domain. That makes it a fit for dashboards and market notes more than for lead enrichment.

When to use it
you prepare a report on which tools dominate a segment and want the numbers in a sheet.
Watch out
the name is all Make documents, so run it once and inspect the bundle before you build a report layout around it.
DataForSEO Domain Analytics API6

Get live domain technologies

ActionIn the docs only

Give it a domain and you receive the technologies DataForSEO detects on that site, ready to map into a CRM or a sheet. It is the module that fits the lead qualification scenario above best.

When to use it
a new lead, signup or client file includes a website and your team wants the stack before reaching out.
Watch out
map a clean domain from the previous module, with no extra text around it.
DataForSEO Domain Analytics API7

Get live technology stats

ActionIn the docs only

Statistics on a technology land in your scenario with this module, so you can follow its footprint without opening DataForSEO. Its title points to figures about one technology rather than a list of sites.

When to use it
a product or content team wants to log how widely a tool is used whenever a report is refreshed.
Watch out
Make gives no description beyond the title, so check the returned values with Run once first.
DataForSEO Domain Analytics API8

Make an API Call

ActionIn the docs only

When none of the seven named modules covers what you need, this one lets you call any endpoint of the DataForSEO Domain Analytics API with the connection you already set up. No second login required.

When to use it
the DataForSEO documentation shows an endpoint that has no dedicated module in Make.
Watch out
you build the request yourself from the vendor documentation, so test it with Run once before plugging it into a live scenario.
Need help

Need help automating DataForSEO Domain Analytics API with Make?

A person reads every message.

FAQ

DataForSEO Domain Analytics API and Make: common questions

01Is the DataForSEO Domain Analytics API Make integration free?
Yes, on the Make side. It is a standard app, available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) drop the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. Your DataForSEO subscription is separate: check the DataForSEO pricing page for what the API itself costs.
02What do you need to connect DataForSEO Domain Analytics API to Make?
You need an active DataForSEO account with API access. In your DataForSEO dashboard, open the API access section and copy the login and password shown there. Then add any module of the app in your Make scenario, click Create a connection, optionally give it a name, and paste the two values. That single connection is reused by all 8 modules of this app, so you set it up once and every new module of the app picks it up.
03Does DataForSEO Domain Analytics API trigger Make scenarios in real time?
No, because the app has no trigger at all. All 8 modules are actions, so something else has to start the scenario. You have two options. Put the trigger of another app first, for example the form or CRM where new leads arrive, and the lookup runs for each new item it sends. Or start the scenario on a schedule set on the first module, every 15 minutes by default on a new scenario and never under 15 minutes on the Free plan.
04What if a DataForSEO endpoint has no Make module?
Use Make an API Call. This module ships with the app and lets you reach any endpoint of the DataForSEO Domain Analytics API with the connection you already created, so there is no extra setup on the account side. You build the request yourself from the vendor documentation. Keep in mind that the Make documentation for this app is flagged as AI generated: when a detail matters, check it against DataForSEO directly or ask their support before you rely on it.
05Make or n8n for DataForSEO Domain Analytics API?
It depends on your criteria. On Make, this app gives you 8 ready modules, including Make an API Call for endpoints without a dedicated module, and it is available from the Free plan. Apps like this one often have an n8n node as well, but this page only documents the Make side, so check the n8n catalog for this API before you decide. The fair test is to list the endpoints you need, see which platform covers them without custom calls, and pick the editor your team is most comfortable maintaining.
Same platform

Other docs you might need on this stack.

Browse all integrations