The problem this solves

Asking for reviews consistently is easy to mean to do and easy to never actually do. The businesses that do it well end up with a steady stream of public proof; the ones that don't rely on luck, and still get blindsided when an unhappy customer posts first.

This kit automates the ask, every time, and gives unhappy customers a private channel before a public one.

Who it's for

  • Service businesses with a clear "job done" moment, trades, studios, clinics, hospitality, anyone who finishes discrete jobs
  • Businesses that currently ask for reviews inconsistently, or not at all
  • Anyone who already owns the Lead Machine kit and wants the post-sale half of the same system

What the workflow does

Below is the exact nodes from workflow/review-followup.json, as two independent triggers. The moment that matters is the rating fork, happy customers head toward a public review, everyone else goes privately to you.

16 real nodesnames from the workflow filepaths verified against the kit's own logic

A happy customer is thanked and nudged toward your public review link.

Job Completed (Webhook)
Validate JobCode node
Is Job Valid?
Respond: Job RejectedHTTP 422
Respond: Job ScheduledHTTP 200 · immediately
Wait Before Askingdefault 1 day
Build Review Requestfeedback link
Feedback Received (Webhook)
Validate FeedbackCode node
Is Feedback Valid?
Respond: Feedback RejectedHTTP 422
Rating >= 4?
Public reviewGoogle / Facebook
Private to the ownernever pushed public
Respond: Feedback ReceivedHTTP 200

Step by step

  1. Triggers when a job is marked complete, any system that can call a webhook.
  2. Waits a configurable delay (1 day by default) so the ask doesn't feel instant or robotic.
  3. Sends a review-request email with a short feedback link.
  4. Routes the response: a rating of 4-5 gets a thank-you and a nudge toward your public review link; a rating of 1-3 goes privately to the owner, with the full comment, and is never pushed toward the public platform.
  5. Never silently drops a response: every feedback submission gets a clear success or validation-error response.

What's included

The workflow

An importable n8n workflow, two webhook entry points, a configurable delay, rating-based routing, bounded retries.

Setup guide

Import, credential wiring, feedback-link fix, and go-live checklist.

Configuration checklist

Every placeholder you must edit, including the one that silently breaks the feedback link if missed.

Credential instructions

SMTP setup, reuse the same credential as the Lead Machine kit if you already have it.

Architecture diagram

Every node explained, including the reasoning behind the rating threshold and why it isn't "review gating".

Sample test data + a runnable test

Eight realistic test events and a zero-dependency script that proves the validation and routing logic.

Troubleshooting guide

Common import and runtime issues, with fixes.

Prerequisites

  • An n8n instance (self-hosted or n8n Cloud)
  • An SMTP-capable email account (reuse the Lead Machine kit's, if you have it)
  • A way to call a webhook when a job is marked complete, and a short feedback form on your side
  • No paid API calls, no SMS provider required

What you configure

Ships generic by design. Before going live, you (or Radiance, if you buy installation) set:

  • How long to wait after a job before asking (default: 1 day)
  • The rating threshold for "ask for a public review" vs "alert the owner" (default: 4/5)
  • Email copy on all three email nodes
  • Owner notification address

Demo vs. production: the honest version

The workflow and validation/routing logic are real and tested: structurally validated against n8n's own node schemas, and a runnable test (test/run-logic-test.cjs) checks eight realistic sample events against expected outcomes, all eight pass.

What hasn't happened yet: it hasn't processed a real paying client's live traffic, it ships with placeholder credentials, and it needs a short feedback form built on your side (not included, it's a few lines of HTML specific to your site, not a generic component). Treat it as a proven reference implementation, not a finished, branded product.

Get the kit, or have it installed

Self-install, or have it installed and wired to your actual booking/CRM system, see the Technology service tiers, or pair it with the Lead Machine and Quotation Follow-Up kits for the full lead-to-close-to-reputation system.