Resources · Make integration

DataForSEO Content Analysis API Make integrationAutomate DataForSEO Content Analysis API with Make.

Can Make pull content analysis data from DataForSEO without a line of code? Yes: the DataForSEO Content Analysis API Make integration gives you 14 modules, 13 actions and 1 search. This guide shows how to link your account, build a first scenario and pick the right module.

Try the DataForSEO Content Analysis API integration on MakeSee the 14 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the DataForSEO Content Analysis API Make integration do?

The DataForSEO Content Analysis API Make integration lets a Make scenario (the automation you build, a chain of modules) send requests to your DataForSEO account and pass the answers to other apps. Each module is one brick of that chain. This app has no trigger, so something else starts the scenario: a schedule or another app.

A sentiment snapshot on demand. A row lands in the tool your team already uses, Make calls Get Sentiment Analysis Data and hands the answer to the next module, so the result sits next to the row instead of in a separate dashboard.

A trend check for a content plan. Pair Get Phrase Trends with Get Category Trends to collect both views in one run, then store them wherever your editors plan their pieces.

A list of citations to review. Search Citation Data returns a set of results, and Make handles each one as a separate bundle (one item flowing to the next module), which makes it easy to write them out one per line.

Know the limits before you start. Seven of the 14 modules carry the tag (deprecated) in Make, and the Make documentation for this app is AI-generated and warns it may contain mistakes, so check anything important against DataForSEO's own docs. If you want a guided start, the Make training walks through scenarios step by step, and the Make troubleshooting guide helps when a run fails. The same app often has an n8n node too; the n8n vs Make comparison lays out how the two tools differ.

Connect

How do you connect DataForSEO to Make?

  1. 01

    Add a module and open the connection

    Log in to Make, add any DataForSEO Content Analysis API module to your scenario and click Create a connection. A connection is your DataForSEO account linked to Make once, then reused by every module of the app.

  2. 02

    Name it so you can find it later

    The Connection name field is optional. A clear label still helps when you run several DataForSEO accounts or share scenarios with a teammate who has to pick the right one.

  3. 03

    Paste your DataForSEO credentials

    Enter the authentication credentials from your DataForSEO account, or follow the instructions Make shows on screen. They sit in the section of your DataForSEO account where your login credentials are displayed.

First scenario

Build your first scenario with DataForSEO Content Analysis API

GoalWhen a new entry appears in the app you start from, Make asks DataForSEO for sentiment data, then for rating distribution data, and hands both results to the rest of the scenario.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + to add the first module. Since DataForSEO has no trigger, pick the module of the app that holds your source entries.

  2. 02

    Add the sentiment module

    Click the + on the right of that first module, search for DataForSEO Content Analysis API and pick Get Sentiment Analysis Data. Click Create a connection if this is your first DataForSEO module.

  3. 03

    Map the values it needs

    Fill the module fields with data mapped from the first module, so every new entry sends its own value to DataForSEO instead of a fixed one typed by hand.

  4. 04

    Chain the rating module

    Add Get Rating Distribution Data after it and fill its fields the same way. You now have two views on the same entry, ready for whatever module comes next.

  5. 05

    Test with Run once

    Click Run once. Make executes the scenario one time and shows the bundles each module received, so you can read what DataForSEO actually sent back before going further.

  6. 06

    Schedule and switch it on

    Set the schedule on the first module (every 15 minutes by default) and switch the scenario on. On the Free plan, 15 minutes is also the shortest gap between two scheduled runs.

Modules

What can each DataForSEO Content Analysis API module do?

DataForSEO Content Analysis 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 Content Analysis API1

Generate Meta Tags (deprecated)

ActionIn the docs only

As its name says, this module was built to produce meta tags for a page, and Make now flags it as deprecated, meaning it is on its way out and should not anchor a new scenario.

When to use it
only to keep an older scenario running while you plan its replacement.
Watch out
Make's documentation names no successor for it, so test your fallback, for example Make an API Call, before the day it stops working.
DataForSEO Content Analysis API2

Generate Sub-Topics (deprecated)

ActionIn the docs only

This one targets content planning: going by its name, it breaks a subject into smaller topics you can turn into sections or articles. Make lists it as deprecated.

When to use it
in an existing brainstorming scenario you have not rebuilt yet.
Watch out
the Make documentation for this app is AI-generated and may contain mistakes, so confirm on DataForSEO's side what this endpoint still returns before relying on it.
DataForSEO Content Analysis API3

Generate Text Based on a Topic (deprecated)

ActionIn the docs only

Here the starting point is a subject rather than a draft: the name points to text written from a topic you supply. The deprecated tag tells you not to design new work around it.

When to use it
to keep a legacy drafting flow alive for now.
Watch out
anything generated still needs a human read before it goes anywhere public, since the documentation says nothing about the quality or length of the output.
DataForSEO Content Analysis API4

Generate Text From Initial Input (deprecated)

ActionIn the docs only

Unlike the topic-based module, this one starts from text you already have and, judging by its name, continues or expands it. It carries the same deprecated tag in Make.

When to use it
when an old scenario feeds it the opening lines of a draft.
Watch out
mixing it with the topic-based module in one scenario doubles the calls and the operations Make counts on your plan.
DataForSEO Content Analysis API6

