Shopify + Google Sheets: WhatsApp recovery tracking
Cancelled orders hurt twice. You lose the sale, then you waste time digging through Shopify, copying customer details, and sending “one-off” WhatsApp messages that never get tracked properly.
Shopify store owners feel it in daily revenue. A marketing manager sees it as missed follow-up. And customer success ends up stuck doing spreadsheet cleanup. This Shopify WhatsApp tracking automation fixes that by verifying numbers first, sending a personalized recovery message, and logging every outcome in Google Sheets.
Below, you’ll see how the workflow runs, what it changes in your day-to-day, and what you need to get it live without turning it into a “project.”
How This Automation Works
See how this solves the problem:
n8n Workflow Template: Shopify + Google Sheets: WhatsApp recovery tracking
flowchart LR
subgraph sg0["Schedule Flow"]
direction LR
n0@{ icon: "mdi:swap-vertical", form: "rounded", label: "Loop Over Items", pos: "b", h: 48 }
n1["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/httprequest.dark.svg' width='40' height='40' /></div><br/>Get Specific Customer Data"]
n2@{ icon: "mdi:swap-vertical", form: "rounded", label: "Split Out", pos: "b", h: 48 }
n3["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/httprequest.dark.svg' width='40' height='40' /></div><br/>Get All Cancelled Order"]
n4["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/code.svg' width='40' height='40' /></div><br/>Get Product name with re-ord.."]
n5["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/httprequest.dark.svg' width='40' height='40' /></div><br/>Get customer info"]
n6["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/code.svg' width='40' height='40' /></div><br/>Get Customer Total Spent"]
n7@{ icon: "mdi:play-circle", form: "rounded", label: "Schedule Trigger", pos: "b", h: 48 }
n8@{ icon: "mdi:swap-horizontal", form: "rounded", label: "If", pos: "b", h: 48 }
n9@{ icon: "mdi:web", form: "rounded", label: "Rapiwa (verify number)", pos: "b", h: 48 }
n10@{ icon: "mdi:web", form: "rounded", label: "Rapiwa (sent message)", pos: "b", h: 48 }
n11@{ icon: "mdi:cog", form: "rounded", label: "Wait", pos: "b", h: 48 }
n12@{ icon: "mdi:database", form: "rounded", label: "Store State of Rows in Verif..", pos: "b", h: 48 }
n13@{ icon: "mdi:database", form: "rounded", label: "Store State of Rows in Unver..", pos: "b", h: 48 }
n8 --> n10
n8 --> n13
n11 --> n0
n2 --> n0
n0 --> n1
n7 --> n3
n5 --> n6
n10 --> n12
n9 --> n8
n3 --> n2
n6 --> n9
n1 --> n4
n4 --> n5
n12 --> n11
n13 --> n11
end
%% Styling
classDef trigger fill:#e8f5e9,stroke:#388e3c,stroke-width:2px
classDef ai fill:#e3f2fd,stroke:#1976d2,stroke-width:2px
classDef aiModel fill:#e8eaf6,stroke:#3f51b5,stroke-width:2px
classDef decision fill:#fff8e1,stroke:#f9a825,stroke-width:2px
classDef database fill:#fce4ec,stroke:#c2185b,stroke-width:2px
classDef api fill:#fff3e0,stroke:#e65100,stroke-width:2px
classDef code fill:#f3e5f5,stroke:#7b1fa2,stroke-width:2px
classDef disabled stroke-dasharray: 5 5,opacity: 0.5
class n7 trigger
class n8 decision
class n12,n13 database
class n1,n3,n5,n9,n10 api
class n4,n6 code
classDef customIcon fill:none,stroke:none
class n1,n3,n4,n5,n6 customIcon
The Challenge: Recovering Cancelled Orders Without Guesswork
Most “order recovery” efforts fall apart in the messy middle. You notice a cancelled order, then scramble: find the customer, confirm the number, decide what to offer, build a reorder link, send a message, and then… nothing. No visibility. Next week, you can’t tell if WhatsApp follow-ups are working, if the discount was too weak, or if half the numbers were invalid. Meanwhile, the team keeps doing it manually because setting up a real system feels complicated.
It adds up fast. Here’s where it breaks down in real stores, not theory.
- You spend about 10 minutes per cancelled order just collecting the right details and building a decent message.
- Messages get sent to unverified numbers, which means wasted discounts, wasted effort, and awkward follow-ups.
- There’s no reliable log of “sent vs. not sent,” so reporting turns into guessing (or silence).
- When volume spikes, teams either stop sending recoveries or send sloppy ones that don’t match the customer or the cart.
The Fix: Verified WhatsApp Recovery + Sheet-Based Tracking
This workflow runs on a schedule and pulls your cancelled orders from Shopify automatically. For each cancelled order, it builds the “reorder package” (customer name, item name, a reorder link, and a coupon code), then checks the customer profile to decide if the order qualifies for your recovery outreach. Next, it verifies the WhatsApp number through Rapiwa before sending anything, so you don’t waste time shouting into the void. If the number is verified, it dispatches a personalized WhatsApp message using your template. Either way, it writes a clean row to Google Sheets so you can see what happened, when, and why.
The workflow starts with a timed trigger and Shopify order retrieval. From there, it loops through cancelled orders in batches, generates the customer-specific message data, and runs verification plus sending through Rapiwa. Finally, Google Sheets becomes your source of truth: “Verified & Sent” vs. “Unverified & Not Sent.”
What Changes: Before vs. After
| What This Eliminates | Impact You’ll See |
|---|---|
|
|
Real-World Impact
Say your store sees 10 cancelled orders a day. Manually, even a “quick” process looks like 10 minutes per order between checking details, verifying a number, writing the message, sending it, and logging something somewhere, which is about 1.5 hours daily. With this workflow, the trigger and processing happen in the background, and you mainly spend a few minutes reviewing the Google Sheet and tweaking the offer if needed. That’s roughly an hour back most days, plus much cleaner tracking.
Requirements
- n8n instance (try n8n Cloud free)
- Self-hosting option if you prefer (Hostinger works well)
- Shopify for cancelled orders and customer data.
- Rapiwa to verify numbers and send WhatsApp messages.
- Google Sheets to log “verified/sent” outcomes.
- Shopify API token (create it in Shopify Admin API apps).
- Rapiwa Bearer token (get it from your Rapiwa dashboard).
Skill level: Intermediate. You’ll connect accounts, paste tokens into n8n credentials, and match Google Sheets column headers exactly.
Need help implementing this? Talk to an automation expert (free 15-minute consultation).
The Workflow Flow
A scheduled check for cancelled orders. The workflow runs daily or weekly (your call) and pulls cancelled orders from Shopify so nothing slips through the cracks.
Customer and order details get assembled. It retrieves the relevant customer profile and builds the message context like item name, coupon code, and the reorder link your customer can actually use.
Qualification and WhatsApp verification happen before sending. A spending filter can gate who receives offers, then Rapiwa verifies the WhatsApp number. If verification fails, the workflow does not send the message.
Messages go out and everything is logged. Verified numbers get the recovery message via Rapiwa, then Google Sheets logs the result as “Verified & Sent” or “Unverified & Not Sent.” A short wait step helps pacing, then it continues with the next batch.
You can easily modify the spending filter to target VIPs only, or change the message template to match seasonal offers based on your needs. See the full implementation guide below for customization options.
Step-by-Step Implementation Guide
Step 1: Configure the Timed Automation Trigger
Set the workflow schedule so cancelled orders are checked automatically.
- Add the Timed Automation Trigger node and set the schedule rule to your desired interval in Rule.
- Connect Timed Automation Trigger to Retrieve Cancelled Orders to start the data pull on each run.
Step 2: Connect Shopify Data Sources
Pull cancelled orders and fetch customer order history from Shopify via HTTP requests.
- In Retrieve Cancelled Orders, set URL to
https://your_shopify_domain/admin/api/2025-07/orders.json?customer_id=&status=cancelled. - Enable Send Headers and set X-Shopify-Access-Token to
[CONFIGURE_YOUR_API_KEY]in Retrieve Cancelled Orders. - In Fetch Customer Order List, set URL to
=https://your_shopify_domain/admin/api/2025-07/orders.json?customer_id={{ $json.customer.id }}&status=anyand enable Send Headers with the same Shopify token. - In Fetch Customer Profile, set URL to
=https://your_shopify_domain/admin/api/2025-07/customers/{{ $json.customerId }}.jsonand enable Send Headers with the Shopify token.
Step 3: Set Up Order Parsing and Customer Filtering
Split orders into individual items, build reorder data, and filter eligible customers.
- In Separate Orders, set Field To Split Out to
orders. - Ensure Separate Orders connects to Batch Item Iterator, and the second output of Batch Item Iterator connects to Fetch Customer Order List.
- Keep the JavaScript in Build Reorder Details as provided to generate
customerId,phone,re_order_link, andproductsBoughtvalues. - In Compute Spending Filter, keep the provided JavaScript that filters customers where
total_spentis greater than0.
Step 4: Verify and Send WhatsApp Messages
Verify the customer’s WhatsApp number, branch based on verification, and send the recovery message.
- In Verify WhatsApp Number, set Operation to
verifyWhatsAppNumberand Number to={{ $json.phone }}. - Credential Required: Connect your rapiwaApi credentials in Verify WhatsApp Number.
- In Conditional Branch Check, keep the boolean condition using
={{ $json.exists }}to route verified numbers. - In Dispatch WhatsApp Message, set Number to
={{ $json.jid }}and keep the message body with expressions referencing{{ $('Build Reorder Details').item.json.name }}and{{ $('Build Reorder Details').item.json.re_order_link }}. - Credential Required: Connect your rapiwaApi credentials in Dispatch WhatsApp Message.
Step 5: Log Results and Control Batch Timing
Record verified and unverified sends to Google Sheets and pace the workflow.
- In Log Verified Sends, set Operation to
append, Document ID to[YOUR_ID], and Sheet Name togid=0. - Map columns in Log Verified Sends using expressions like
={{ $('Build Reorder Details').item.json.name }},={{ $('Build Reorder Details').item.json.phone }}, and={{ $('Build Reorder Details').item.json.re_order_link }}. - Credential Required: Connect your googleSheetsOAuth2Api credentials in Log Verified Sends.
- In Log Unverified Attempts, keep Operation as
appendand set validity tounverifiedin the column mappings. - Credential Required: Connect your googleSheetsOAuth2Api credentials in Log Unverified Attempts.
- Connect both Log Verified Sends and Log Unverified Attempts to Delay Execution Step, then connect Delay Execution Step to Batch Item Iterator for controlled batching.
Step 6: Test & Activate Your Workflow
Validate the full flow end-to-end before enabling the schedule.
- Click Execute Workflow to run a manual test and confirm Retrieve Cancelled Orders returns data.
- Verify that Build Reorder Details outputs
name,phone, andre_order_linkfields for each customer. - Confirm that verified numbers route through Conditional Branch Check to Dispatch WhatsApp Message and appear in Log Verified Sends.
- Turn on the workflow with the Active toggle to run it on schedule.
Watch Out For
- Shopify credentials can expire or need specific permissions. If things break, check your Admin API app scopes (orders and customers) and token status first.
- If you’re using Wait nodes or external rendering, processing times vary. Bump up the wait duration if downstream nodes fail on empty responses.
- Google Sheets column headers must match exactly. Extra spaces and casing mistakes are honestly the most common reason your logs “vanish.”
Common Questions
Usually about an hour if your tokens and Sheet are ready.
Yes, but you’ll want someone who’s comfortable with copy-pasting API tokens and double-checking spreadsheet headers. No coding is required for the standard setup.
Yes. n8n has a free self-hosted option and a free trial on n8n Cloud. Cloud plans start at $20/month for higher volume. You’ll also need to factor in Rapiwa usage costs based on how many verifications and messages you send.
Two options: n8n Cloud (managed, easiest setup) or self-hosting on a VPS. For self-hosting, Hostinger VPS is affordable and handles n8n well. Self-hosting gives you unlimited executions but requires basic server management.
You can. Swap the spending filter logic in the “Compute Spending Filter” step to target VIPs, first-time buyers, or customers above a certain lifetime spend. Most stores also customize the WhatsApp template used in the “Dispatch WhatsApp Message” step to match brand voice, offer type, and link format. If your team prefers a different verification provider, you can replace the Rapiwa verification with an HTTP Request node that hits your chosen service.
Usually it’s an expired or wrong Bearer token in your n8n credentials. If verification works but sending fails, check your Rapiwa template settings and confirm the phone number format you pass from Shopify is in the expected international format. Rate limiting can also show up when you process large batches; reducing batch size and adding a slightly longer wait often stabilizes it.
On n8n Cloud, capacity mainly depends on your plan’s monthly executions, and on self-hosted it depends on your server. Practically, most stores run this daily in batches without issues as long as you pace requests and keep batch sizes reasonable.
Often, yes, because this flow needs branching (verified vs. unverified), batching to avoid rate limits, and a clean logging pattern that stays consistent over time. n8n makes that easier to maintain without paying extra for every “path” or every added step. Zapier or Make can still work if you keep it very simple, but you may end up splitting logic across multiple zaps/scenarios. Frankly, the moment you care about verification and reliable reporting, n8n starts to feel calmer. Talk to an automation expert if you want a quick recommendation based on your volume.
You end up with fewer lost sales, fewer manual follow-ups, and a Google Sheet that tells the truth. Set it once, then let the workflow do the repetitive part while you focus on improving the offer and the customer experience.
Need Help Setting This Up?
Our automation experts can build and customize this workflow for your specific needs. Free 15-minute consultation—no commitment required.
