Resources · Make integration

DataForSEO Merchant API Make integrationAutomate DataForSEO Merchant API with Make.

Need Amazon and Google Shopping data inside your automations, without code? The DataForSEO Merchant API Make integration offers 12 action modules and no trigger. This guide is for e-commerce and SEO teams: connect the account, build a first scenario, then pick the right module.

Try the DataForSEO Merchant API integration on MakeSee the 12 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the DataForSEO Merchant API Make integration let you automate?

The DataForSEO Merchant API Make integration links your DataForSEO account to Make, so a scenario (the automation you build in Make, a chain of modules) can ask for Amazon and Google Shopping data and pass it to your other tools. Each module is one brick of that chain, and here all 12 of them are actions you call on demand.

A price watch on Google Shopping. A marketplace manager sets Get Google Shopping Products Advanced to run on a schedule, then sends the results to a spreadsheet or a chat app. Every product comes out as a bundle, one item passed to the next module.

A seller map on Amazon. A brand team pulls product lists with Get Amazon Products Advanced, then checks who sells an item with Get Amazon Sellers Advanced. The same connection serves both modules.

A review digest. Get Google Shopping Product Reviews brings back what buyers say about a product, ready to route to a support or product team.

What Make does not do here: the app has no trigger, so nothing starts on its own when a price moves. The scenario starts on its schedule, or on a trigger from another app. The Make documentation for this app also notes that its content is AI-generated and should be checked against the vendor documentation. To size the plan, read Make pricing; to weigh the other tool, open n8n vs Make; to learn the editor step by step, see Make training.

Connect

How do you connect your DataForSEO account to Make?

  1. 01

    Open the connection window

    In your scenario, add any DataForSEO Merchant API module and click Create a connection. A connection is your DataForSEO account linked to Make once, then reused by all 12 modules.

  2. 02

    Name the connection

    The Connection name field is optional, but a clear name helps when a client and an in-house account sit side by side. Pick something that says whose DataForSEO account it is.

  3. 03

    Paste your API credentials

    In DataForSEO, open the dashboard, click API Access, copy the API key shown as your login and the API token shown as your password. Paste both in Make and save.

First scenario

Your first scenario with DataForSEO Merchant API

GoalWhen the schedule fires, Make searches Google Shopping with DataForSEO Merchant API, then fetches the reviews of each product it found.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + to add a first module. The app has no trigger, so an action opens the flow.

  2. 02

    Add the product search

    Search for DataForSEO Merchant API, pick Get Google Shopping Products Advanced, then click Create a connection or choose the one you already made.

  3. 03

    Chain the reviews module

    Click the + on the right, add Get Google Shopping Product Reviews and map the product data coming out of the first module into its fields.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario one time, and you can open each module to read the bundles it received before going further.

  5. 05

    Schedule and switch on

    Open the clock on the first module: a new scenario runs every 15 minutes by default. Set the schedule that fits your watch, then switch the scenario on.

Modules

What each DataForSEO Merchant API module does in Make

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

DataForSEO Merchant API1

Get Amazon Product ASINs Advanced

ActionIn the docs only

This module gets you the ASINs, the Amazon product identifiers, in the Advanced result that its name announces, so later modules can work product by product.

When to use it
before looking up sellers or details, when you first need a clean list of identifiers.
Watch out
the Make documentation gives no description of the output, so run it once and read the bundles before mapping anything.
DataForSEO Merchant API2

Get Amazon Product ASINs HTML

ActionIn the docs only

Here you receive the ASIN lookup as HTML, as the module name states, which suits a team that stores or parses raw pages itself.

When to use it
when an archive of the page matters more than ready-to-map fields.
Watch out
if you only need identifiers to pass on, the Advanced variant is the one to try first, since HTML still has to be read by another step.
DataForSEO Merchant API3

Get Amazon Products Advanced

ActionIn the docs only

You get Amazon product results in the Advanced version, one bundle per product, ready to send to a sheet, a database or a message.

When to use it
to follow how a product line shows up on Amazon each time the scenario runs.
Watch out
each product bundle that reaches the next module costs an operation there, so filter before long chains.
DataForSEO Merchant API4

Get Amazon Products HTML

ActionIn the docs only

This one returns the Amazon product results as HTML, according to its name, for people who want the page itself rather than mapped values.

When to use it
when an analyst needs a raw copy of what Amazon displayed at the moment of the run.
Watch out
Make will not split that HTML into fields for you; plan a parsing step or prefer Get Amazon Products Advanced.
DataForSEO Merchant API5

Get Amazon Sellers Advanced

ActionIn the docs only

Knowing who sells a product on Amazon is the point of this module, which brings the seller data back in the Advanced format its name refers to.

When to use it
after a product search, to see which merchants offer an item your brand distributes.
Watch out
map the product reference from the previous module, and check with Run once that each bundle matches the right item.
DataForSEO Merchant API6

