# Changelog of Google Maps Reviews Scraper + Reputation Intelligence (`ryanclinton/google-maps-reviews-scraper`) Actor

- **URL**: https://apify.com/ryanclinton/google-maps-reviews-scraper/changelog.md
- **Full Actor documentation**: https://apify.com/ryanclinton/google-maps-reviews-scraper.md

## Changelog

### 1.0 (2026-06-09) — Deliver results to Slack and Notion

- You can now send each run's reputation read straight into your own Slack or Notion using Apify MCP connectors. Notion archives a per-run (or per-location) summary; Slack posts the daily briefing and any escalations. Your Slack/Notion credentials stay on your Apify account — the actor never sees them. Leave the new connector fields blank and the actor works exactly as before.

### 1.0 (2026-05-30) — No-limit option: collect every review

- Set Max reviews per place to 0 to collect a place's entire review history with no cap, all the way back to its oldest review (collection is newest-first, so this is the way to capture older reviews on places with thousands)

### 1.0 (2026-05-30) — Maintenance: large-run reliability

- Improved reliability of very large multi-place runs

### 1.0 (2026-05-30) — Results appear within the first minute

- Reviews now stream into the dataset as each place is scraped, instead of all appearing at the end — so you see results within about a minute of the run starting rather than waiting for the whole job to finish

### 1.0 (2026-05-30) — Much faster result writing on large runs

- Saving reviews to the dataset is now dramatically faster on runs with many reviews — large multi-place runs that previously spent many minutes writing results now finish that phase quickly

### 1.0 (2026-05-30) — Live progress while running

- The run status now updates as each place is scraped and as reviews stream in, showing the current place name, running review count, and an estimated time remaining
- Added progress reporting during the result-writing phase so large multi-place runs never appear idle