Review Roll-up — Multi-Location Review Digest

Monitor Google reviews across many business locations in a single scheduled run. Instead of checking each location one at a time, point this actor at a list of businesses and get back one combined digest: which locations need attention right now, how ratings are moving, and what complaint themes are showing up across the group.

What it does

Each run:

1. Resolves every business in your list on Google Maps (by name + city, or a pasted Maps URL).
2. Checks its current reviews against the last snapshot for that location.
3. Produces one digest covering all locations — an alert-level breakdown (none / info / warning / critical), per-location rating movement, and any recurring complaint keywords showing up in new negative reviews across the group — plus the full per-location detail.

Run it on a schedule (Apify Schedules) and wire the run's output to email or Slack via Apify Integrations for hands-off multi-location monitoring.

Input

• businesses (required) — a list of locations to check, each as { "placeQuery": "Business Name, City", "country": "gb" }. country is optional; placeQuery also accepts a pasted Google Maps URL directly.
• maxReviews (optional, default 100) — how many of the newest reviews to check per location each run, unless a location overrides it.

Output

• A markdown digest report (digest.md in the key-value store) — the fastest way to read what happened this run.
• A dataset with one digest row (the summary across all locations) plus one location row per business, machine-readable for your own dashboards or alerting.

Pricing

Pay-per-event: a flat fee per digest run, plus a per-location fee only for locations that were actually checked successfully — a location that fails to resolve isn't charged. No subscription, no per-seat pricing, no minimum location count.

Notes

• This actor is not affiliated with, endorsed by, or sponsored by Google. All data is read from Google's own publicly accessible Maps search results.
• The first run for each location records a baseline; alerts start appearing from the second run onward for that location.
• If a location can't be resolved or fetched in a given run, it's reported as an error in that location's row and the digest continues for the rest of the batch — one bad entry doesn't fail the whole run.