<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[ReputeMap Engineering]]></title><description><![CDATA[ReputeMap Engineering]]></description><link>https://reputemap.hashnode.dev</link><image><url>https://cdn.hashnode.com/uploads/logos/6af9a1d1b0bfe49a3cef3817/ea1aef21-534a-4275-8f7f-ebc40f3dadbb.png</url><title>ReputeMap Engineering</title><link>https://reputemap.hashnode.dev</link></image><generator>RSS for Node</generator><lastBuildDate>Wed, 18 Nov 2026 14:43:11 GMT</lastBuildDate><atom:link href="https://reputemap.hashnode.dev/rss.xml" rel="self" type="application/rss+xml"/><language><![CDATA[en]]></language><ttl>60</ttl><item><title><![CDATA[Send a Google review request automatically when a job closes: a webhook recipe for Zapier, Make and n8n]]></title><description><![CDATA[A webhook recipe for Zapier, Make and n8n: send a Google review request after each job, with de-duplication, delays, quiet hours and a log.]]></description><link>https://reputemap.hashnode.dev/send-a-google-review-request-automatically-when-a-job-closes-a-webhook-recipe-for-zapier-make-and-n8n</link><guid isPermaLink="true">https://reputemap.hashnode.dev/send-a-google-review-request-automatically-when-a-job-closes-a-webhook-recipe-for-zapier-make-and-n8n</guid><category><![CDATA[webhooks]]></category><category><![CDATA[Zapier]]></category><category><![CDATA[automation]]></category><dc:creator><![CDATA[ReputeMap]]></dc:creator><pubDate>Sun, 15 Nov 2026 12:24:16 GMT</pubDate><content:encoded><![CDATA[<p>Most home-service and clinic owners agree that the best moment to ask for a Google review is right after the job: the plumber just left, the invoice is paid, the visit is fresh. The worst way to do it is by hand, because by Friday nobody remembers who to ask.</p>
<p>The fix is boring and reliable: your job tool fires a webhook when a job closes, and something sends the review request. Here's the pattern we built at ReputeMap, and the details that decide whether it works in real life.</p>
<h2>The shape of it</h2>
<p>Every workspace gets a private trigger URL:</p>
<pre><code class="language-plaintext">POST https://api.reputemap.com/api/hooks/jobs/rmj_…
</code></pre>
<p>Your tool posts the customer. JSON or form-encoded both work:</p>
<pre><code class="language-bash">curl -X POST "https://api.reputemap.com/api/hooks/jobs/rmj_…" \
  -H "Content-Type: application/json" \
  -d '{"first_name":"Ava","email":"ava@example.com",
       "job_id":"J-1042","location":"Austin","staff":"Jesse Ramirez"}'
</code></pre>
<p>ReputeMap then sends the same review request a person would send from the app: by email, or by text from the business's own Quo (OpenPhone) or Twilio number when there's only a phone.</p>
<h2>Wiring it up</h2>
<ul>
<li><strong>Zapier:</strong> trigger = your tool's "job completed" / "invoice paid", action = <em>Webhooks by Zapier → POST</em> to the trigger URL. (Webhooks by Zapier needs a paid Zapier plan.)</li>
<li><strong>Make:</strong> your tool's module → <em>HTTP → Make a request</em>, method POST, body type JSON.</li>
<li><strong>n8n:</strong> your trigger node → <em>HTTP Request</em> node, POST, JSON body.</li>
<li><strong>Housecall Pro:</strong> its Webhooks app (MAX plan) can post <code>job.completed</code> straight to a location's own trigger URL.</li>
<li><strong>Jobber:</strong> through Zapier's "Job Closed" trigger.</li>
</ul>
<h2>Five details that matter more than the webhook</h2>
<p><strong>1. Forgiving field names.</strong> Every tool names things differently: <code>First Name</code>, <code>customer_email</code>, <code>customer[email]</code>, a nested <code>customer</code> object. We normalise case, spaces, dashes and common prefixes, and look inside wrapper objects like <code>data</code> or <code>payload</code>. Otherwise every new tool turns into a support ticket.</p>
<p><strong>2. Never ask twice.</strong> Webhooks get retried, and Zaps get duplicated. The <code>job_id</code> (or invoice or appointment id) is the de-duplication key: the same job never sends twice. On top of that, anyone asked in the last 30 days, by any location or campaign, is skipped.</p>
<p><strong>3. Wait a little.</strong> Requests go out 2 hours after the event by default. "Job closed" often fires while the technician is still in the driveway.</p>
<p><strong>4. Respect the quiet.</strong> Quiet hours hold requests at night and on weekends, and opt-outs from any channel are honoured everywhere.</p>
<p><strong>5. Show what happened.</strong> The settings page has a "Send a test event" button that runs the whole pipeline without sending anything, and a log of the last 50 events with the outcome in plain words: queued, sent, skipped (duplicate job, asked recently, opted out), or rejected (no email or phone, unknown location). Silent failures are the number-one complaint about review-request tools, and a log is the cheapest cure.</p>
<h2>One rule we won't break</h2>
<p>Every customer gets the same request. There's no "only ask the happy ones" filter and no way to cancel a queued request because the job went badly. Google's review policies and the FTC's 2024 rule on consumer reviews both forbid review gating, and it backfires anyway.</p>
<h2>Links</h2>
<ul>
<li>Setup guide for each tool: <a href="https://reputemap.com/integrations/job-tools">reputemap.com/integrations/job-tools</a></li>
<li>REST API and MCP server for the rest: <a href="https://reputemap.com/docs/api">reputemap.com/docs/api</a></li>
</ul>
]]></content:encoded></item></channel></rss>