# Collect new reviews in one review log Canonical page: https://agents.paretoid.com/workflows/collect-reviews-in-google-sheets/ Category: Local SEO Practice relevance: cross-practice. A general operational method. Review the stated tool and jurisdiction limits before use. Jurisdiction/provider scope: Use Make’s template to save new Google Business Profile reviews in Google Sheets. Status: Method documented by the vendor. Our law-firm adaptation and starter prompt have not been tested. Verification: The source describes a method or feature. It does not provide a verified outcome for this exact law-firm adaptation. ## The problem Staff need a review log they can check without repeatedly opening the public profile. Why it matters: Reviews spread across locations can be missed or handled twice. A dated review log gives staff a shared record of what arrived and what still needs attention. ## Sources and evidence - method: [Make: Google reviews to Google Sheets](https://www.make.com/templates/4406-export-google-my-business-reviews-to-google-sheets) Original published template describes collecting new profile reviews in Sheets. It supplies a method, not verified law-firm results. - authoring: [Make: Maia authoring and oversight](https://help.make.com/maia-by-make-system-card) Official authoring documentation. Maia can modify scenario drafts; connections and human review are still required. Source checked: October 15, 2026. ## Suggested approach Start when: A new review is added to the selected profile. 1. Make’s template watches for new Google Business Profile reviews. 2. It saves each review in Google Sheets. 3. We propose adding a review owner and status; check whether these work during setup. ## What you need - Existing authorized access to the correct source account and records; no new login, credentials, installation or permission grant is included. - Responsible lawyer/operations reviewer approves scope, definitions and any later action. - AI optional; use only approved minimized data and retain originals separately. - Use synthetic inputs first. Keep real data in firm-approved accounts and processing, with appropriate access, confidentiality and retention controls. Aliases alone do not anonymize records. Never paste credentials, API keys or unnecessary client details. ## How to use Documentation-checked component path; proposed workflow, not tested - Template not imported or tested. Exact module parameters, historical coverage and idempotency are unverified. Access and setup: - The live account, entitlement, exact headers, records and field coverage have not been observed. ### 1. Identify the exact collection path Tool: Make official template / Google Business Profile Location: Official Make template 4406; Google Business Profile Watch Reviews module Template 4406 describes storing new location reviews in Google Sheets. Read it without importing. Record intended profile/location and approved destination spreadsheet; assess what public review fields may be retained. No backfill, deduplication, edits or deletions behavior is promised by the description. Expected output: Exact template reference and a bounded collection specification. Next step: For a manual pilot, copy a review’s actual Share link and visible metadata into a local sample ledger; do not create a public fake review. Check before continuing: Watch Reviews is a documented Make module, not proof that a newly connected trigger captures all past reviews. Execution status: Public official documentation checked 2026-10-15; no login, export, live query, import, installation, configuration, message or client workflow was executed. Step documentation: https://www.make.com/templates/4406-export-google-my-business-reviews-to-google-sheets https://apps.make.com/google-my-business https://support.google.com/business/answer/3474050?hl=en ### 2. Define an explicit source-to-sheet mapping Tool: Make and Google Sheets, future authorized setup only Location: Make template > scenario editor > Google Business Profile Watch Reviews > Google Sheets row action; approved spreadsheet and sheet Proposed sheet columns are review_key,profile_alias,source_url,captured_at,published_date_label,rating,approved_text,review_status. The operator must inspect the trigger’s actual sample output, native review identifier if any, cursor/start position, pagination and row action fields before mapping. No invented native header or trigger parameter. Preserve raw approved source capture separately; exclude sensitive narrative unless explicitly approved for this destination. Expected output: Mapping and acceptance-test specification; no sheet created or written. Next step: For the optional AI QA, first create a separate local ReviewLog table from the approved manual pilot capture or an actually available existing log: review_key,profile_alias,source_url,captured_at,published_date_label,rating,approved_text,source_ref. Include complete Scope and key-provenance notes in that workbook; an empty schema is not evidence. The future authorized operator checks new-review, repeat-run, edited-review and missing-text cases in a private test sheet only after separate permission. Check before continuing: The official template verifies a Google Sheets destination, not idempotency. A collection/record-write workflow does not need AI to function. Execution status: Public official documentation checked 2026-10-15; no login, export, live query, import, installation, configuration, message or client workflow was executed. Step documentation: https://www.make.com/templates/4406-export-google-my-business-reviews-to-google-sheets https://apps.make.com/google-sheets ### 3. Ask AI to inspect the checked inputs Tool: Excel Copilot, optional Location: Analysis workbook > Copilot icon at lower right > Chat only Open the minimized workbook containing the named tables and Scope. Paste the exact prompt; if unavailable, perform the same rule checks manually. Prompt: ```text Optional QA only: use the sanitized ReviewLog and Scope. Check repeated review_key values, missing source_url, inconsistent profile aliases and capture-date gaps. Do not infer unseen or deleted reviews, compute client satisfaction from legal outcomes, or invent a complete backfill. Return anomalies with source rows and coverage limits; do not change the sheet or post replies. ``` Expected output: Optional data-quality checklist for an existing sanitized log. Next step: Copy checked results into a new Review sheet, retaining source references and unresolved blockers. Check before continuing: If no actual native key is available, a locally assigned key must be labeled editorial and cannot prove deduplication across edits. Execution status: Public official documentation checked 2026-10-15; no login, export, live query, import, installation, configuration, message or client workflow was executed. Step documentation: https://support.microsoft.com/en-us/excel/copilot/get-started-with-copilot-in-excel ### 4. Human review and final action Tool: Responsible firm reviewer Location: Internal Review worksheet / review document Collection owner approves storage scope and verifies the trigger-to-row mapping and replay behavior after a separately authorized synthetic/private pilot. Keep the scenario off until those checks pass. Expected output: Approved collection plan with tests pending; no live monitor or sheet write. Next step: Only after explicit setup and recurring-data-sharing authorization may the operator enable the chosen schedule. Check before continuing: No AI step is required for simple collection, no fake public reviews, no automatic reply. Execution status: Public official documentation checked 2026-10-15; no login, export, live query, import, installation, configuration, message or client workflow was executed. Step documentation: https://www.make.com/templates/4406-export-google-my-business-reviews-to-google-sheets https://apps.make.com/google-my-business ## What you will get A draft review-to-sheet scenario plus a mapping and test checklist. A prompt alone does not connect accounts. ## Human review and limits The firm approves the destination sheet, access permissions, retention, and test mapping before activating the scenario. The assistant drafts or reports only. Check source records and review the output before a human performs any separately approved send or change. No automatic legal decision, money movement, account connection or publication is included. What to measure: New reviews captured correctly and duplicate or missing entries found during comparison. ## Original prepared-input schema Synthetic example input: ```text ``` Expected synthetic output: ```text ``` Failure check: ## Starter files Native blank scaffolds and original synthetic examples may use different schemas. Follow NATIVE-INPUT-MAPPING where supplied. These files do not connect accounts or install automation. - [Download starter kit](https://agents.paretoid.com/assets/starter-kits/collect-reviews-in-google-sheets-starter-kit.zip) — All inputs, synthetic examples and review notes in one ZIP. No automation is installed. - [Start here: get the sources and prepare the review](https://agents.paretoid.com/assets/starter-kits/collect-reviews-in-google-sheets/START-HERE.txt) — Documentation-checked acquisition, explicit manual mapping, exact prompts and human review limits - [Input preparation checklist](https://agents.paretoid.com/assets/starter-kits/collect-reviews-in-google-sheets/input-preparation.txt) — Collect the actual recipe inputs without inventing product export headers - [Synthetic example and expected result](https://agents.paretoid.com/assets/starter-kits/collect-reviews-in-google-sheets/synthetic-test.txt) — Exercise the important safety and data-quality boundary - [Review log policy template](https://agents.paretoid.com/assets/starter-kits/collect-reviews-in-google-sheets/review-log-policy-template.txt) — Editable recipe-specific setup input - [Setup and review checklist](https://agents.paretoid.com/assets/starter-kits/collect-reviews-in-google-sheets/README.txt) — Use the original recipe with the provided preparation files - [Native input scaffold: ReviewLog](https://agents.paretoid.com/assets/starter-kits/collect-reviews-in-google-sheets/native-reviewlog-template.csv) — Empty editorial table for ReviewLog; populate from verified source evidence after reviewed mapping; not a native export - [Native input scaffold: Scope](https://agents.paretoid.com/assets/starter-kits/collect-reviews-in-google-sheets/native-scope-template.txt) — Approved text input for Scope; complete from verified evidence and include in the AI-visible packet - [Native input mapping and scope guide](https://agents.paretoid.com/assets/starter-kits/collect-reviews-in-google-sheets/NATIVE-INPUT-MAPPING.txt) — Old-file-to-native-input compatibility map, acquisition requirements, privacy and blocking gates ## Optional original prepared-input prompt Destination: Maia in Make This original prompt uses its own prepared-input schema. Do not mix it with native-step tables without the supplied mapping. ```text Prepare a NEW, INACTIVE Make scenario following the published template that stores new Google Business Profile reviews in Google Sheets. Use [test profile placeholder], [test sheet placeholder], and [approved column list]. Do not change any live scenario. Propose fields for review reference, date, rating, review text, and a staff review-status column. Explain which fields are available; do not invent a connector field. Identify a safe duplicate-check option or mark it as a manual review step if unsupported. Use synthetic reviews only for the proposed test. Do not fetch real reviews, post replies, change a profile, or share the sheet. List connections, permissions, plan limits to check, and unresolved mapping questions. Do not ask for passwords or API keys in chat. Return a configuration checklist and leave everything inactive until [reviewer role] approves the test and privacy settings. ``` Editorial adaptation · untested Published by Law Firm Agents. Proposed adaptation; not tested. Not legal advice.