collect-reviews-in-google-sheets: native input mapping Collect new reviews in one review log Purpose and compatibility A blank file is an input scaffold, not a native export or completed mapping. Preserve the exact column names/order and input names. Populate only from the documented native acquisition or explicit manual evidence. Stop if a required input, permission, privacy condition or coverage requirement is missing. Do not replace an old prompt until the named inputs and field-level mapping are reviewed. These files do not authorize login, setup, imports, account changes, message sending, publication, test submissions or spending. Contract status: Requires distinct native-input templates or an explicit reviewed mapping; existing kit is not drop-in compatible Compatible without mapping: false Required inputs ReviewLog -> native-reviewlog-template.csv Exact columns: review_key,profile_alias,source_url,captured_at,published_date_label,rating,approved_text,source_ref Populate only from the recipe’s documented export or explicit manual evidence capture. Existing blanks and synthetic fixtures do not supply facts. Scope -> native-scope-template.txt Required content: Full approved scope, source account aliases, date filters, date basis/timezone, as-of capture time, definitions, source-to-alias map provenance, matching rules, inspected/excluded records, permission/privacy limits, missing-data reasons, coverage and responsible reviewer. Include recipe-specific policies, versions and tests. Scope must be inside the AI workbook or pasted packet, not merely a separate unprovided file. Complete each required field from approved source evidence. Old files and reviewed mapping input-preparation.txt Original first line: Prepare a test sheet and approved column list for review reference, date, rating, review text and staff review status. Match those concepts to actual connector fields before configuring the scenario. Confirm the duplicate-check capability or document a manual check. Record retention, access and reviewer policy. Keep the scenario inactive and use the official template linked in README. review-log-policy-template.txt Original first line: Approved columns: [required] review-log-policy-template.txt and input-preparation.txt -> Scope: carry approved columns, destination, access/retention, privacy and reviewer policy. They supply no observed trigger data or real review facts. ReviewLog requires actual reviewed review_key, profile_alias, source_url, captured_at, published_date_label, rating, approved_text and source_ref, mapped from observed output or authorized manual evidence. Confirm retention/privacy, repeat-run behavior and destination approval. Do not infer backfill or deduplication from the template description; keep the scenario inactive. How to perform the handoff 1. Keep original exports and raw evidence unchanged in restricted firm storage. Check actual source fields, dates, coverage, privacy and access before mapping. 2. Prepare the distinct native inputs above. Record every mapped field, derived interpretation, missing value and observed source reference in Scope. Identically named columns still require source/evidence validation. 3. Create a separate minimized analysis workbook or text packet. Name tables/sections exactly as listed. A CSV file does not itself create a named Excel table. 4. Include the full completed Scope in the same AI-visible workbook or pasted packet. Verify exclusions, denominator, matching rules and unknowns. Do not hide raw client data on another worksheet. 5. Obtain the responsible reviewer’s approval of the completed mapping and evidence coverage before using the native prompt. Keep all blocked items visible. Any later external action is a separately authorized human step. Acquisition and privacy requirements Use approved minimized administrative metadata and aliases only. Aliases alone do not guarantee anonymity. Keep untouched exports/screenshots, identifying source maps, full documents and sensitive narratives in restricted firm storage. A hidden worksheet is not a privacy boundary. Do not insert credentials, payment/tax identifiers, raw client documents or unsanitized review text. Unknown is not zero, false, completed or absent. 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. Template not imported or tested. Exact module parameters, historical coverage and idempotency are unverified. The live account, entitlement, exact headers, records and field coverage have not been observed. Recipe acquisition / manual mapping instructions Identify the exact collection path 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. Verification: Watch Reviews is a documented Make module, not proof that a newly connected trigger captures all past reviews. 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 Do not proceed when - Missing destination approval, privacy assessment, observed trigger output or safe repeat-run behavior. Scope template requirements Full approved scope, source account aliases, date filters, date basis/timezone, as-of capture time, definitions, source-to-alias map provenance, matching rules, inspected/excluded records, permission/privacy limits, missing-data reasons, coverage and responsible reviewer. Include recipe-specific policies, versions and tests. Scope must be inside the AI workbook or pasted packet, not merely a separate unprovided file. Old examples and validation limits Legacy synthetic examples and negative cases belong to their old prompts. They do not automatically test the native route and must not be fed into a new prompt without an explicit reviewed mapping and separately approved test design. These new files contain no synthetic values, source exports, account results or live-test evidence. Documentation-checked component path; proposed workflow, not tested Public official documentation checked 2026-10-15; no login, export, live query, import, installation, configuration, message or client workflow was executed. Local validation covers only exact scaffold schemas, placeholder presence, blank CSV rows and required warnings. It does not establish live account coverage, native export validity, successful integration or completed workflow tests.