Automate Review Requests in n8n with a Feedback Gate

More reviews lift local ranking and conversion, but the wrong automation does real damage: blast a public Google review link to every customer and you'll hand your angry ones a megaphone. The fix is a gate. Ask how it went first, then route. An n8n review request automation that pre-screens sentiment sends happy customers to Google and unhappy ones to a private form where you can fix the problem quietly.

That gate is the entire job, and it's exactly the step the templates skip. They ship a "send a review email" flow and stop. None ship the negative-feedback gate that decides who sees the public link.

This builds the gated version, from job-complete trigger to tracked touchpoint.

What you can automate in a review flow

A gated review-request workflow covers the full ask:

• Trigger a request the moment a job or order is marked complete
• Send a one-tap rating prompt by SMS and email
• Gate on the rating: high scores to the public review link, low scores to a private form
• Alert the owner instantly when a low rating comes in, while it's still fixable
• Send one polite follow-up to non-responders, then stop
• Track every touchpoint so nobody gets asked twice

The result is more public five-star reviews and fewer public one-star surprises, because the unhappy feedback got caught privately first.

Why the gate matters more than the send

Here's the opinionated part: a review-request workflow without a sentiment gate is worse than no automation at all. Manual asks are self-gating, a person doesn't text the customer who just yelled at them. Automation removes that judgment. So if you send the public link to everyone, you've systematized handing your worst experiences a public stage. The gate puts the judgment back.

The mechanic is simple. Ask for a 1–5 rating. A Switch routes on it:

rating >= 5  → public Google review link
rating <= 4  → private feedback form + owner alert

Four stars goes to the private form too. Someone who's "pretty happy" isn't reliably going to leave a glowing public review, but they will tell you what kept it from being a five. That intel is worth more than a lukewarm public post.

The review request pipeline

Trigger (job complete: webhook / sheet / CRM)
  → Wait (let the experience settle)
  → Send rating prompt (Twilio SMS + Gmail)
  → Capture rating (form webhook)
  → Switch: rating gate
      → high → public review link
      → low  → private form + Slack alert
  → Log touchpoint (Google Sheets)

The Switch in the middle is the gate. Everything before it is delivery; everything after is routing on sentiment.

1. Trigger on job complete

The flow starts when a job, order, or appointment is marked done. That's a webhook from your booking tool, a new row in a Google Sheet, or a CRM stage change. Add a short delay so the request doesn't land before the customer has walked out the door. A few hours, sometimes a day, depending on the business.

2. Send the rating prompt

A Twilio SMS and a Gmail email go out with a one-tap rating link. Personalize with the customer name and the job; keep {{customer_name}} and {{job_type}} backticked in your build notes so they're treated as variables, not literal text. SMS gets read faster; email gives a fallback. Send both, dedupe on response.

3. Capture the rating

The rating link points at a simple form whose submission hits an n8n Webhook. The payload carries the customer ID and the score. A Code node parses it into a clean object before the gate reads it. Don't let the Switch reach into a raw form payload; one field rename and the routing breaks.

4. The gate

A Switch routes on the score. Five stars: send the public Google review link by SMS, the easiest possible path while goodwill is high. Four or below: send a private feedback form and post a Slack alert to the owner with the customer and the score. The owner can call before a bad experience hardens into a public review.

// Code node ahead of the Switch: derive the gate branch
const r = Number(items[0].json.rating || 0);
return [{ json: { ...items[0].json, branch: r >= 5 ? 'public' : 'private' } }];

5. Track and follow up

Every send, rating, and outcome logs to a Google Sheet keyed on the customer. That log powers the single follow-up to non-responders (one nudge, then stop) and guarantees nobody gets asked twice. Re-asking a customer who already reviewed reads as broken, and it is.

Implementation patterns

Pattern 1: the sentiment gate. Capture a rating, Switch on it, route high to public and low to private. This is the pattern that makes the whole thing safe.

form rating → Switch(rating >= 5) → public link OR private form + alert

Pattern 2: dual-channel send with dedupe. Fire SMS and email, but track responses so a reply on one channel cancels the follow-up on the other.

Twilio + Gmail → wait → IF responded → cancel pending follow-up

Pattern 3: closed-loop alerting. Low ratings ping the owner in real time. For routing and analyzing the private feedback that comes back, the User Feedback Loop template ingests it, runs OpenAI sentiment, and notifies the team on Telegram.

n8n nodes you'll use most

Getting started

1. Decide your trigger: a webhook from the booking tool, a CRM stage, or a new sheet row.
2. Add a Wait so the request doesn't land too early.
3. Send the rating prompt over Twilio SMS and Gmail with a one-tap link.
4. Point the link at a form that POSTs to an n8n Webhook; parse the rating.
5. Add the Switch gate: 5 stars to the public Google link, 4-and-below to the private form.
6. Wire a Slack alert on the low branch so the owner can act fast.
7. Log every touchpoint to a sheet and add one follow-up for non-responders.

Requesting reviews and responding to them are two halves of the same reputation loop. For the reply side once reviews land, see the n8n review-response build, and for capturing structured feedback more broadly there's automating customer feedback in n8n. Gate strict, alert fast, and the public five-stars take care of themselves.