E-commerce

Abandoned Cart Recovery

Most abandoned carts are interruptions rather than rejections. This workflow waits an hour, sends a plain reminder with the cart link, waits a day and sends one more with a reason to return, then logs the outcome so you can see what recovery is actually worth to you.

6 stepsRequires Zapier Starter or higher15–20 minEasy

ShopifyGmailGoogle SheetsDelay by Zapier

What you get

Abandoned checkouts get two timed, well-written reminders.

You can measure recovered revenue instead of guessing.

Nobody has to remember to send anything.

Workflow blueprint

When this happens

ShopifyNew Abandoned Cart

1DE

Delay by ZapierDelay For

2GM

GmailSend Email

3DE

Delay by ZapierDelay For

4GM

GmailSend Email

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 5 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 →