Collect new reviews in one review log Get the source data and prepare the review Documentation-checked component path; proposed workflow, not tested WHAT WAS CHECKED Public official documentation and supplied candidate artifacts only. No product login, account exports, client data, installation, credential access, external writes, advertising spend, template imports or live tests. Proposed prompts do not prove a feature supports every requested field. Missing required source data blocks execution. BEFORE YOU START - 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. DATA ACQUISITION LIMITS - Template not imported or tested. Exact module parameters, historical coverage and idempotency are unverified. STOP IF - Missing destination approval, privacy assessment, observed trigger output or safe repeat-run behavior. KEEP THE ANALYSIS COPY SEPARATE Keep untouched original exports/screenshots and the identifying source map in restricted firm storage. Build a separate minimized analysis file; do not hide raw client data on another tab. Include the complete Scope/coverage note in the AI-visible workbook or prompt. Use aliases and administrative metadata only. Unknown is not zero, false, completed or absent. INPUT FORMAT LIMIT All capitalized analysis tables and alias fields are editorial contracts. Native exports retain real vendor headers; mapping is explicit. No blank starter template is evidence of available data. NATIVE REVIEW INPUTS version: 1 status: Requires distinct native-input templates or an explicit reviewed mapping; existing kit is not drop-in compatible compatibleWithoutMapping: False existingKitFilesInspected: - file: input-preparation.txt firstLine: 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. - file: review-log-policy-template.txt firstLine: Approved columns: [required] requiredNativeInputs: - name: ReviewLog kind: editorial_table proposedDistinctTemplate: native-reviewlog-template.csv columns: - review_key - profile_alias - source_url - captured_at - published_date_label - rating - approved_text - source_ref acquisitionRequirement: Populate only from the recipe’s documented export or explicit manual evidence capture. Existing blanks and synthetic fixtures do not supply facts. - name: Scope kind: approved_text_section proposedDistinctTemplate: native-scope-template.txt requiredContent: 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. templateFilesCreatedByThisTask: False requiredGate: Kit owner must add the named inputs or document field-level mapping before replacing an existing kit prompt. Preserve the old kit contract; never rename headers without acquiring missing evidence. OPEN THE INPUT MAPPING GUIDE NATIVE-INPUT-MAPPING.txt Use the distinct native input scaffolds listed below. Complete them from the acquired, reviewed evidence and include every required scope section in the AI-visible packet. Existing synthetic examples exercise the original review prompt only. They are not acquired evidence or a test of this native chain. ReviewLog: native-reviewlog-template.csv Scope: native-scope-template.txt STEP 1: Identify the exact collection path Tool: Make official template / Google Business Profile Open: Official Make template 4406; Google Business Profile Watch Reviews module Access needed: Existing authorized access and relevant plan/region feature; exact live subscription and permissions not tested. No setup or persistent access changes included. AI role: not_an_ai_step 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. Use it next: 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: Watch Reviews is a documented Make module, not proof that a newly connected trigger captures all past reviews. Documentation limit: The source verifies the component feature; workflow prompts, schemas, manual captures, checks and handoffs are proposed editorial adaptations. Source 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 STEP 2: Define an explicit source-to-sheet mapping Tool: Make and Google Sheets, future authorized setup only Open: Make template > scenario editor > Google Business Profile Watch Reviews > Google Sheets row action; approved spreadsheet and sheet Access needed: Existing authorized access and relevant plan/region feature; exact live subscription and permissions not tested. No setup or persistent access changes included. AI role: not_an_ai_step 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. Use it next: 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: The official template verifies a Google Sheets destination, not idempotency. A collection/record-write workflow does not need AI to function. Documentation limit: The source verifies the component feature; workflow prompts, schemas, manual captures, checks and handoffs are proposed editorial adaptations. Source documentation: https://www.make.com/templates/4406-export-google-my-business-reviews-to-google-sheets https://apps.make.com/google-sheets STEP 3: Ask AI to inspect the checked inputs Tool: Excel Copilot, optional Open: Analysis workbook > Copilot icon at lower right > Chat only Access needed: Existing authorized access and relevant plan/region feature; exact live subscription and permissions not tested. No setup or persistent access changes included. AI role: downstream_application_ai Open the minimized workbook containing the named tables and Scope. Paste the exact prompt; if unavailable, perform the same rule checks manually. PASTE THIS PROMPT 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. Use it next: Copy checked results into a new Review sheet, retaining source references and unresolved blockers. Check: If no actual native key is available, a locally assigned key must be labeled editorial and cannot prove deduplication across edits. Documentation limit: The source verifies the component feature; workflow prompts, schemas, manual captures, checks and handoffs are proposed editorial adaptations. Source documentation: https://support.microsoft.com/en-us/excel/copilot/get-started-with-copilot-in-excel STEP 4: Human review and final action Tool: Responsible firm reviewer Open: Internal Review worksheet / review document Access needed: Existing authorized access and relevant plan/region feature; exact live subscription and permissions not tested. No setup or persistent access changes included. AI role: not_an_ai_step 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. Use it next: Only after explicit setup and recurring-data-sharing authorization may the operator enable the chosen schedule. Check: No AI step is required for simple collection, no fake public reviews, no automatic reply. Documentation limit: The source verifies the component feature; workflow prompts, schemas, manual captures, checks and handoffs are proposed editorial adaptations. Source documentation: https://www.make.com/templates/4406-export-google-my-business-reviews-to-google-sheets https://apps.make.com/google-my-business ACCOUNT AND SOURCE CHECKS STILL NEEDED - The live account, entitlement, exact headers, records and field coverage have not been observed. USING THE FILES IN THIS KIT Use the exact files or source text named in the steps above. Native exports keep their own headers. The kit tables are editorial review worksheets; they are not a claim that a product exports those fields. Some routes use reviewed text directly or require additional original files. Never rename an unreviewed raw export to make it appear mapped. Keep expected-result files separate from inputs. The source account, actual data, prompts and end-to-end workflow were not tested. Any final communication, filing, permission change, payment or publication needs its own authorized human action. This guide performs none.