Get Grammar Corrections (deprecated)

ActionIn the docs only

A proofreading step inside a scenario: the name promises grammar fixes on a piece of text you send. Make marks it deprecated, so treat it as a temporary helper.

When to use it
in a review flow that already exists and that you are not ready to rebuild.
Watch out
keep the original text next to the corrected one in your output, so nobody loses the source if the suggestion reads wrong.
DataForSEO Content Analysis API8

Get Rating Distribution Data

ActionIn the docs only

Judging by its name, Get Rating Distribution Data shows how ratings spread out for what you query, which tells you more than a single average. It is a current module, not a deprecated one.

When to use it
right after the sentiment module, to put tone and ratings side by side for the same entry.
Watch out
the documentation lists no field for this module, so rely on the list Make shows once your connection exists.
DataForSEO Content Analysis API9

Get Sentiment Analysis Data

ActionIn the docs only

This is the module that tells you how something is talked about: it fetches sentiment analysis data from DataForSEO and passes it to the next brick of your scenario.

When to use it
when a brand, product or topic enters your tracking sheet and you want its sentiment captured without opening DataForSEO.
Watch out
the Make documentation for the app may contain mistakes, so double-check how you read the result against DataForSEO's docs.
DataForSEO Content Analysis API10

Get a Summary

ActionIn the docs only

Get a Summary hands you a condensed view of the data behind your request, in one module call. Next to the deprecated Get a Text Summary, it looks like the version to choose today.

When to use it
when a report or a message only needs the short version, not every detail.
Watch out
the documentation does not say whether it summarizes text or analysis data, so run it once and read the bundle first.
DataForSEO Content Analysis API11

Get a Text Summary(deprecated)

ActionIn the docs only

The older way to shorten content: the name points to a summary of a text you pass in, and Make tags the module as deprecated.

When to use it
only in a scenario that already depends on it and still gives you what you need.
Watch out
when you rebuild that scenario, test Get a Summary in its place, and compare both outputs with Run once before switching the old one off.
DataForSEO Content Analysis API12

Make an API Call

ActionIn the docs only

Make an API Call is your way around the gaps: it lets the scenario call any endpoint of the DataForSEO API with the same connection, even when no ready-made module covers it.

When to use it
when a deprecated module stops doing what you need, or when the endpoint you want has no module at all.
Watch out
you write the request yourself here, so keep DataForSEO's own API docs open while you set it up.
DataForSEO Content Analysis API13

Paraphrase Text (deprecated)

ActionIn the docs only

Paraphrase Text rewords a passage you send, as its name suggests, so the same idea comes back in different words. Make lists it among the deprecated modules.

When to use it
in an older flow that turns one product description into a variant for another channel.
Watch out
reworded copy can drift in meaning, so route the output to a person for approval rather than straight to a live page.
DataForSEO Content Analysis API14

Search Citation Data

SearchIn the docs only

Search Citation Data is the only search module of the app: it looks up citation data and can return zero, one or several results, each one as its own bundle.

When to use it
when you want a list of mentions to review, one line per result in a sheet.
Watch out
every module placed after it runs once per bundle, so a long result list multiplies the operations Make counts.
Need help

Need help automating DataForSEO Content Analysis API with Make?

A person reads every message.

FAQ

Questions about the DataForSEO Content Analysis API Make integration

01Is the DataForSEO Content Analysis 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, 15 minutes at least between two 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 and allow 40 minutes of execution. Your DataForSEO account is a separate subscription, described on DataForSEO's own pricing page.
02What do you need to connect DataForSEO Content Analysis API to Make?
An active DataForSEO account and an API key. In Make, add any module of the app, click Create a connection, optionally give it a name, then enter the authentication credentials from your DataForSEO account. They appear in the section of that account where your login credentials are shown. Once saved, the connection is reused by every DataForSEO module in your scenarios, so you only do this once per account, not once per module.
03Does the DataForSEO Content Analysis API react in real time in Make?
No, because the app has no trigger module at all, neither scheduled nor instant. A scenario that uses it has to start another way. Either you open it with a trigger from another app, which fires when that app sees something new, or you rely on the schedule of the first module, set to every 15 minutes by default. On the Free plan, 15 minutes is the shortest interval; paid plans go down to 1 minute.
04What if the DataForSEO module you need is missing or deprecated?
Use Make an API Call. It lets the scenario call any endpoint of the DataForSEO API with the connection you already have, so it covers what the 14 listed modules do not. It is also the natural fallback for the seven modules tagged deprecated. Keep in mind that the Make documentation for this app is AI-generated and may contain mistakes, so check the endpoint details in DataForSEO's own docs before you build on them.
05Should you use Make or n8n with DataForSEO Content Analysis API?
It depends on the tool your team already runs. In Make, you get 14 ready modules, one connection shared by all of them and Make an API Call for everything else. The same app often has an n8n node as well, so check it exists before comparing. Neither tool is ranked above the other here: look at which one already hosts your other automations, and read the n8n vs Make comparison linked earlier on this page for the differences.
Same platform

Other docs you might need on this stack.

Browse all integrations