Resources · Make integration

Review Scraper Make integrationAutomate Review Scraper with Make.

Can the Review Scraper Make integration run without a line of code? Yes. Make offers 5 Review Scraper modules: one scheduled trigger, three actions and one search. If you know Review Scraper but are new to Make, this page takes you from the connection to a first live scenario.

Try the Review Scraper integration on MakeSee the 5 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Review Scraper Make integration do for you?

The integration links your Review Scraper account to Make so a scenario, the automation you build as a chain of modules, can pick up results and reviews and hand them to your other tools. Each module is one brick of that chain: a trigger, an action or a search. You drag them onto a canvas, no code involved.

Hand work over in batches. Submit a Batch sends a batch to Review Scraper from a scenario, and Get a Batch Status tells you where that batch stands, so a later module only runs once the answer suits you.

React to fresh results. Watch Results is the only trigger. Make checks it on the scenario's schedule and starts the flow when it finds something new, which spares you from opening Review Scraper to look.

Pull reviews into another app. List Reviews is a search: it can return zero, one or many reviews, each one a bundle, the item that travels from one module to the next. Add a module from your spreadsheet or chat tool after it and every review lands there.

Know the gap before you start: Make says its documentation for Review Scraper is limited because little public information exists about the app, and no module comes with an official description. Plan a test with Run once before trusting a field. If you get stuck, Make troubleshooting covers the usual errors, and Make training helps if scenarios are new to you. Many apps also exist as an n8n node; n8n vs Make lays out how to choose.

Connect

How do you connect Review Scraper to Make?

  1. 01

    Open the connection window

    Add any Review Scraper module to your scenario, then click Create a connection. The connection is your Review Scraper account linked to Make once, and every Review Scraper module will reuse it.

  2. 02

    Give it a clear name

    Naming the connection is optional, but a label such as the account owner or the client makes it easy to pick the right one later, once several scenarios share the same account.

  3. 03

    Authorize and save

    Depending on what Review Scraper asks for, either approve Make on the app's own page or paste the key the app gives you. Then click Save and Make lists the connection in the module.

First scenario

Your first scenario with Review Scraper

GoalWhen Review Scraper has new results, Make lists the matching reviews so you can send them wherever your team reads them.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the large + in the middle of the canvas to place the first module.

  2. 02

    Add Watch Results

    Search for Review Scraper, choose Watch Results and click Create a connection to link your account, or pick the connection you already made.

  3. 03

    Add List Reviews

    Click the + on the right of Watch Results, pick List Reviews and fill the fields it shows, mapping values from the trigger where they fit.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario one time; open the bubble above each module to read the bundles it received and check the reviews look right.

  5. 05

    Schedule and switch on

    Open the clock on Watch Results to set how often Make checks (every 15 minutes by default), then switch the scenario on so it keeps running without you.

Triggers

What starts a Review Scraper scenario

1 module starts a scenario when something happens in Review Scraper. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Review Scraper as soon as it happens.

Review Scraper1Watch Results

Watch Results

triggerIn the docs only

Watch Results gives your scenario a starting point: when Make finds new results in Review Scraper, the next modules run on them. The documentation lists the module without a description, so read the first bundles carefully during your test.

How it fires
scheduled. Make checks the app on the scenario's schedule, every 15 minutes by default, and at most once every 15 minutes on the Free plan.
When to use it
any time the scenario should follow results instead of you starting it by hand.
Watch out
each check costs an operation, one run of one module, which Make counts on your plan even when nothing new turns up.
Modules

What Review Scraper can do in Make

Review Scraper gives you 4 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Review Scraper1

Get a Batch Status

ActionIn the docs only

Get a Batch Status tells you where a batch stands, so the rest of the scenario can react to that answer instead of guessing. It is an action, and Make gives no official description of its output.

When to use it
right after Submit a Batch, or in a separate scenario that checks batches you sent earlier.
Watch out
run it once and read the bundle before adding a filter on its values.
Review Scraper2

List Reviews

SearchIn the docs only

With List Reviews you get reviews out of Review Scraper as separate bundles, ready to copy into a sheet, a database or a message. As a search, it can return nothing, one review or many.

When to use it
after Watch Results, when you want the reviews themselves and not just a signal.
Watch out
every module placed after it runs once per review, so a long list multiplies the operations counted on your plan.
Review Scraper3

Make an API Call

ActionIn the docs only

Make an API Call covers what the four named modules leave out: it calls any endpoint of the Review Scraper API from your scenario, with the same connection you already set up.

When to use it
when you need something the other modules do not offer and the Review Scraper API documentation describes it.
Watch out
you write the request yourself, so keep the API documentation of Review Scraper open while you fill it.
Review Scraper4

Submit a Batch

ActionIn the docs only

Submit a Batch lets a scenario hand a batch of work to Review Scraper without you opening the app. It is an action, and no official description says what the batch must contain.

When to use it
when another app, such as a form or a sheet, supplies what you want Review Scraper to process.
Watch out
pair it with Get a Batch Status, since submitting a batch does not mean the results are ready yet.
Need help

Need help automating Review Scraper with Make?

A person reads every message.

FAQ

Questions about Review Scraper and Make

01Is the Review Scraper Make integration free?
Yes, Review Scraper is a standard app in Make, so you can use it on the Free plan. That plan has limits: 2 active scenarios, a minimum of 15 minutes 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) lower the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. Usage is counted in operations per month. Your Review Scraper subscription is a separate matter that this page does not cover.
02What does it take to connect Review Scraper to Make?
A Review Scraper account and a Make account. Make's documentation lists no prerequisite for this app, so the generic steps apply: add a Review Scraper module, click Create a connection, name it if you like, then either authorize Make on the Review Scraper page or paste the key the app provides, and click Save. The connection is created once and reused by all five modules. If Make asks for a key, it comes from Review Scraper, not from Make.
03Does the Review Scraper trigger in Make react instantly?
No. Watch Results is a scheduled trigger: Make checks Review Scraper on the scenario's schedule rather than being alerted by the app. A new scenario checks every 15 minutes by default. On the Free plan, 15 minutes is also the shortest gap allowed, while paid plans go down to 1 minute. While testing, Run once launches the scenario by hand whenever you like, but in production the schedule decides when new results are picked up.
04What can you do if a Review Scraper module is missing in Make?
Use Make an API Call. This module exists for Review Scraper and calls any endpoint of the app's API with the connection you already have, so it covers requests that Get a Batch Status, List Reviews, Submit a Batch and Watch Results do not. Keep in mind that Make describes its own Review Scraper documentation as limited, so the Review Scraper API reference will be your guide for the request. Test each call with Run once and read the bundle before building on it.
05Should you automate Review Scraper with Make or with n8n?
It depends on the tool your team already works in. Make gives Review Scraper 5 modules: one scheduled trigger, three actions, one search, including Make an API Call for anything else. Many apps also have an n8n node, so check whether Review Scraper has one before deciding. Neither tool is ranked here: compare which modules each one offers for your case, and which editor you feel at ease building in. If the Make modules listed above cover your flow, you can start today on the Free plan.
Same platform

Other docs you might need on this stack.

Browse all integrations