Collect new reviews in one review log
Use Make’s template to save new Google Business Profile reviews in Google Sheets.
Tools in the source
Practice relevance
Cross-practice idea · A general operational method. Review the stated tool and jurisdiction limits before use.
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 & evidence
Method documented by the vendor. Our law-firm adaptation and starter prompt have not been tested.
What’s been verified
The source describes a method or feature. It does not provide a verified outcome for this exact law-firm adaptation.
What to measure: New reviews captured correctly and duplicate or missing entries found during comparison.
- Make: Google reviews to Google Sheets ↗Original published template describes collecting new profile reviews in Sheets. It supplies a method, not verified law-firm results.
- Make: Maia authoring and oversight ↗Official authoring documentation. Maia can modify scenario drafts; connections and human review are still required.
Source checked: October 15, 2026. We wrote the problem summary. The vendor documents the method. We wrote these prompts. The adapted workflow hasn’t been tested.
The source method
Start when: A new review is added to the selected profile.
- Make’s template watches for new Google Business Profile reviews.
- It saves each review in Google Sheets.
- We propose adding a review owner and status; check whether these work during setup.
Limits and review
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.
Who reviews it: The firm approves the destination sheet, access permissions, retention, and test mapping before activating the scenario.
What you need
Maia in Make
- 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.
Check access and setup
- The live account, entitlement, exact headers, records and field coverage have not been observed.
Identify the exact collection path
Make official template / Google Business Profile · 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.
Define an explicit source-to-sheet mapping
Make and Google Sheets, future authorized setup only · 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.
Ask AI to inspect the checked inputs
Excel Copilot, optional · 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.
- 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.
Human review and final action
Final human reviewResponsible firm reviewer · 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.
What you’ll get
A draft review-to-sheet scenario plus a mapping and test checklist. A prompt alone does not connect accounts.
Try with the sample files
Follow the tool steps above and use the inputs named in each step. Where provided, native-* files are blank scaffolds and NATIVE-INPUT-MAPPING explains their fields. Original examples and the optional full review prompt use a separate prepared-input schema. Keep them separate unless the mapping explicitly connects them. Downloading a kit does not connect accounts or prove the workflow works.
Download inputs and checklist 9 files
Instructions, blank templates and separate synthetic examples; these files do not install an automation. Blank templates still need verified source data.
- Download starter kit All inputs, synthetic examples and review notes in one ZIP. No automation is installed.
- Start here: get the sources and prepare the review Documentation-checked acquisition, explicit manual mapping, exact prompts and human review limits
- Input preparation checklist Collect the actual recipe inputs without inventing product export headers
- Synthetic example and expected result Exercise the important safety and data-quality boundary
- Review log policy template Editable recipe-specific setup input
- Setup and review checklist Use the original recipe with the provided preparation files
- Native input scaffold: ReviewLog Empty editorial table for ReviewLog; populate from verified source evidence after reviewed mapping; not a native export
- Native input scaffold: Scope Approved text input for Scope; complete from verified evidence and include in the AI-visible packet
- Native input mapping and scope guide Old-file-to-native-input compatibility map, acquisition requirements, privacy and blocking gates
Connect your own approved accounts and test with synthetic records. This is the vendor’s template, not an exported blueprint from this directory.
Optional full review prompt for prepared inputs
Prepared-input review prompt with Maia in Make
Editorial adaptation · untested. This prompt uses the original prepared-input schema shown in the sample test. Step prompts may use different tables. Follow NATIVE-INPUT-MAPPING where supplied; do not mix the original examples with native-step inputs without mapping and checking every field.