Turn new reviews into response drafts
Use Make’s template to draft replies to Google reviews and save them in Airtable.
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 can miss reviews or lose track of which replies still need approval.
Why it matters: A public review response can reveal a client relationship or say more than the firm intends. Preparing a neutral draft gives staff a chance to check confidentiality and tone before anything is posted.
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: Drafts reviewed, amendments needed, and time from review arrival to a human decision.
- Make: review responses in Airtable ↗Original published template: Google reviews → generated responses → Airtable. It is not a law-firm case study.
- 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 reaches the configured Google Business Profile location.
- Make’s template monitors Google Business Profile reviews.
- It uses OpenAI to draft responses and saves them in Airtable.
- We propose keeping every response as a draft until the firm approves it.
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: A designated firm reviewer checks confidentiality, tone, and whether responding is appropriate. No response is published automatically.
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
- Official template is a reusable starting point, not a tested blueprint. Safe legal use requires a sanitization/review gate absent from the claimed default description.
Check access and setup
- The live account, entitlement, exact headers, records and field coverage have not been observed.
Identify the exact template and safe input boundary
Make official template / Google Business Profile · Official Make template 15168; GBP listing > Read reviews; Google Maps review > More > Share review for source URL
Read template 15168: Google Business Profile reviews > OpenAI response generation > Airtable records. For a safe manual pilot, capture an actual public review link and only lawyer-approved nonsensitive wording. Public reviews can themselves reveal sensitive facts; do not route raw review text automatically to AI.
- Expected output
- Verified template reference plus a sanitized review example, or a privacy blocker.
- Next step
- Use the manual drafting step below; an unmodified watch-to-AI template is not approved for live law-firm reviews.
- Check before continuing
- Template existence proves neither installed module versions nor tested field mappings. It was not imported or run.
Draft from the approved source packet
Acrobat PDF Spaces / AI Assistant, optional · Acrobat home > PDF Spaces > Create a PDF Space > Paste copied text > Add to PDF Space > chat
Paste only the approved nonconfidential packet, source IDs and full Scope note. Paste the exact prompt into the Space chat. Do not upload raw client records; this is a downstream drafting assistant, not an AI in the source application.
- Expected output
- Draft-only review record or lawyer-review escalation.
- Next step
- Copy reviewed output into an internal review document or the named downstream tool, preserving evidence IDs.
- Check before continuing
- The reviewer compares against the public source locally, without importing client records to answer it.
Map the checked output to the intended record
Airtable / Make, future authorized setup only · Make scenario editor > Airtable > Create a Record > existing approved Connection / Base / Table / Record fields
The proposed downstream table is Reviews(review_alias,source_url,captured_at,sanitized_text,reply_draft,review_status,reviewer). A human checks each field mapping. Use a pre-AI manual approval gate or separate sanitized-input draft workflow; do not connect the raw Watch Reviews output directly to AI. Existing Make Google Business Profile Watch Reviews and Airtable Create a Record are documented, but target keys and template module details require inspection after authorized setup.
- Expected output
- A mapping specification with pending approval default; no external record created.
- Next step
- Authorized operator may later build in a test base after explicit connection, data-sharing and write approval. Keep scheduling off and omit Create/Update a Review Reply.
- Check before continuing
- New OAuth/credentials, paid usage and persistent access are outside this task. Review alias is editorial; never claim it is Google’s native ID.
Human review and final action
Final human reviewResponsible firm reviewer · Internal Review worksheet / review document
Lawyer approves each draft. If a reply is separately authorized, the profile owner manually uses Business Profile > Read reviews > Reply and checks it before submission. Keep the Airtable status and actual public-post result distinct.
- Expected output
- Reviewed draft queue; no post, scenario or Airtable write performed.
- Next step
- Human-approved text only enters Google’s native Reply control.
- Check before continuing
- No auto-posting, representation confirmation or raw sensitive review upload.
What you’ll get
An inactive scenario draft or setup proposal for a staff review queue. Setup and approval are still required.
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 10 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
- Response policy template Editable recipe-specific setup input
- Setup and review checklist Use the original recipe with the provided preparation files
- Native input scaffold: SanitizedReview Approved text input for SanitizedReview; complete from verified evidence and include in the AI-visible packet
- Native input scaffold: ApprovedReplyPolicy Approved text input for ApprovedReplyPolicy; complete from verified evidence and include in the AI-visible packet
- 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.