Recover abandoned carts with a delayed WhatsApp nudge
Waits an hour after a checkout is abandoned, re-checks the cart against the store API, and sends a WhatsApp template nudge with a recovery link only if it is genuinely still unpaid and above a value f.
A webhook receives the abandoned checkout and a Set node captures the cart id, phone, first name, value and recovery URL immediately — the payload will not be available when the execution resumes. A Filter applies three gates: a real phone number, a cart above the value floor, and a working recovery link. Remove Duplicates keys on the cart id so a shopper editing their basket does not start five timers. The Wait node then suspends the execution for an hour. On resume an HTTP Request re-reads the checkout from the store's admin API with `neverError` and the full response, and an IF requires both a 200 and an incomplete checkout before anything is sent — so a paid, deleted or unreachable cart takes the quiet branch. Only genuinely open carts get the approved WhatsApp template. Every send is logged, and failures route to an error rail on Slack.
Key benefits
- ✓Recovery messages land on WhatsApp, where they are read, rather than in an unopened email
- ✓The cart is re-checked after the delay, so customers who already paid are never messaged
- ✓A value floor stops you spending goodwill chasing carts that are not worth it
- ✓One nudge per cart, however many times the storefront fires the event
- ✓The log gives you a real recovery rate to measure instead of a vendor's claim
Use cases
- →Stores whose customers checkout on a phone and drop off mid-payment
- →Merchants in markets where WhatsApp outperforms email by an order of magnitude
- →Growth teams that want recovery attribution they can audit
- →Anyone who has been messaged about a cart they had already paid for
Integrations
Workflow preview (11 nodes)
The template's actual node layout and connections. Node parameters and credential slots unlock with the download.
What's inside (11 nodes)
A look at the node types this workflow uses. No purchase required — full parameters and credentials are yours after you buy.
From download to running in 3 steps
- 1Import. In n8n, open Workflows → menu → “Import from File” and pick the downloaded JSON.
- 2Connect. Add your own credentials on the app nodes - n8n highlights exactly which ones need them.
- 3Activate. Run it once to test, then toggle Active. The automation is live.
What you'll learn
Production levelProduction-grade: idempotency, dead-letter handling, and reconciliation included.
- •Moving data between Google Sheets and Slack in a single run
- •Adding retries and an explicit error path to external calls
- •Testing against pinned sample data before connecting anything real
Every node carries its own documentation on the canvas, plus notes explaining why the architecture was built this way, a credential setup guide, troubleshooting, and three practice exercises. Sample data comes pinned to the trigger, so you can hit Execute and watch data flow before connecting a single account.
Common questions
What exactly do I get?
The complete, ready-to-import n8n workflow as a JSON file, delivered instantly after payment. Import it into your own n8n (cloud or self-hosted), add your credentials, and it runs.
How do I import it into n8n?
In n8n, open Workflows, click the three-dot menu, choose “Import from File”, and select the downloaded JSON. Then connect your own app credentials on the highlighted nodes.
Do I need anything else for it to work?
You need your own n8n instance and accounts/credentials for the apps this workflow connects to (HTTP / REST API, WhatsApp, Google Sheets, Slack). No coding is required.
What if it doesn't work for me?
If the file is faulty, won't import, or isn't as described, contact us within 7 days and we'll fix it or refund you - see our refund policy.
Can I modify or resell it?
You can freely adapt and use it in your own or your clients' projects. Reselling or redistributing the template file itself is not permitted.
Related templates
Notify the team on new events for cart recovery
Cart recovery on n8n: runs when a webhook arrives across Google Sheets, Slack and Twilio, starting at "Map to Canonical Schema". Routes each kind of record down its own branch. 13 documented nodes.
Win back incomplete checkouts for cart recovery
Cart recovery on n8n: runs on a schedule across Google Sheets and Slack, starting at "Read Pending Queue (Google Sheets)". Walks the list in batches, pausing between them. 22 documented nodes.
Route new orders for cart recovery
Cart recovery on n8n: runs when a webhook arrives across Google Sheets, Slack and Shopify, starting at "Map to Canonical Schema". Routes each kind of record down its own branch. 23 documented nodes.
Alert the team on new events: Slack & Google Sheets
Cart recovery on n8n: runs when a webhook arrives across Slack and Google Sheets, starting at "Map to Canonical Schema". Routes each kind of record down its own branch. 14 documented nodes.