automations / Make · updated 2026-07-20

Google Play reviews snapshot (Make)

The review-snapshot job as a Make blueprint: one HTTP module pulls an app's newest reviews, an Iterator fans them out one bundle per review with the numeric score, and failed lookups exit on a filtered route. Schedule the scenario for a daily snapshot.

Get the blueprint on GitHub Google Play Reviews Scraper docs

100 newest reviews per day cost $0.008 — about $0.24 per month per app.

What's inside

  1. 1.Get new reviews (HTTP → Make a request → run-sync-get-dataset-items, sort: newest)
  2. 2.One bundle per review (Flow control → Iterator)
  3. 3.Router with two filtered routes: success = true and success = false
  4. 4.Review row (billed route: app_id, numeric score, text, posted_at)
  5. 5.Failure row (unbilled route: app_id, code, request_id)

Set it up

Open the blueprint on GitHub (button above), click Raw and save the file, then in the Make scenario editor: ⋯ (More) → Import Blueprint — Make imports blueprints from a file, not a URL. Open Get new reviews and replace YOUR_APIFY_TOKEN; set appIds to your app's package name. For a daily snapshot, set the scenario's schedule in Make — the blueprint itself carries no schedule. The token comes from Apify Console → Settings → API tokens; the free tier works, and the run bills per delivered row on your Apify account.

Ways to extend it

  • Append Review row bundles to Google Sheets for a running log.
  • Add a third route filtered on score ≤ 2 into Slack for negative-review alerts (the n8n version of that pattern ships as its own template).
  • Duplicate the scenario with a competitor's package name to watch both side by side.

Going deeper: the Make guide — the same HTTP + Iterator + filter pattern, step by step; the Python/pandas export guide for working with the same review rows. Actor pricing: what a Google Play Reviews Scraper run costs. Error codes the failure branch can carry: the error-code reference.