Resources · Make integration

DataForSEO App Data API Make integrationAutomate DataForSEO App Data API with Make.

Can Make pull App Store and Google Play data for you? The DataForSEO App Data API Make integration offers 14 modules: 12 actions and 2 searches. This guide helps a marketer or product lead connect the account and build a first scenario.

Try the DataForSEO App Data API integration on MakeSee the 14 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the DataForSEO App Data API Make integration do?

The DataForSEO App Data API Make integration lets a Make scenario (the automation you build, a chain of modules) fetch app store data: app details, app lists and user reviews from the App Store and Google Play. You drag modules instead of writing requests.

Review watch for your own app. Pair Get App Reviews from App Store with Get App Reviews from Google Play and send what users write to the place your support team already reads.

A competitor scan on Google Play. Search Google Play Listings finds apps in a niche, then Get App Info from Google Play returns the details of each one, row by row, for your analysis.

Raw pages for your own parser. The three Google Play modules that end in "in HTML" return the page itself, useful when another tool does the parsing.

What Make does not give you here: a trigger. This app has none, so a scenario starts on a schedule or on another app. The Make doc also flags its own documentation for this app as limited and describes none of the 14 modules, which is why the notes below read the module names and ask you to confirm each output with Run once. The same API may exist as an n8n node; the n8n vs Make page sets out how to choose. If you are new to the editor, the Make training covers the basics, and Make troubleshooting helps when a run fails.

Connect

How do you connect your DataForSEO account to Make?

  1. 01

    Add a module and create the connection

    Open a scenario, add any DataForSEO App Data API module and click Create a connection. A connection is your account linked to Make once, then reused by every module of this app.

  2. 02

    Name it so you can find it

    Giving the connection a name is optional, but a clear one (the account or the client it belongs to) saves guesswork when several connections show up in the same list later.

  3. 03

    Authorize, then save

    Depending on what Make shows, either authorize Make on the DataForSEO page or paste the key DataForSEO gives you. Click Save, and the module can now use the connection.

First scenario

Your first scenario with DataForSEO App Data API

GoalWhen the schedule runs, Make searches Google Play for apps and fetches the reviews of each app it finds.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + in the middle of the editor to add the first module.

  2. 02

    Add the Google Play search

    Type the app name, pick Search Google Play Listings and select your connection. This module returns zero, one or several apps, each as a bundle (one item passed to the next module).

  3. 03

    Describe your search

    Fill the fields the module shows with the search you want to follow. Keep it narrow: every app found will cost an operation, one run of one module, in the next step.

  4. 04

    Chain the reviews module

    Click the + on the right of the search, add Get App Reviews from Google Play and map the app from the bundle of the previous module.

  5. 05

    Test with Run once

    Click Run once. Make runs the scenario one time and shows the bundles each module received, which is the only reliable way to see what these modules return.

  6. 06

    Schedule and switch on

    Set the schedule on the first module, every 15 minutes by default, pick the interval that suits your follow-up, then switch the scenario on.

Modules

What each DataForSEO App Data API module does

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

DataForSEO App Data API1

Get App Info from App Store

ActionIn the docs only

You get the store page details of one iOS app in a bundle, ready to drop into a sheet or a report. The name points to App Store data only.

When to use it
Your product team tracks a single competitor app and wants its listing pulled into the next module.
Watch out
The Make doc gives no description of what comes back, so run it once and read the bundle before you map anything.
DataForSEO App Data API2

Get App Info from Google Play

ActionIn the docs only

This one hands you the Google Play details of a single Android app, which is the counterpart of the App Store module above.

When to use it
You follow the same competitor on both stores and need the Android side of the comparison.
Watch out
An App Store identifier will not describe a Google Play app, so keep each store in its own module.
DataForSEO App Data API3

Get App Info from Google Play in HTML

ActionIn the docs only

Here the Google Play details of one app come back, as the name says, in HTML rather than as ready-to-map items. That suits anyone who wants to store or parse the raw page.

When to use it
You archive listing pages as they looked on a given day, or feed them to a parser of your own.
Watch out
Choose the plain Get App Info from Google Play if all you need is to map values into another app; check what each returns with Run once.
DataForSEO App Data API4

Get App List from App Store

ActionIn the docs only

What you gain is a list of iOS apps in one call, instead of one app at a time. Make treats each app it returns as a bundle for the next module.

When to use it
A growth marketer wants to see which apps appear in a given App Store list before digging into a few of them.
Watch out
Every bundle that flows on costs an operation in each following module, so a long list multiplies the count on your plan.
DataForSEO App Data API5

Get App List from Google Play

ActionIn the docs only

You obtain a list of Android apps from Google Play in a single step, the natural start of any market scan on that store.

When to use it
You map a category on Google Play and then pass each app to a reviews or info module.
Watch out
The doc does not say how this module differs from Get Apps from Google Play; test both with Run once before you pick one.
DataForSEO App Data API6

Get App List from Google Play in HTML

ActionIn the docs only

The same Google Play list arrives as HTML, which helps when you keep the raw page for your own processing rather than mapping fields in Make.

When to use it
A data analyst stores snapshots of a Google Play list to compare them later in another tool.
Watch out
HTML is harder to map in the editor than regular items, so pick the non-HTML version when a spreadsheet is the destination.
DataForSEO App Data API7