Get Amazon Sellers HTML

ActionIn the docs only

The seller lookup arrives here as HTML, per the module name, so you keep the listing as the module received it.

When to use it
when you need proof of what the seller page showed, for a dispute or an audit file.
Watch out
to compare sellers inside Make with filters and routes, the Advanced variant is easier to map than a block of HTML.
DataForSEO Merchant API7

Get Google Shopping Product Info

ActionIn the docs only

For a single Google Shopping product, this module fetches its details so the rest of the scenario can use them.

When to use it
when you already hold a product found by a search and want its full record before writing it to your catalog.
Watch out
it works on one product per run of the module, so a list of products from a search means one operation per item.
DataForSEO Merchant API8

Get Google Shopping Product Reviews

ActionIn the docs only

Customer opinions are what this module brings in: the reviews Google Shopping holds for a product, ready to route to a team.

When to use it
after Get Google Shopping Products Advanced, to track what buyers say about your products or a competitor's.
Watch out
the documentation gives no field list, so read a first result with Run once before building a filter on it.
DataForSEO Merchant API9

Get Google Shopping Products Advanced

ActionIn the docs only

Most first scenarios start with this module: it searches Google Shopping and returns the products in the Advanced format, one bundle each.

When to use it
as the opening module of a price or visibility watch, set on the scenario's schedule.
Watch out
every product found flows into the next modules, and each one counts operations there, so keep the search narrow.
DataForSEO Merchant API10

Get Google Shopping Products HTML

ActionIn the docs only

The Google Shopping search comes back as HTML with this variant, as its name says, the raw result page for you to parse.

When to use it
for archiving search pages, or when your own parser already reads that HTML.
Watch out
if the goal is to push prices into a sheet, Get Google Shopping Products Advanced saves you the parsing step entirely.
DataForSEO Merchant API11

Get Google Shopping Sellers Advanced

ActionIn the docs only

Which shops list a product on Google Shopping? This module answers with the seller data in the Advanced format, so you can compare merchants.

When to use it
for a distribution check, when a brand wants to spot resellers carrying its items.
Watch out
there is no HTML twin for this one among the 12 modules; for anything it does not cover, turn to Make an API Call.
DataForSEO Merchant API12

Make an API Call

ActionIn the docs only

When none of the ready-made modules fits, this one lets you call any endpoint of the DataForSEO Merchant API with the connection you already set up.

When to use it
for a request the 11 named modules do not cover.
Watch out
you write the request yourself, so keep the DataForSEO API documentation open and test with Run once before switching the scenario on.
Need help

Need help automating DataForSEO Merchant API with Make?

A person reads every message.

FAQ

DataForSEO Merchant API and Make: frequent questions

01Is the DataForSEO Merchant API Make integration free?
Yes on the Make side: DataForSEO Merchant API is a standard app, available from the Free plan. That plan allows 2 active scenarios, 15 minutes at least between two scheduled runs, 5 minutes of execution per run and 512 MB of data transfer. Paid plans (Core, Pro, Teams, Enterprise) lower the interval to 1 minute and count usage in operations each month. Your DataForSEO subscription is a separate matter, handled on the DataForSEO pricing page.
02What do you need to connect DataForSEO Merchant API to Make?
An active DataForSEO account and its API credentials. In the DataForSEO dashboard, click API Access, copy the API key shown as your login and the API token shown as your password. If the password is hidden, click Send by e-mail and the token arrives in your inbox. In Make, add any module of the app, click Create a connection, optionally fill Connection name, paste both values and save. One connection then serves all 12 modules.
03Does DataForSEO Merchant API trigger Make scenarios in real time?
No, because the app has no trigger module in Make: all 12 modules are actions. A scenario that uses them starts in one of two ways. Either you set a schedule on its first module, every 15 minutes by default and never under 15 minutes on the Free plan, or another app opens the flow with its own trigger and DataForSEO Merchant API runs as the next step. Either way, test first with Run once.
04What if a DataForSEO Merchant API module is missing in Make?
Use Make an API Call. It is part of the app and reaches any endpoint of the DataForSEO Merchant API with the connection you already created, so you are not limited to the 11 named modules. You write the request yourself, which means reading the DataForSEO API documentation first. Keep in mind that the Make page for this app warns its content is AI-generated, so check important details with DataForSEO directly.
05Should you use Make or n8n for DataForSEO Merchant API?
It depends on what the automation needs. In Make, this app gives 12 ready modules and Make an API Call, with one connection reused by all of them, and a first scenario built without code. n8n often has a node for the same app, so check its catalog for DataForSEO before choosing. Compare the modules each side offers for Amazon and Google Shopping, then pick the tool your team already runs.
Same platform

Other docs you might need on this stack.

Browse all integrations