E-commerce

Post-Delivery Review Request Engine

Reviews arrive when you ask a happy customer shortly after delivery, and almost never otherwise. This workflow waits for fulfilment, gives the customer time to actually use the product, then asks — by email and optionally by SMS — and routes unhappy replies to you privately before they become public.

6 stepsRequires Zapier Professional20 minMedium

ShopifyGmailGoogle SheetsDelay by ZapierPaths by Zapier

What you get

Review requests go out on a consistent schedule after delivery.

Dissatisfied customers reach you privately first.

You build a review log you can use in marketing.

Workflow blueprint

When this happens

ShopifyNew Fulfillment

1DE

Delay by ZapierDelay For

2GM

GmailSend Email

Path A — Positive response

Path B — Negative response

5GS

Google SheetsCreate Spreadsheet Row

The full blueprint — every field mapping, example value and the written copy for each message — is included with purchase.

Getting it into Zapier

Build this one from the recipe. The blueprint gives you the exact trigger, action events and field mapping for all 6 steps, so it is a copy-and-paste job rather than a design job.

You need your own Zapier account. Zapier’s Free plan runs single-step Zaps only; multi-step Zaps need a paid plan, and Paths and Webhooks need Professional. How this works →

Not on Zapier?

n8n — import and go

An n8n workflow JSON ships with this template. Import it and all 6 steps arrive on the canvas wired in order, and 3 of the 6 nodes arrive with their fields already filled in — the subject lines, the message copy, the delays, the column names. Every step maps to a native n8n node.

What an import cannot carry is your credentials, and the IDs that only exist inside your own account — which spreadsheet, which channel, which board. Those stay in a sticky note under the node, listing what is already done so you do not retype it, and what is left so you can see it.

Make — build guide

A Make-specific guide ships with this template: every module in order, every field value, and the concept translations that catch people out — filters live on the links between modules, and the schedule lives on the scenario rather than in a trigger module.

Self-hosted n8n has no per-task fee, which is worth knowing if this workflow runs at volume. Platform coverage →