Get App Reviews from App Store

ActionIn the docs only

This module brings back what users write about an iOS app, so you can read feedback without opening the store. It is the App Store half of review tracking.

When to use it
Support or product teams collect App Store reviews of their own app and send them to a shared sheet or channel.
Watch out
If the reviews come back as several bundles, each one costs an operation in every later module; check with Run once, and an aggregator can group them.
DataForSEO App Data API8

Get App Reviews from Google Play

ActionIn the docs only

Android user feedback lands in your scenario with this one, each review ready to route to the tool where your team reads comments.

When to use it
A mobile product manager sends Google Play reviews to the team chat to spot bugs reported by users.
Watch out
Map the app you want from a previous module, such as a Google Play search, and check the result with Run once before switching the scenario on.
DataForSEO App Data API9

Get Apps from App Store

ActionIn the docs only

You receive several iOS apps as separate bundles, ready for app-by-app processing in the next module. The name suggests a batch pull rather than one record.

When to use it
You already hold a set of App Store apps and want their data in one pass.
Watch out
Its difference with Get App List from App Store is not documented; compare the two outputs in the editor to see which fits your case.
DataForSEO App Data API10

Get Apps from Google Play

ActionIn the docs only

Several Android apps come back at once with this module, handy when the next step handles each app on its own.

When to use it
A consultant pulls a batch of Google Play apps for a client audit and writes each to a row.
Watch out
Each app becomes a bundle, and each following module then costs one operation per app: size the batch to your plan.
DataForSEO App Data API11

Get Apps from Google Play in HTML

ActionIn the docs only

This variant returns a batch of Google Play apps as HTML, for those who store or parse pages outside Make.

When to use it
You need the raw markup of several Android listings for an archive or a custom parser.
Watch out
If you plan to map values into a CRM or a sheet, the non-HTML Get Apps from Google Play is the easier choice.
DataForSEO App Data API12

Make an API Call

ActionIn the docs only

Make an API Call lets you reach any endpoint of the DataForSEO App Data API with the connection you already have. It covers what the other modules leave out.

When to use it
A request you need has no dedicated module in the list, and you know the endpoint from the DataForSEO documentation.
Watch out
You build the request yourself, so the page cannot tell you which endpoint or parameters to use; read the DataForSEO API reference first.
DataForSEO App Data API13

Search App Store Listings

SearchIn the docs only

Search App Store Listings finds iOS apps that match your search and returns zero, one or several results. Each result travels as a bundle to the next module.

When to use it
You look for competitors on a topic before pulling their details or reviews.
Watch out
A search can come back empty, and then the next modules get nothing to work on; test your query with Run once first.
DataForSEO App Data API14

Search Google Play Listings

SearchIn the docs only

With this search you get the Google Play apps that match your query, one bundle each, which makes it the usual first step of the scenario on this page.

When to use it
You want to find the Android apps in a niche and then fetch their reviews with Get App Reviews from Google Play.
Watch out
Several results mean several operations downstream, so narrow your search before you switch the scenario on.
Need help

Need help automating DataForSEO App Data API with Make?

A person reads every message.

FAQ

Questions about the DataForSEO App Data API Make integration

01Is the DataForSEO App Data API Make integration free?
Yes, on the Make side. DataForSEO App Data API is a standard app, so it works on the Free plan. That plan allows 2 active scenarios, a scheduled run every 15 minutes at the shortest, up to 5 minutes per execution, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams, Enterprise) lower the interval to 1 minute and count usage in credits each month. What DataForSEO charges for its own API is not covered here.
02What do you need to connect DataForSEO App Data API to Make?
A DataForSEO account and a Make account. The Make doc lists no prerequisite for this app. In the editor, add one of its modules, click Create a connection, name it if you like, then authorize Make on the DataForSEO page or paste the key DataForSEO provides, depending on what the window asks. Click Save. That single connection then serves all 14 modules of the app. If you manage several DataForSEO accounts, create one connection per account and name each clearly.
03Does DataForSEO App Data API trigger a Make scenario in real time?
No. The app has no trigger module at all, neither scheduled nor instant. A scenario that uses it starts in one of two ways: on its own schedule, every 15 minutes by default and down to 1 minute on paid plans, or behind a trigger from another app that calls Make. The DataForSEO modules then run as the second or third step of the flow. The clock badge you see on other apps will not appear on these modules, since none of them is a trigger.
04What if a DataForSEO App Data API module is missing in Make?
Use Make an API Call. With it, any endpoint of the DataForSEO API can be called from the scenario, with the same connection as the other modules. Keep in mind that the Make doc labels its documentation for this app as limited and describes none of the modules, so check each output with Run once and rely on the DataForSEO API reference for endpoints and parameters. If neither covers your need, look for another app in the Make catalog that serves the same data.
05Should you use Make or n8n for DataForSEO App Data API?
It depends on your setup. On Make, the app brings 12 actions, 2 searches and Make an API Call for the rest, with no trigger of its own. n8n often has a node for the same app; check whether it covers the requests you need before deciding. The comparison page linked in the section above lists the criteria without ranking either tool. Whichever you pick, test the output of each module before you build on it.
Same platform

Other docs you might need on this stack.

Browse all integrations