Automate Google Review Requests With Zapier

How do you automate Google review requests with Zapier?

Pick the event in your current tool that means “the work is done” — job closed, invoice paid, appointment finished. Zapier catches that event and fires a single webhook POST to ReputeMap’s review-request endpoint. ReputeMap handles everything after: the branded email ask, the automatic reminder, and the tracked link straight to the Google review box.

That ordering is the entire trick. 97% of consumers read reviews for local businesses (BrightLocal Local Consumer Review Survey 2026), yet most local businesses still ask for those reviews in monthly batches — a CSV export three weeks after anyone felt anything about the service. The homeowner who was delighted at 2 p.m. Tuesday when the technician packed up is a different, busier person by the end of the month.

Here’s what makes this the right pattern for agencies specifically: your clients already run tools that know the exact moment satisfaction peaks. Jobber knows when the job closed. QuickBooks knows when the invoice got paid. Calendly knows when the consult wrapped. None of them turns that moment into a Google review on its own — and every client runs a different stack. The webhook recipe below is one bridge that works for all of them. You build it once, clone the Zap per client, and swap only the trigger app and one ID.

If you’re still deciding what the ask itself should say and when it should land, start with our guide on how to ask customers for reviews — automation amplifies whatever ask you design, good or bad.

The 10-minute recipe: any trigger, one webhook step

You don’t need a native integration for this. Zapier’s built-in Webhooks by Zapier action can POST JSON to any endpoint, and ReputeMap exposes a review-request endpoint built for exactly this call.

1. Grab your ReputeMap API key. Settings → API keys in your dashboard. Keys are scoped to your organization, so one key covers every client location you manage. (API access is included on every plan, trial included — more on plans below.)

2. Look up the location ID. Call GET https://api.reputemap.com/api/v1/locations with your key and you’ll get back every location as { "id": "...", "label": "Client — Location" }. Copy the id for the client you’re wiring up.

3. Build the trigger. In Zapier, pick the source app and event — say, Jobber’s “Job Closed.”

4. Shape the timing if needed. Booking-tool triggers fire when the appointment is created, not when it happens, so add Delay by Zapier’s “Delay Until” step set to the appointment’s end time. A Filter step is also where you’d skip internal jobs or repeat visits.

5. Add the Webhooks by Zapier POST step. Configure it like this:

POST https://api.reputemap.com/api/v1/review-requests
X-API-Key: rm_live_************
Content-Type: application/json

{
  "location_id": "9b2f61c4-7d3e-4a1b-8c5f-2e9d0a4b6c81",
  "email": "dana.whitfield@example.com",
  "name": "Dana Whitfield"
}

Map email and name from the trigger’s output fields — Zapier presents them as dropdowns. location_id stays hard-coded in each Zap; it’s what routes the request to the right client and the right Google listing.

6. Test it. A {"status": "sent"} response means the ask is on its way. A skipped response means ReputeMap protected you: that address previously opted out or is suppressed, so no email goes out no matter how many times the Zap fires.

Which tools can fire the trigger?

Any app with a Zapier trigger works, but these are the natural pairings for local-service clients. Every trigger below was verified against Zapier’s app directory:

Source tool	Verified Zapier trigger	When the ask should land
Jobber	”Job Closed”	Same day the job closes — see our Jobber review automation guide
Housecall Pro	”New Completed Job”	Within hours of completion — full walkthrough in Housecall Pro review automation
Square / Square Appointments	”New Appointment” + Delay Until	After the visit ends, not when it’s booked — details in Square Appointments review requests
Calendly	”Invitee Created” + Delay Until	An hour or two after the booked slot ends
QuickBooks Online	”New Paid Invoice”	Right after payment clears — a paying customer is a satisfied one, on the record
HubSpot or any CRM	”Updated Deal Stage”	The moment a deal enters your “work delivered” stage

Two of these deserve a caveat. The Square and Calendly triggers fire at booking time, which is the wrong moment to ask — nobody reviews a haircut they haven’t had. That’s what the Delay Until step fixes: the webhook holds until the appointment is actually over.

What happens after Zapier fires the webhook?

ReputeMap treats each POST as a one-person campaign send, which means the customer gets the full sequence, not a bare link:

• The email ask goes out under the location’s campaign settings, with a tracked short link that lands the customer directly in Google’s review composer.
• An automatic reminder follows if they don’t act — the polite nudge most agencies never have time to send manually.
• Every email carries an opt-out link, and opted-out addresses are suppressed from all future sends automatically. That’s the skipped status doing its job.
• Everyone gets asked. ReputeMap never gates — no “how was your experience?” filter that routes unhappy customers away from Google. That practice violates FTC rules, and Google’s, and it’s a liability you don’t want attached to your agency. Honest asking at the right moment beats filtered asking every time.
• Sends are idempotent and logged, so a Zapier retry won’t double-email a customer, and you can show clients exactly what went out and when.

The copy itself matters too — a review ask that sounds like a robot converts like one. Our review request templates cover the short, human phrasing that works for service businesses.

One knock-on effect to plan for: when asks go out at the moment of peak satisfaction, review volume climbs — and occasionally one of them will be a 2-star. ReputeMap emails you within minutes when that happens, so your client can respond before the review ages badly. See how that works in negative review alert software.

Does ReputeMap have a native Zapier app?

Not yet — and we’d rather tell you that plainly than imply otherwise. A native Zapier app (and a native Jobber app) is on the roadmap. Today, the Webhooks by Zapier recipe above does the same job in about ten minutes, and nothing breaks when the native app ships: it will sit on the same endpoint your Zaps already call.

Also worth saying out loud: this is email-based asking. ReputeMap doesn’t send SMS — review requests go out by email with automatic reminders, plus QR codes and per-employee QR links for in-person asks. If your client’s customers genuinely only respond to texts, we’re not the right fit; if email plus a QR card at the point of service works, this setup runs itself.

The Zapier recipe requires API access, which is included in the Pro plan at $49/mo (30 locations, full white-label reports, and the branded client portal — the agency bundle). Starter is $29/mo and Growth is $39/mo if you only need campaigns, QR asks, and the unified inbox without the API. Every plan starts with a 14-day free trial — card required, nothing charged until the trial ends, cancel anytime — and setup takes about 3 minutes. See plans and start your 14-day free trial, and have your first Zap firing this afternoon.